From 0f9fb7d8844569db8d7205ca846062215fe18d24 Mon Sep 17 00:00:00 2001 From: Wim Taymans Date: Fri, 12 Oct 2012 13:13:32 +0200 Subject: [PATCH] manual: move embedding elements to separate chapter --- docs/manual/advanced-dataaccess.xml | 68 -------------------------- docs/manual/appendix-compiling.xml | 76 +++++++++++++++++++++++++++++ docs/manual/manual.xml | 2 + 3 files changed, 78 insertions(+), 68 deletions(-) create mode 100644 docs/manual/appendix-compiling.xml diff --git a/docs/manual/advanced-dataaccess.xml b/docs/manual/advanced-dataaccess.xml index b57f25b91a..983d757183 100644 --- a/docs/manual/advanced-dataaccess.xml +++ b/docs/manual/advanced-dataaccess.xml @@ -1572,72 +1572,4 @@ main (int argc, char **argv) - - Embedding static elements in your application - - The Plugin - Writer's Guide describes in great detail how to write elements - for the &GStreamer; framework. In this section, we will solely discuss - how to embed such elements statically in your application. This can be - useful for application-specific elements that have no use elsewhere in - &GStreamer;. - - - Dynamically loaded plugins contain a structure that's defined using - GST_PLUGIN_DEFINE (). This structure is loaded - when the plugin is loaded by the &GStreamer; core. The structure - contains an initialization function (usually called - plugin_init) that will be called right after that. - It's purpose is to register the elements provided by the plugin with - the &GStreamer; framework. - If you want to embed elements directly in - your application, the only thing you need to do is to replace - GST_PLUGIN_DEFINE () with a call to - gst_plugin_register_static (). As soon as you - call gst_plugin_register_static (), the elements - will from then on be available like any other element, without them - having to be dynamically loadable libraries. In the example below, you - would be able to call gst_element_factory_make - ("my-element-name", "some-name") to create an instance of the - element. - - - - - - diff --git a/docs/manual/appendix-compiling.xml b/docs/manual/appendix-compiling.xml new file mode 100644 index 0000000000..2d83c989be --- /dev/null +++ b/docs/manual/appendix-compiling.xml @@ -0,0 +1,76 @@ + + Compiling + + This section talks about the different things you can do when building + and shipping your applications and plugins. + + + + Embedding static elements in your application + + The Plugin + Writer's Guide describes in great detail how to write elements + for the &GStreamer; framework. In this section, we will solely discuss + how to embed such elements statically in your application. This can be + useful for application-specific elements that have no use elsewhere in + &GStreamer;. + + + Dynamically loaded plugins contain a structure that's defined using + GST_PLUGIN_DEFINE (). This structure is loaded + when the plugin is loaded by the &GStreamer; core. The structure + contains an initialization function (usually called + plugin_init) that will be called right after that. + It's purpose is to register the elements provided by the plugin with + the &GStreamer; framework. + If you want to embed elements directly in + your application, the only thing you need to do is to replace + GST_PLUGIN_DEFINE () with a call to + gst_plugin_register_static (). As soon as you + call gst_plugin_register_static (), the elements + will from then on be available like any other element, without them + having to be dynamically loadable libraries. In the example below, you + would be able to call gst_element_factory_make + ("my-element-name", "some-name") to create an instance of the + element. + + + + + + + diff --git a/docs/manual/manual.xml b/docs/manual/manual.xml index 2d1ec9aff5..6462cccc0f 100644 --- a/docs/manual/manual.xml +++ b/docs/manual/manual.xml @@ -52,6 +52,7 @@ + @@ -257,6 +258,7 @@ --> &PROGRAMS; + &COMPILING; &CHECKLIST; &PORTING; &INTEGRATION;