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:
miscellaneous fixes, added gst_pad_unset_sched() api.
although I unref the old pipeline and the cothread context gets freed in dynamic-pipeline.c,
I still get segfaults.
Original commit message from CVS:
added a slightly new twist in dynamic-pipeline.c: I actually iterate the first pipeline.
this causes a segfault (at least on my machine, i've been having link issues today though).
if a scheduler wizard (ahem) could take at glance at this, i'd be eternally grateful :-)
Original commit message from CVS:
summary: fix xml in gstreamer
1) make clear distinction between loading xml that actually creates objects and loading xml that just
synchronizes properties with objects. moved most of gst_element_restore_thyself functionality to
gst_xml_make_element. this new function name can change if it sucks.
2) many various fixes. createxml and runxml work now.
3) doc updates.
4) GstSignalObject is stil broken. i have no idea what it's supposed to do.
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:
fixed mainloop for non-glib2
this is a hack, we really need to fix this properly so i don't have to do this in every file
Original commit message from CVS:
i've added a testcase where the scheduler fails. i don't know enough about
the scheduler to fix it, though. the sequence goes:
- make a pipeline, iterate it once
- re-use one of the elements in a new pipeline, see if it works
