[gst-devel] Problem with alsa.m4
omega at temple-baptist.com
Sat Jan 13 10:28:50 CET 2001
I noticed that alsa.m4 (as of Nov 20, 2000 CVS), will put the ALSA_LIBS
and ALSA_CFLAGS contents into the main LIBS and CFLAGS unconditionally,
which is quite different than any other package out there. I consider
this to be a problem, because I need to be able to choose whether to link
against libasound on a .so-by-.so basis, since I have a core library with
no major dependencies and an ALSA plugin to do all the work.
The usual way is to set just the ALSA_* vars, and let the application's
configure.in decide where/when to add them to the LIBS and CFLAGS. As it
is, I'm going to have to do the ac_save_* trick around the ALSA check.
I'm not sure what the state of HEAD is, but from the comments it looks
like it is still the same way. However, I can't check because the wbcvs
interface is broken (no perms to write history).
Erik Walthinsen <omega at temple-baptist.com> - System Administrator
/ \ GStreamer - The only way to stream!
| | M E G A ***** http://gstreamer.net/ *****
More information about the gstreamer-devel