Original commit message from CVS:
Revert aclocal invocation to do cat m4/*.m4 > acinclude.m4 beforehand,
rather than adding m4/ to aclocal search path. Shouldn't cause errors when
macros are already present on system, because macros in acinclude.m4 are
used in preference.
Original commit message from CVS:
fix for libtool issue which has been fixed in cvs (of libtool)
until packages are available, we'd probably do best to keep ltmain.sh in CVS and not run libtoolize in autogen.sh
Original commit message from CVS:
* changed -d configure option to --autogen-debug
* added --autogen-noconfigure option that skips the configure stage
* added --autogen-nocheck to skip version checks
* cleared a little bit of kruft
Original commit message from CVS:
* removed gstreamer.m4 (packages should use pkg.m4)
* guilaunch depends only on gtk, not libglade-gnome
* removed an unnecessary check in dynamic-pipeline.c
* attempted to avoid a spurious autoheader run
* gtk2 fixes
* killed a lot of files that automake brings in for us
* killed acinclude.m4, it's autogenerated
Original commit message from CVS:
* minor typographical change to autogen
* added --with-html-dir option to configure
* more robust docbook checks
* convert to standard docbook makefiles, at least for the gst/ directory
* added filesrc.h so that docbook can know about filesrc
* updated -sections.txt because docbook is incredibly stupid and requires that at
least one of the lines between <section> and </section> is not an entity
* first pass at possible getting the docs to build on glib2, untested
Original commit message from CVS:
Added feature check macro, GST_CHECK_FEATURE.
Moved generation of configure.{in,ac} into a separate script.
Add hack to the script to stop automake complaining about missing
AM_CONDITIONAL call.
Replace ESD check by a call to GST_CHECK_FEATURE.
Original commit message from CVS:
Reworked the arguments for DEBUG and INFO. Removed -debug-verbose.
Renamed GST_DISABLE_XML to GST_DISABLE_LOADSAVE and added --disable flag.
Original commit message from CVS:
Don't ever run if we know automake isn't patched: people keep complaining
that their machine crashed while trying to build...
Original commit message from CVS:
Clarify the messages about the patched automake one more time.
If it's not clear now, and people continue to complain about automake
eating their resources, I'm mysteriously unable to hear them.
Original commit message from CVS:
Automatically generate a patched automake if needed, and put instructions
in the README about how to use such a patched automake.
Original commit message from CVS:
* create a configure.base file, containing the contents of
configure.{in,ac}, with those lines specific to one file prepended by
"SUBSTFOR configure.in:" or "SUBSTFOR configure.ac:" appropriately.
* Add lines to autogen.sh to generate configure.in and configure.ac
automatically from this file. (Very simple sed scripts)
* Remove configure.in and configure.ac
This shouldn't cause any problems to anyone, and should make it easy to do
work on configure scripts by just working on configure.base.
Original commit message from CVS:
Deal more gracefully with being either unable to check that automake is
patched (will now just give a small warning), or finding that automake
definitely isn't patched (will give a big loud warning recommend stopping
the build and sleep briefly to give the user a chance to read the message).
Will eventually try to do the build anyway though.
Also, don't abort if autoconf or automake return error codes: they both
seem able to do so even when having produced viable results.
Original commit message from CVS:
Add checks for appropriate versions of automake.
Add check that automake has been patched if it is a version which requires
a patch.
Please check that this doesn't cause problems: it's a bit of a hairy test,
so I might well have mucked it up and broken some people's build systems.
Hope not, though. ;-)
