On Thursday 01 September 2005 16:52, Bob Friesenhahn wrote: > So it seems that a libtool-provided macro should be used in > configure.ac to test for an installed libltdl. Testing for it in a > simple way could well indeed result in false negatives due to libltdl > depending on some other library (e.g. -ldl). It is not necessary for > a package to include its own copy of libtool in order to make use of > it. Libtool may already be installed in a standard location. > > I may be missing something, but all the libltdl-related macros I see > are for the case of when libltdl is bundled with the package. I don't > see one for simply testing for an already installed libltdl.
thanks bob, that is exactly the problem I'm facing. now I wonder: if the libtool *.la files contain all information about the dependencies etc, then shouldn't there be some macro that searches for that *.la files, gets the dependencies from it, does the compile and link test and sets up CFLAGS and LIBS to include whatever is necessary? is there something that works like AC_CHECK_LIB, except that AC_CHECK_LIB seems to have no clue about *.la files, so is there some alternative that does? Regards, Andreas _______________________________________________ http://lists.gnu.org/mailman/listinfo/libtool
