Hi Enrico,
* Enrico Weigelt wrote on Tue, Sep 27, 2005 at 03:27:21PM CEST:
> * Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
>
> > > how does libtool decide whether to link against an .la library
> > > dynamically vs. statically ?
> >
> > For a program or a library? Uninstalled or installed librar
On Tue, 27 Sep 2005, Howard Chu wrote:
> First of all, my objective - other folks may have their own objectives
> different than this: Build a suite of software that uses shared libraries,
> such that any embedded runpaths only reflect the ultimate install path (e.g.
> /opt/foo/lib) and not any of
* Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
Hi,
> > how does libtool decide whether to link against an .la library
> > dynamically vs. statically ?
>
> For a program or a library? Uninstalled or installed library
> (see recent bug report of Howard Chu)?
Each of these cases ...
I've now fig
Ralf Wildenhues wrote:
We have better support for sysroot and/or DESTDIR on our TODO list.
Why don't you help us improve and fix libtool? That is bound to be
a lot less work.
*time passes*
http://lists.gnu.org/archive/html/libtool-patches/2005-06/msg00161.html
Oh, you asked before. Why not r
Hi Enrico,
* Enrico Weigelt wrote on Mon, Sep 26, 2005 at 09:56:27PM CEST:
>
> how does libtool decide whether to link against an .la library
> dynamically vs. statically ?
For a program or a library? Uninstalled or installed library
(see recent bug report of Howard Chu)? On a system with bot
Hi folks,
how does libtool decide whether to link against an .la library
dynamically vs. statically ?
I'm currently working on my own implementation, since libtool
doesn't suit my needs (ie. sysroot'ed building), but I didn't
find any clear specification for libtool's behaviour.
cu
--
