Sander,
If you can ensure this check is done after the libtool script is
created,
you may be able to write a macro similar to AC_CHECK_LIB that uses a
shared library rather than an executable. If it won't link, you can
assume that there isn't a shared version of the dependent library.
If this test fails, but AC_CHECK_LIB doesn't, then you only have a
static lib.
HTH,
Robert
-----Original Message-----
From: Sander Niemeijer [mailto:address@hidden
Sent: Thursday, September 18, 2003 3:53 AM
To: address@hidden; address@hidden
Subject: Re: Detecting availability of a shared libray
Is there really nobody who can help me further with this?
Regards,
Sander
On vrijdag, sep 5, 2003, at 17:25 Europe/Amsterdam, Sander Niemeijer
wrote:
Hi all,
I have a package that produces a shared/static library via libtool.
However this package needs to make use of some external library for
data import/export. Since my library has both a shared and a static
version this external library also needs to have at least a shared
version available. If this is the case then linking my library with
libtool and the appropriate -L and -l flags will work nicely. However,
if only a static version of the external library is available then
building a shared version of my library will fail (except perhaps on
systems that do not need specific PIC flags when creating shared
library object files).
My problem is that if I use AC_CHECK_LIB to check for the external
library, then the check that is being performed is to see whether the
external library can be linked into a program. Now this works of
course fine if the external library is only available as a static
version. So my question now is, does anybody know whether there is a
way to explicitly test for the availability of the shared version of
the external library?
Regards,
Sander Niemeijer
_______________________________________________
Libtool mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/libtool