|author||Diego E. 'Flameeyes' Pettenò <email@example.com>||2009-01-22 16:37:40 +0100|
|committer||Diego E. 'Flameeyes' Pettenò <firstname.lastname@example.org>||2009-01-22 16:37:40 +0100|
Remove support for internal distributing and bundling of libltdl.
Standing to what the libtool documentation says, the LTDL_INIT macro and the related configure options are only useful when intending to distribute libltdl, and is superfluous if the system copy were always to be used. Which makes it very easy to just drop the internal copy and use the system library, just do it like any other library lacking pkg-config files to identify its presence. If this tries to build against an older libtool version it might fail at link time, so for now this is not an user-proof solution. But it at least should provide a working environment for packagers.
Diffstat (limited to 'configure.ac')
1 files changed, 21 insertions, 3 deletions
diff --git a/configure.ac b/configure.ac
index 9912843f..f659d49e 100644
@@ -237,9 +237,28 @@ AS_IF([test "$pulseaudio_cv__Bool" = "yes"], [
#### libtool stuff ####
LT_INIT([dlopen win32-dll disable-static])
+dnl Unfortunately, even up to libtool 2.2.6a there is no way to know
+dnl exactly which version of libltdl is present in the system, so we
+dnl just assume that it's a working version as long as we have the
+dnl library and the header files.
+dnl Check the header files first since the system may have a
+dnl libltdl.so for runtime, but no headers, and we want to bail out as
+dnl soon as possible.
+dnl We don't need any special variable for this though, since the user
+dnl can give the proper place to find libltdl through the standard
+dnl variables like LDFLAGS and CPPFLAGS.
+ [AC_CHECK_LIB([ltdl], [lt_dlopen], [LIBLTDL=-lltdl], [LIBLTDL=])],
+AS_IF([test "x$LIBLTDL" = "x"],
+ [AC_MSG_ERROR([Unable to find libltdl.])])
#### Determine build environment ####
@@ -1174,7 +1193,6 @@ AM_CONDITIONAL([FORCE_PREOPEN], [test "x$FORCE_PREOPEN" = "xyes"])