Re: forcing configure to use /opt/gnome

["Ben Taylor" <sol7x86 hotmail com>]

Steve Vertigan wrote:

> Ben Taylor wrote:
>
> > The main problem is that some directories and -L flags
> > are not added for specific sets of *LIBS.  I've tried
> > to update some of the sources, but eventually gave
> > up because they never made it in to the next release
> > of the source.
>
> Indeed. In my case I've managed to get things working running .
> /configure --help
> and then noting every library that it has an option for and then
> specifying them all. But it's tedious and stopping me from automating
> the process.
> For instance to compile one application I had to type
>
> ./configure --prefix=/opt/gnome   \
> --with-gnome=/opt/gnome  \
> --with-gtk-prefix=/opt/gnome  \
> --with-esd-prefix=/opt/gnome  \
> --with-orbit-prefix=/opt/gnome  \
> --with-glib-prefix=/opt/gnome  \
> --with-oaf-prefix=/opt/gnome  \
> --with-gconf-prefix=/opt/gnome  \
> --with-gdk-pixbuf-prefix=/opt/gnome

ouch, ouch, ouch.  If you hack the gnome-config and associated *-config 
files and the other files in /opt/gnome/lib/*Conf.sh,
you can add the right flags which get left out.  I've haven't
had to what you did, and can appreciate your pain.

> Maybe ./configure needs a --default-prefix or something to try looking
> for libaries in first.

<shrug>   Having a good environment setup with PATH, LDFLAGS,
CFLAGS, CPPFLAGS, and CXXFLAGS really reduced my pain.  I only
had to hack a few configure script to get them to build the
environment properly.  IMHO, if you fix glib/gtk+-config and gnome-libs 
gnome-config and gnomeConf.sh first and foremost,
the rest of it is progressively easier and doesn't require
the kind of hackery you've had to do above.

I doubt that a "global-prefix" is really the right solution.
Folks can configure the code to be almost anywhere they want.
Folks using depot have it especially easy because they have
all the versions online and can specify exactly which version
of a particular package they want to use.


> On a relatively unrelated note does anyone know why despite adding
> entries to /etc/ld.so.conf and running ldconfig I still can't get
> applications that rely on non-standard libraries to run until I put the
> path in the environment variable $LD_LIBRARY_PATH?  I'm observing this
> with gnome libraries in /opt/gnome/lib and Mesa libraries in
> /usr/local/lib.  I suppose I could just set $LD_LIBRARY_PATH from a
> login script but I'm trying to figure out the basics of libraries and
> linking and ld.so.conf seems  potentially more elegant way.

Not being a BSD kinda guy, I'm not sure what options you have.
In solaris,  in addition to the -L<libdir> flag, I also use
-R<libdir> flag to tell the runtime linker how to find the
library path's without setting an LD_LIBRARY_PATH.

For some things that have libraries, in Solaris, I've had to
set an LD_RUN_PATH to make sure that libraries that depend
on other libraries (like the xmms libs) can find them.  I don't
think I have to do this anymore cause I finally bothered to add
the libtool macro to my aclocal macro. (Thanks to whoever suggested
it to me. It's made my life a whole lot easier)

HTH,

Ben
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com