Yes, it may be a good idea if somebody wrote this.
It should probably depend on LT_OUTPUT.
OTOH, the havelib module from gnulib already provides quite a bit of
functionality in this area.
OK, but what should I tell to the library users? Using gnulib is quite
troublesome since
it does not
Thank you for your reply, Ralf
This is not possible, in general. It has nothing much to do with
libtool either, because typically it's just the system semantics that
allow for only one unversioned soname symlink.
OK, but an easy check whether I can safely link with the lib would be nice, too.
On Tue, 2009-02-03 at 11:05 +0100, Matěj Týč wrote:
Yes, it may be a good idea if somebody wrote this.
It should probably depend on LT_OUTPUT.
OTOH, the havelib module from gnulib already provides quite a bit of
functionality in this area.
OK, but what should I tell to the library
Hi all,
I wonder if it's possible to tell libtool to generate .lo file
elsewhere than in source directory (where Makefile resides).
Best regards,
Michel
--
.''`.
: :' : We are debian.org. Lower your prices, surrender your code.
`. `' We will add your hardware and software distinctiveness
Hello Michel,
* Michel Briand wrote on Tue, Feb 03, 2009 at 06:09:11PM CET:
I wonder if it's possible to tell libtool to generate .lo file
elsewhere than in source directory (where Makefile resides).
Yes:
libtool --mode=compile $CC -o some/where/foo.lo -c else/where/foo.c
If you're using
* Matěj Týč wrote on Tue, Feb 03, 2009 at 11:15:10AM CET:
This is not possible, in general. It has nothing much to do with
libtool either, because typically it's just the system semantics that
allow for only one unversioned soname symlink.
OK, but an easy check whether I can safely link
