The portability warning class warns during automake calls about non-POSIX
variable names and GNU make extensions. Since both happens with the current
Makefile.am files and it's reasonable to expect that they wouldn't be
rewritten (GNU make is a reasonable requirement), just avoid the warnings.
The lt_dladvise_* interfaces are implemented only in the 2.x series and are
not implemented in 1.4, so we can rely on their presence to know that the
version is good enough.
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.
Since the tests are only useful either if you're hacking at pulseaudio as
a developer, or when running "make check", allow users to opt-out from
their build.
This for instance allows for Gentoo users not to build the tests when
installing the ebuild with tests disabled, and also allow for skipping over
eventually broken tests when trying to get the basic build going on a port.
According to Daniel, AC_PATH_XTRA is sort-of deprecated.
This patch changes the configure arguments, --x-includes=dir and
--x-libraries=dir, which are now removed and use standard pkg-config.
It also replaces --with{,out}-x with --{dis,en}able-x11, which is the
same as other optionnal dependencies.
(this patch was done in an attempt to solve a build issue on maemo, it
turns out it didn't help)
Instead of compiling the build tests manually, use autoconf
facilities, so that the results are cached between runs. Also avoid
linking when a simple compile test is enough.
Create a new macro that can be shared between projects to check for
__thread support by the compiler. This macro might come useful for
xine-lib too so I want to keep it separate for easier importing it
over.
Name the defined macro SUPPORT_TLS___THREAD to follow the same style
as the checks from attributes.m4.
Instead of writing custom code to check for cflags checking, import a
copy of attributes.m4 from xine-lib's repository and use the
CC_CHECK_CFLAGS macro.
The advantage lies not only in being able to reduce the custom code in
configure.ac, but also in the fact that the CC_CHECK_CFLAGS macro
caches the results, making ./configure -C quite faster on second run.
Check for the CFLAGS for any compiler and not just GCC, if the
compiler does support the flag it is better to u se it anyway,
otherwise it will be skipped.
Instead of just checking if the compiler supports -std=c99 option,
make use of the autoconf macro for discovering C99. This way other
non-GCC compiler could be used in C99 mode too.
Split acinclude.m4 in multiple macro files.
Let it be known to autoconf and aclocal to use the m4 directory.
Ignore macro files copied or linked by libtool and intltool.
