Hi,
> However, I need these plugins to be in the same directory as where the main
> executable resides, and I cannot install them into one of the $blah/lib
> paths or add the current path to LD_LIBRARY_PATH.
This is a bad idea. Most likely, your program will end up in /usr/bin or
/usr/local/bin
I'm really sorry but it seems I was a bit too sleepy last night when I wrote
my original post. :(
This isn't about plugins, it's actually about a few helper libraries which
are needed by the main program.
These libraries are not loaded by the program itself @ runtime, but rather
by the dynamic l
Hi,
> This isn't about plugins, it's actually about a few helper libraries which
> are needed by the main program.
There is nothing to say against installing these libraries into
$(libdir), although you can also simply link them statically when they
are used by only one program (gives you a 5% s
Hi,
There is nothing to say against installing these libraries into
$(libdir), although you can also simply link them statically when they
are used by only one program (gives you a 5% speed bonus on i386, as
shared libraries need one register to point to itself, as they may be
mapped to different
This patch was first posted to [EMAIL PROTECTED] org on Sat, 14 Jun 2003
09:47:10 -0700. It has been pinged and reposted to libtool-patches in
the mean time without receiving an answer.
Hi all,
the libtool m4 macros check among other things for maximum command line
length.
As Tony Wyatt found
