Hi,

> I know there are better and more elegant solution involvingthe ELF
> header and the RPATH/RUNPATH field, but I think tha above is the most
> portable and debuggable, since AFAIK we got a fair MacOsX userbase
> and since I had no reliable access to any OSX box (neither I'll have
> into the foreseeable future) I don't want to harm them unless it
> becomes absolutely unavoidable.

Since you're using libtool, I don't think you'll have to mess with all
that and use a wrapper (which may not work in all cases, think about
a multilib setup with x86_32 & x86_64 support or a /home install).
In a project of mine, I'm using internal libs like what you wanna
do, all I have to do is to add stuff like that:

foo_LDADD = $(top_builddir)/path/to/libbar.la

and add things like that for libbar:
libbardir = $(libdir)/mypetprogram

libtool will play the rpath game by itself at install time.

If I take tcmp3cut as an example, this should be as simple as replacing:
noinst_LTLIBRARIES = libtc.la
by:
libtc_LTLIBRARIES = libtc.la
libtcdir = $(libdir)/transcode-$version


since tcmp3cut already uses libtc.la to link, libtool should do the rest
of the work for you :)



Regards,

Alexis.

Attachment: signature.asc
Description: PGP signature

Reply via email to