* Joakim Tjernlund wrote on Sat, Dec 12, 2009 at 04:33:49PM CET:
We have this big directory structure which contains both apps and libs.
The apps needs lots of libs that are scattered in various sub dirs.
It is rather messy to add lots -LDIR options to apps linking stage.
For dependencies on
* Joakim Tjernlund wrote on Sat, Dec 12, 2009 at 12:05:13PM CET:
Ralf Corsepius wrote on 12/12/2009 07:20:05:
The whole purpose of DESTDIR is being set at install-time and not to be
AC_SUBST'ed anywhere.
I.e. doing things like outlined above would contradict it's purpose.
It doesn't
Ralf Wildenhues ralf.wildenh...@gmx.de wrote on 13/12/2009 11:14:58:
From: Ralf Wildenhues ralf.wildenh...@gmx.de
To: Joakim Tjernlund joakim.tjernl...@transmode.se
Cc: libtool@gnu.org
Date: 13/12/2009 11:15
Subject: Re: lib seach path
* Joakim Tjernlund wrote on Sat, Dec 12, 2009 at
Ralf Wildenhues ralf.wildenh...@gmx.de wrote on 13/12/2009 11:18:31:
* Joakim Tjernlund wrote on Sat, Dec 12, 2009 at 12:05:13PM CET:
Ralf Corsepius wrote on 12/12/2009 07:20:05:
The whole purpose of DESTDIR is being set at install-time and not to be
AC_SUBST'ed anywhere.
I.e.
Hello,
this is ltdl-related, especially related to the case when you try to
open an invalid module without knowing that it actually is invalid.
The story is that if you try to lt_dlopen a module that can't be
dlopened (for example when it has unsatisfied dependencies), the
lt_dlopen function will
Hello,
if you want to lt_dlsym functions from your modules, how do you do that?
If you write Windows libraries, you have to dllexport stuff, however GCC
4 supports the same feature, there you have to use visibility(default)
stuff.
There is something about this in the libtool manual (section 11.2):
On Sun, 13 Dec 2009, Matěj Týč wrote:
What I have thought of is stopping any attempt to open any new module
filename if the previous attempt has failed for another reason that
because the file wasn't there. Do you think this is a good assumption?
The problem is that libltdl supports several
* Joakim Tjernlund wrote on Sun, Dec 13, 2009 at 12:04:23PM CET:
Ralf Wildenhues wrote on 13/12/2009 11:14:58:
For dependencies on libraries within the build tree, prefer relative
file references over link flags; i.e., write
../lib/libfoo.la rather than -L../lib -lfoo
That way,
* Joakim Tjernlund wrote on Sun, Dec 13, 2009 at 12:26:18PM CET:
I am building for /opt/appl/ on the target using a build tree
outside my sources: I want to install my apps/libs into a dir
next to my build tree. Once everything is installed into the
temporary install tree, I build a
