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 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 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, automake (which I assume you're using) will know to rebuild > the output when libfoo changes. I am using automake. I didn't know automake didn't handle -lfoo dependency wise I hope ../lib/libfoo.a works though because some apps wants the static lib even though there is a shared one too? > > > Is there a way to tell libtool after it has built a lib to do a > > "subinstall" of the > > lib into some dir in the build tree so that one don't have to specify lots > > of -LDIR options, just to the one dir instead? > > No. OK, thanks _______________________________________________ http://lists.gnu.org/mailman/listinfo/libtool
