Commit graph

58 commits

Author SHA1 Message Date
Andy Wingo
1f0374782c fix refcounting tests so that they compile and run, but they fail currently: gst leaks obscene amounts of memory ;) f...
Original commit message from CVS:
* fix refcounting tests so that they compile and run, but they fail currently:
gst leaks obscene amounts of memory ;)
* fix plugin loading test so that it only refers to plugins within the gstreamer/
tree
* store gst plugin paths in the registry
* is GST_REGISTRY is set, only use the user registry with the PLUGIN_PATH explictly
specified by the user
* all tests should pass now except refcounting
2002-05-11 20:30:05 +00:00
Wim Taymans
2314c02f42 Small fixes for testsuite/plugin
Original commit message from CVS:
Small fixes for testsuite/plugin
2002-05-10 19:23:18 +00:00
Andy Wingo
e0a3d5eaf8 added a get_perms_func to gstxmlregistry that will set _WRITABLE and _READABLE as appropriate added an object propert...
Original commit message from CVS:
* added a get_perms_func to gstxmlregistry that will set _WRITABLE and _READABLE
as appropriate
* added an object property for location so that we can do some cleanup and initialization
2002-05-10 18:26:14 +00:00
Andy Wingo
fbbdca6996 GST_PLUGIN_PATH gets split into the user registry some debugging output in registry rebuilding don't go into =build, ...
Original commit message from CVS:
* GST_PLUGIN_PATH gets split into the user registry
* some debugging output in registry rebuilding
* don't go into =build, =inst, etc
* i really don't know what the current idiom is for the plugin test suites, disabling for now

still pending issues: what to do when other plugin paths are passed on the command
line for existing registries. if the existing registries were built against those
paths, the time checks work, but if not they will need to be rebuilt. i have a feeling
they should be rebuilt in any case, but it's a tricky issue.
2002-05-10 03:27:42 +00:00
Andy Wingo
246b03c75d Funny how doing things the right way takes less code...
Original commit message from CVS:
Funny how doing things the right way takes less code...
2002-05-10 01:24:08 +00:00
Andy Wingo
d9a656b89b Check to see if the registry is out of date, and if so try to rebuild it.
Original commit message from CVS:
Check to see if the registry is out of date, and if so try to rebuild it.

WIERD THING: trying to run gst-register using system() fails. Apparently child processes
can't link to libs parent processes use? It's wierd, and it could be a libtool issue.

That's probably just as well, it would be better just to use -register's code from within
core and not rely on another binary.
2002-05-10 01:13:40 +00:00
Ronald S. Bultje
96667dfb24 At least check whether the directory exists when creating the registry file
Original commit message from CVS:
At least check whether the directory exists when creating the registry file
2002-05-08 21:16:41 +00:00
Wim Taymans
086de421dc Totally rewritten registry handling.
Original commit message from CVS:
Totally rewritten registry handling.
- move the registry save/load code into a gstregistry subclass, this
will make it possible to use other registries (flat file, web based,
RDBMS type, etc..)
- a simple GMarkup xml registry is implemented
- use standard statically linked plugins for core elements.
- GstPlugin has a very well defined set of functions now
A little bytestream hack..
Added more info to -inspect.
Some more debugging info for clocking.
Small cleanups

I use ./gst-register --gst-plugin-path=/opt/src/sourceforge/gst-plugins/gst-libs:/opt/src/sourceforge/gst-plugins/
to register core and gst-plugins now.
2002-05-08 20:40:48 +00:00