Re: Suggestion

Libtool doesn't use DESTDIR.... The makefiles (autoconf/automake) use 
DESTDIR.
When the *.la files are built, libtool puts a line like
   libdir=/some/path/to/a/lib/dir
in it.  Then, when you try to install via 'make install'  which, in turn 
call libtool --mode=install
libtool will refuse to install into any directory EXCEPT what was 
specified in the .la file.
It breaks, therefore, if you try to use DESTDIR= or prefix= arguments to 
the 'make install'
command.

-Rob

Bob Friesenhahn wrote:

> On Fri, 12 Mar 2004, Robert Wyrick wrote:
>
>  
>
> > I'm developing a package manager that aids users in installing
> > sofware (from source) into their home directories.  Packages
> > are managed in a way VERY MUCH like GNU stow.  The significant
> > feature of stow (and my package manager) is that there is a
> > distinction between runtime directories and install directories.
> >
> > I've noticed that some packages that utilize libtool have
> > problems with this because libtool has checks that make it
> > refuse to install libraries into a directory that doesn't
> > start with the location it was informed of at "configure"
> > time.  libtool has no concept of separate runtime/install
> > time directories.
> >    
>
> Libtool uses the DESTDIR environment variable to support this.
>
> Bob
> ======================================
> Bob Friesenhahn
> bfriesen@xxxxxxxxxxxxxxxxxxx
> http://www.simplesystems.org/users/bfriesen
>