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. ;-)
Original commit message from CVS:
Collection of minor changes:
* autogen.sh - remove config.cache before running ./configure
* gst/elements/gstfakesink.c - print out the size of the buffer, too
* plugins/Makefile.am - removed a spare trailing backslash
* plugins/arts/gst_artsio_impl.cc - change the scale back to 0.5
* plugins/oss/gstosssrc.c - change name slightly to match osssink
Original commit message from CVS:
Added a check for libjpeg
Added and action for the load menu in gstplay
Fixed drag and drop in gstplay
More verbose errors in gstasyndisksrc
Original commit message from CVS:
Massive, massive update of most source files. I went through and cleaned
up all the warnings that I could, which involved fixing some of the plugins.
The configure.in script was re-arranged and cleaned up so, and a check for
libtool 1.3.5 was added to autogen.sh. Added checks for Gtk and GNOME.
Some plugins were removed from the list of things to build for various reasons.
Added GST_DEBUG_FORCE_DISABLE in gstgetbits, since that's time critical and
even an if() from a DEBUG can significantly increase runtimes.
Original commit message from CVS:
Fix compile problem due to DEBUG being redefined in
libs/getbits/gstgetbits.h. Also fix several small typos in the docs and
examples.
Original commit message from CVS:
Fix on x86 architectures - was just checking for 386, D'oh.
Fix autogen to run autoheader _before_ autoconf, since it generates a
required file (config.h.in, which I just removed from CVS since its an
autogenerated one). Also fix messed up variables in gst/Makefile.am
Original commit message from CVS:
Build fixes.
Adapted the test directory to the new state management
added an mpeg2 to avi encoder.
added a v4l to divx capture example.
Original commit message from CVS:
Megapatch, changes which states are available, how they're used, and how
they're set. Also modifies the scheduling system, breaking pulled
buffers. Check mail archives for more details.
