summaryrefslogtreecommitdiff
path: root/PLUGINS.html
diff options
context:
space:
mode:
authorKlaus Schmidinger <vdr@tvdr.de>2013-02-01 12:57:53 +0100
committerKlaus Schmidinger <vdr@tvdr.de>2013-02-01 12:57:53 +0100
commitbb7d8b3b5bdf35ff088c90120cd60c0e9c532e0c (patch)
treeb7bbee8ac0a0c71292c34a093c799649a2bca4d6 /PLUGINS.html
parent45f660e35894902316045782232cb5a95a971212 (diff)
downloadvdr-bb7d8b3b5bdf35ff088c90120cd60c0e9c532e0c.tar.gz
vdr-bb7d8b3b5bdf35ff088c90120cd60c0e9c532e0c.tar.bz2
Added some notes about plugin Makefiles to PLUGINS.html
Diffstat (limited to 'PLUGINS.html')
-rw-r--r--PLUGINS.html8
1 files changed, 7 insertions, 1 deletions
diff --git a/PLUGINS.html b/PLUGINS.html
index 0c7d223a..fafd6feb 100644
--- a/PLUGINS.html
+++ b/PLUGINS.html
@@ -173,9 +173,15 @@ The <tt>src</tt> directory contains one subdirectory for each plugin, which carr
the name of that plugin (in the above example that would be <tt>hello</tt>).
What's inside the individual source directory of a
plugin is entirely up to the author of that plugin. The only prerequisites are
-that there is a <tt>Makefile</tt> that provides the targets <tt>all</tt> and
+that there is a <tt>Makefile</tt> that provides the targets <tt>all</tt><modified>, <tt>install</tt></modified> and
<tt>clean</tt>, and that a call to <tt>make all</tt> actually produces a dynamically
loadable library file for that plugin (we'll get to the details later).
+<modified>
+The dynamically loadable library file for the plugin shall be located directly under
+the plugin's source directory.
+See the section <a href="#Initializing a new plugin directory">Initializing a new plugin directory</a>
+for how to generate an example Makefile.
+</modified>
<p>
The <tt>lib</tt> directory contains the dynamically loadable libraries of all
available plugins. Note that the names of these files are created by concatenating