[gst-devel] configure.base cleanup

[Erik Walthinsen]

The configure.base file is once again in need of some major cleanup.  In
an earlier mail I proposed a standard structure for checking for dependent
libraries, and Richard suggested an m4 macro.  I'll reply to his mail soon
with some comments, but the idea is sound.

Even with that, we're left with a *huge* configure.base file.  The only
packages on my system that beat us are gcc, SDL (huge amount of per-arch
stuff), glib (arch-specific stuff), kdelibs, and the gnome-vfs-extras
samba stuff.

I've made a list of the major sections and such, with a few comments:


Initialization
	package, version definitions
	libtool versions
Fundamental tools checks
	cc, cxx, cxxpp, isc_posic,headers, etc.
	libtool
Tools
	nasm
	gtkdoc, docbook, fig2dec
Architecture determination
	mmx...			# I'd like to move this out to 'SpeciaLib'
Essential libraries
	glib2 / glib+gtk	# this is nasty because we have to pick
	gnome			# is this the right place for this check?
	libxml
Optional library checks
	esd
	artsc
	arts
	xmms
	asound
	libaudiofile
	gdk-pixbuf
	[gnome]			# see above
	libghttp
	libglade_gnome
	gnome-vfs
	avifile
	atomic.h		# usure if we use this atm
	X11 extensions
	Xv
	oss
	xaudio
	libmad
	libvorbis
	libjpeg
	libHermes
	libgsm
	cdparanoia
	liblame
	libshout
	mpeg2dec
	libtrp
	libraw1394
	libdv
	aalib
	openquicktime
	css
	SDL
	cdrom.h
	videodev.h
Library --enable arguments		# should be part of each check
	gdk-pixbuf, libghttp, libmmx, atomic
	etc..
Configuration
	plugin-builddir
	debug
	DEBUG				# == --enable-debug-verbose
	INFO				# == --enable-info-system
	debug-color
	profiling
	configdir=DIR
	win32-libdir=DIR
	docs-build
	plugin-docs
	tests
	examples
	loadsave			# first of the subsystem disables
	etc...
AC_DEFINEs				# should be part of each check
	gdk_pixbuf, libghhtp, libmmx, atomic.h, plugins_use_builddir
	debug (-g)
	profiling (-pg)
	xv,oss,xaudio,libmad,vorbis,libjpeg,libsdl,hermes,css,cdrom,...
	...videodev,mpeg2dec,libaudiofile,libgsm
AC_CONDITIONALs				# should be part of each check
	....
Various defines of strings
	config_dir, win32_libdir, plugins_dir, ....
Setting up CFLAGS and LIBS		# a whole 'nother mess
Warnings


Now, a lot of the goes away with an m4 macro such as Richard suggested,
and becomes rather automatic.  Getting the variable names right will be a
little tricky, but not too hard.  One useful trick might be to keep a list
of the libraries not found and the plugins based on them, and move the
warning down to the bottom with a table of lacking libraries.

Another problem is dealing with the CFLAGS and LIBS.  The current setup is
a mess, and will only get worse with the addition of various DISABLE flags
that need to be added to the CFLAGS in order to be saved off into the
-config and .pc files so other apps can disable things as appropriate.

I'm getting tired now, and have to get up early tomorrow to fly to work,
so I'll leave it at that for now.

      Erik Walthinsen <omega at temple-baptist.com> - System Administrator
        __
       /  \                GStreamer - The only way to stream!
      |    | M E G A        ***** http://gstreamer.net/ *****
      _\  /_