Use plugin descriptions, which start with the major and minor version numbers,...
Use plugin descriptions, which start with the major and minor version numbers, instead of relying on each plugin to c... Original commit message from CVS: Use plugin descriptions, which start with the major and minor version numbers, instead of relying on each plugin to call gst_plugin_new appropriately, and check the return value, and tidy up if there's a failure. This seems to work fine, and factors out some code common to all plugins.
Showing
- examples/plugins/example.c 22 additions, 11 deletionsexamples/plugins/example.c
- gst/autoplug/gststaticautoplug.c 10 additions, 7 deletionsgst/autoplug/gststaticautoplug.c
- gst/autoplug/gststaticautoplugrender.c 10 additions, 7 deletionsgst/autoplug/gststaticautoplugrender.c
- gst/elements/gstelements.c 11 additions, 6 deletionsgst/elements/gstelements.c
- gst/gstplugin.c 14 additions, 5 deletionsgst/gstplugin.c
- gst/gstplugin.h 9 additions, 2 deletionsgst/gstplugin.h
- gst/types/gsttypes.c 10 additions, 7 deletionsgst/types/gsttypes.c
- plugins/elements/gstelements.c 11 additions, 6 deletionsplugins/elements/gstelements.c
- tests/old/examples/plugins/example.c 22 additions, 11 deletionstests/old/examples/plugins/example.c
Loading
Please register or sign in to comment