Original commit message from CVS:
- do not overwrite CFLAGS/CPPFLAGS/LDFLAGS/ASFLAGS
in configure.ac - they are for users, not developers;
now it is possible for users to pass its own cflags,
i.e. ./configure CFLAGS="-march=i686 -Os"
- LIBGST_CFLAGS/LIBS contain flags to build gst;
GST_CFLAGS/LIBS contain flags to build other objects
- no CORE_CLFAGS and CORE_LIBS, use GST_CFLAGS or GST_LIBS
instead, ie:
lib_CFLAGS = $(GST_CFLAGS)
lib_LIBADD = $(GST_LIBS)
prog_LDADD = $(GST_LIBS)
- GLIB_CFLAGS/LIBS contains gtk+ flags and glib flags
when glib 1.2 used or glib 2.0 flags when glib2 is
used
- simplified SDL detection
- some am 1.5 and ac 2.52 fixes
Original commit message from CVS:
- added playondemand plugin by Leif Morgan Johnson <lmjohns3@eos.ncsu.edu>
- some fixes to int2float
- aplied a patch from wrobell <wrobell@ite.pl> that is a first attempt at
making automake 1.5 happy (gst now requires automake1.5). It's still not
perfect but it builds.
- Made the schedulers plugable. The default scheduler now lives inside a
plugin.
- Added a new mpeg1/2 parser/demuxer.
- Fixed some compiler warnings in the core libs.
- substantial work to GstThread (hopefully less race conditions). simplified
the code in GstThread a bit. A state change can now also happen in the
thread context.
- reworked the state semantics of a bin. it'll now automatically get the
highest state of its children.
- the autoplugger now nests the threads so that a state change failure of
one thread doesn't make its upstream thread lock.
- GstQueue refuses to go to PLAYING if the sinkpad is not connected. This
way the queue will not wedge in the _get lock.
- GstQueue unlocks its mutexes when going to PAUSED.
- make sure that when all elements in a bin/thread go to PAUSED, the bin
is set to PAUSED too.
- make a parent bin wait for its children to PAUSE before ending the
iteration with FALSE (EOS)
- Some changes to GstPlay to deal with EOS.
- aplied the latest patch from Zeenix to gstrtp.
end result: GstPlay doesn't crash on EOS and the pipeline is now shut down
properly.
Original commit message from CVS:
Patch from vishnu:
The attached patch adds event support to bytestream. Here's how it
works: When bytestream encounters an event, the event is saved and
it returns NULL. Then you must call a new API to retrieve the event
and handle it:
void
gst_bytestream_get_status (GstByteStream *bs,
guint32 *avail_out,
GstEvent **event_out);
Whatever is necessary to handle the event is left up to the plugin.
Once the event is retrieved then the bytestream continues as usual.
Original commit message from CVS:
Applied vishnus patch:
* Check all return codes and reliably return NULL if no more data is
available.
* Split _flush into _flush/_flush_fast. This is partly to make the code
self-documenting -- the flush in gst_bytestream_read cannot fail. Also,
this is a slight optimization.[A
