mirrors/gstreamer
mirrors/gstreamer
1
1
Fork 0
mirror of https://gitlab.freedesktop.org/gstreamer/gstreamer.git synced 2025-01-25 16:48:11 +00:00
Code Issues 1 Projects Releases Wiki Activity

some cleaning

Browse source 
Original commit message from CVS:
some cleaning
This commit is contained in:
Thomas Vander Stichele 2003-01-05 22:47:42 +00:00
parent 481d542823
commit ed1a0be4b3
1 changed files with 10 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
docs/pwg/building-boiler.xml
View file

@ -265,19 +265,19 @@ U gst-template/gst-app/src/Makefile.am
<para> <para>
Once we have written code defining all the parts of the plugin, we need to Once we have written code defining all the parts of the plugin, we need to
write the plugin_init() function. This is a special function, which is write the plugin_init() function. This is a special function, which is
called as soon as the plugin is loaded, and must return a pointer to a newly called as soon as the plugin is loaded, and must return a pointer to a
allocated GstPlugin structure. This structure contains the details of all newly allocated GstPlugin structure. This structure contains the details
the facilities provided by the plugin, and is the mechanism by which the of all the facilities provided by the plugin, and is the mechanism by
definitions are made available to the rest of the &GStreamer; system. Helper which the definitions are made available to the rest of the &GStreamer;
functions are provided to help fill the structure: for future compatability system. Helper functions are provided to help fill the structure: for
it is recommended that these functions are used, as documented below, rather future compatability it is required that these functions are used, as
than attempting to access the structure directly. documented below, rather than attempting to access the structure directly.
</para> </para>
<para> <para>
Note that the information returned by the plugin_init() function will be Note that the information returned by the plugin_init() function will be
cached in a central registry. For this reason, it is important that the same cached in a central registry. For this reason, it is important that the
information is always returned by the function: for example, it must not same information is always returned by the function: for example, it
make element factories available based on runtime conditions. If an element must not make element factories available based on runtime conditions. If an element
can only work in certain conditions (for example, if the soundcard is not can only work in certain conditions (for example, if the soundcard is not
being used by some other process) this must be reflected by the element being used by some other process) this must be reflected by the element
being unable to enter the READY state if unavailable, rather than the plugin being unable to enter the READY state if unavailable, rather than the plugin