Ralf Wildenhues wrote:
Hello Bruno,
* Bruno Haible wrote on Sun, Feb 24, 2008 at 02:51:08PM CET:
A while ago someone said that if in a build directory I have a (not yet
installed) ../lib/libfoo.la, to link with this library I should *not* use
libtool ... -L../lib -lfoo
but rather mentio
Hello Bruno,
* Bruno Haible wrote on Sun, Feb 24, 2008 at 02:51:08PM CET:
>
> A while ago someone said that if in a build directory I have a (not yet
> installed) ../lib/libfoo.la, to link with this library I should *not* use
>
>libtool ... -L../lib -lfoo
>
> but rather mention the .la file
Bruno Haible wrote:
Hi,
A while ago someone said that if in a build directory I have a (not yet
installed) ../lib/libfoo.la, to link with this library I should *not* use
libtool ... -L../lib -lfoo
but rather mention the .la file explicitly:
libtool ... -L../lib ../lib/libfoo.la
or
li
Hi Bruno,
Bruno Haible wrote:
> Hi,
>
> A while ago someone said that if in a build directory I have a (not yet
> installed) ../lib/libfoo.la, to link with this library I should *not* use
>
>libtool ... -L../lib -lfoo
>
> but rather mention the .la file explicitly:
>
>libtool ... -L../
Hi,
A while ago someone said that if in a build directory I have a (not yet
installed) ../lib/libfoo.la, to link with this library I should *not* use
libtool ... -L../lib -lfoo
but rather mention the .la file explicitly:
libtool ... -L../lib ../lib/libfoo.la
or
libtool ... ../lib/libfo