Original commit message from CVS:
2001-02-06 Christian Schaller <Uraeus@linuxrising.org>
* Small fix to group statement for GStreamer
My work on the SPEC file making the RPM make one package for all non-core plugins is underway,
but I am not ready with it yet.
Original commit message from CVS:
Oops: fixed SDL header check: put flags in CPPFLAGS rather than CFLAGS.
We should really filter the SDL_CFLAGS and only pass appropriate options
through, but this works well enough for now.
Original commit message from CVS:
2001-01-06 Christian Schaller <Uraeus@linuxrising.org>
- First batch of upgrades to the SPEC file, this one from
Dennis Bjorklund. Thanks Dennis.
Original commit message from CVS:
2001-01-06 Christian Schaller <Uraeus@linuxrising.org>
* A few URL additions to the REQUIREMENTS file
* LICENCE readme containing licensing details on our plugins
Original commit message from CVS:
Slightly changed the README, we are not really tied to GNOME.
Added more optional libs to REQUIREMENTS. someone should complete the URLS.
Original commit message from CVS:
Add comments to many (but not all :( ) AC_DEFINES in configure scripts.
Add note about debian packages for building documentation.
Original commit message from CVS:
Abstract the plugin-srcdir installation idiottest into a separate file,
and include it from the include Makefile.am, to ensure that it gets
called at the start of a make install process, not after the whole thing
has happened.
Original commit message from CVS:
Add rules to ensure that the libgst.la and libgstelements.la exist when
trying to link the scanner with them.
Fix mkdirs so that they don't fall over if directories already exist.
Original commit message from CVS:
Add AS and ASFLAGS to configure.base, fixing the build with automake 1.4g
AS is defined in a hacky way: I've asked on the automake list for help
doing this properly.
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:
More small changes to bring the two scripts closer together.
Turned off building docs by default in configure.ac.
Only diffs are now essential due to changes from autoconf 2.13 to 2.50.
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:
Fix differences between configure.in and configure.ac which were trivial
or due merely to formatting differences. diff can now be used to see only
the significant differences, which should be helpful in keeping these
two files in sync.
Original commit message from CVS:
Update Makefile.am.future - a replacement for Makefile.am which uses
features present in recent versions of automake (>1.4d) to avoid horrendous
hackery.
Original commit message from CVS:
Simplify alsa checking: we can use the standard AM_PATH_ALSA macro to
check that we don't have alsa 0.9.x: we just need to specify something
for ACTION_NOT_FOUND to override the default AC_MSG_ERROR behaviour, so
I've put a colon for ACTION_NOT_FOUND. ;-)
Also, update the alsa macro in acinclude with the latest from the alsa
project CVS.
