Original commit message from CVS:
* removal of //-style comments
* don't link plugins to core libs -- the versioning is done internally to the plugins with the plugin_info struct,
and symbol resolution is lazy, so we can always know if a plugin can be loaded by the plugin_info data. in theory.
Original commit message from CVS:
s/@GST_PLUGIN_LDFLAGS@/$(GST_PLUGIN_LDFLAGS)/
@-substitued variables variables are defined as make variables automagically,
and this gives the user the freedom to say make GST_PLUGIN_LDFLAGS=-myflag
Original commit message from CVS:
* s/gst_element_install_std_props/gst_element_class_install_std_props/ -- it just makes more sense that way
* added jack element, doesn't quite work right yet but i didn't want to lose the work -- it does build, register,
and attempt to run though
* imposed some restrictions on the naming of request pads to better allow for reverse parsing
* added '%s' to reverse parsing
* added new bin flag to indicate that it is self-iterating, and some lame code in gst-launch to test it out
* fixen on launch-gui
* added pkg-config stuff for the editor's libs
Original commit message from CVS:
* get up-to-date with the gst_caps_debug api
* improved capsnego in mad
* improved capsnego in adder
* improved capsnego in intfloat plugins
* unbroke capsnego in stereomono plugins
* fix cothread stack allocation within the main thread in new cothreads
Original commit message from CVS:
* on sink connect, check if the current pad is compatible with the given
caps
* cleaned up debug output
* change pad template to only accept allowed sample rates
if these changes are considered ok by others then the same should be
applied to other encoding plugins (notably the compatibility check)
Original commit message from CVS:
somebody help me fix lame ;)
I commented out the state change function because it is called before lame has the right caps.
Is the state change function still necessary ?
in any case, at least now lame actually listens to osssrc re: rate and channels
Original commit message from CVS:
I checked lame packages and source code and they seem to want lame.h in
prefix/include/lame.h
so I fixed stuff accordingly.
Do any systems have lame in include/lame/lame.h ?
If so, mail me and we'll work it out.
Original commit message from CVS:
- use MPEG2DEC_CFLAGS and MPEG2DEC_LIBS which are set with
GST_CHECK_MPEG2DEC macro
- gcc -O3 option removed - it is set by the user if he wants such
optimization
Original commit message from CVS:
... and cvs commits should not be allowed for people who spent six hours
on the phone talking to hardware vendors and struggling with failing raid
systems
Original commit message from CVS:
how do people expect sdl to build if make has no way of getting to the dir
and we don't point it in the right direction ?
Original commit message from CVS:
new policy: demos and tests in plugin dirs, named demo- if they are just demonstrations and
test- if they are regression tests. following the dasho should be a description of the demo or
test.
Original commit message from CVS:
muahahahaha. gstreamer-compprep initializes every plugin so it's a good way
of figuring out plugin issues. it spits out no more errors now.
