link X11 automatically

Ben Artin wrote:
> In article <6com4eF3fleqpU1.TakeThisOut@mid.individual.net>,
> Frank Swarbrick <fswarbrick.TakeThisOut@gmail.com> wrote:
>
>> /usr/bin/ld: can't locate file for: -lX11
>>
>> LFLAGS = -L/usr/X11R6/lib
>>
>> So my question is, is there a way to have /usr/X11R6/lib added to the
>> standard ld lib search chain?
>
> The standard way to solve this problem on UNIX-based systems (of which Mac OS X
> is one) is to use autoconf. See
> <http://www.gnu.org/software/autoconf/autoconf.html>. IMO it's kinda painful.

Yoikes!


I will look at it.

Thanks,
Frank

On Sun, 29 Jun 2008 21:07:05 -0600, Frank Swarbrick <fswarbrick DeleteThis @gmail.com>
wrote:
> Ben Artin wrote:
>> In article <6com4eF3fleqpU1 DeleteThis @mid.individual.net>,
>> Frank Swarbrick <fswarbrick DeleteThis @gmail.com> wrote:
>>
>>> /usr/bin/ld: can't locate file for: -lX11
>>>
>>> LFLAGS = -L/usr/X11R6/lib
>>>
>>> So my question is, is there a way to have /usr/X11R6/lib added to the
>>> standard ld lib search chain?
>>
>> The standard way to solve this problem on UNIX-based systems (of which Mac OS X
>> is one) is to use autoconf. See
>> <http://www.gnu.org/software/autoconf/autoconf.html>. IMO it's kinda painful.
>
> Yoikes!
>
>
> I will look at it.

Be warned, it's not called autohell for nothing. In particular, libtool,
IMO, is spectacularly bloated and grotesque piece of software. To top it
all, autohell works very badly with compilers other than GCC. And I
wouldn't count on it being that well tested on OSes other than Linux
either.

A bientot
Paul
--
Paul Floyd http://paulf.free.fr

Frank Swarbrick wrote:
> I was trying to compile (make) a program that uses X11. Below is the
> compile line followed by the error message:
>
> gcc hi.o s7_comp.a s7_data.a seed7_05.a -lX11 -lncurses -lm -o hi
> /usr/bin/ld: can't locate file for: -lX11
>
> After some searching I found the location of libX11:
> /usr/X11R6/lib/libX11.dylib
>
> So I made this change to the makefile:
>
> LFLAGS = -L/usr/X11R6/lib
>
> And now it works:
> gcc -L/usr/X11R6/lib hi.o s7_comp.a s7_data.a seed7_05.a -lX11 -lncurses
> -lm -o hi
>
> So my question is, is there a way to have /usr/X11R6/lib added to the
> standard ld lib search chain? This program is built on Linux, which I
> assume has X11 in the standard search chain. (Perhaps a bad assumption!)

I'm not sure if I didn't ask my question correctly, because I've found a
different answer to my question. Maybe it's so obvious? Anyway, all I
had to do is create an environment variable LIBRARY_PATH and place
/usr/X11R6/lib in it.

Here it is in my .profile member:
LIBRARY_PATH=/opt/local/lib:/opt/local/lib/db46:/usr/X11R6/lib
export LIBRARY_PATH

(The other two libraries are to pick up libs installed using MacPorts.)

Anyway, that does everything I require. Or seems to at least!

Frank

Frank Swarbrick <fswarbrick.TakeThisOut@gmail.com> writes:

> Here it is in my .profile member:
> LIBRARY_PATH=/opt/local/lib:/opt/local/lib/db46:/usr/X11R6/lib
> export LIBRARY_PATH

Interesting - I've always exported LDFLAGS for that. Even after 20+
years of programming, I *still* learn something new every day.

> (The other two libraries are to pick up libs installed using
> MacPorts.)

It's worth noting, if you link against dynamic libraries with this,
then your users will also need to have those libraries installed, and
in the same location. X11 is optional, although it is installed by
default IIRC. MacPorts is of course a completely separate install.

It's not a *huge* problem; you can simply document that your app
requires the X11 install. For MacPorts libraries, you can simply copy
them into your .app bundle in a "copy files" build phase, and use
install_name_tool in a "run script" build phase to tweak your app
binary so that the loader looks there for them instead of under /opt.

sherm--

--
My blog: http://shermspace.blogspot.com
Cocoa programming in Perl: http://camelbones.sourceforge.net

Sherman Pendley wrote:
> Frank Swarbrick <fswarbrick.DeleteThis@gmail.com> writes:
>
>> Here it is in my .profile member:
>> LIBRARY_PATH=/opt/local/lib:/opt/local/lib/db46:/usr/X11R6/lib
>> export LIBRARY_PATH
>
> Interesting - I've always exported LDFLAGS for that. Even after 20+
> years of programming, I *still* learn something new every day.

Do you mean something like this?
export LDFLAGS=-L/usr/X11R6/lib

>> (The other two libraries are to pick up libs installed using
>> MacPorts.)
>
> It's worth noting, if you link against dynamic libraries with this,
> then your users will also need to have those libraries installed, and
> in the same location. X11 is optional, although it is installed by
> default IIRC. MacPorts is of course a completely separate install.
>
> It's not a *huge* problem; you can simply document that your app
> requires the X11 install. For MacPorts libraries, you can simply copy
> them into your .app bundle in a "copy files" build phase, and use
> install_name_tool in a "run script" build phase to tweak your app
> binary so that the loader looks there for them instead of under /opt.

I'm not really a C programmer, so I don't know most of the tricks. My
need here for X11 was to install the Seed7 programming language.
MacPorts was used to install the gmp and db46 packages required to
install OpenCobol.

But if I ever do develop a program that I want to install elsewhere I
will keep you information in mind. Thanks!

Frank

Frank Swarbrick <fswarbrick.RemoveThis@gmail.com> writes:

> Sherman Pendley wrote:
>> Frank Swarbrick <fswarbrick.RemoveThis@gmail.com> writes:
>>
>>> Here it is in my .profile member:
>>> LIBRARY_PATH=/opt/local/lib:/opt/local/lib/db46:/usr/X11R6/lib
>>> export LIBRARY_PATH
>>
>> Interesting - I've always exported LDFLAGS for that. Even after 20+
>> years of programming, I *still* learn something new every day.
>
> Do you mean something like this?
> export LDFLAGS=-L/usr/X11R6/lib

Yep, exactly. There's nothing wrong with your approach though, I just
thought it was an interesting side note. And the fact that I'm still
learning new things after so long is part of what makes programming
fun, at least for me.

sherm--

--
My blog: http://shermspace.blogspot.com
Cocoa programming in Perl: http://camelbones.sourceforge.net