SF.net SVN: geany: branches/geany-0.18.1
ntrel at users.sourceforge.net
ntrel at xxxxx
Thu Jan 28 17:09:35 UTC 2010
Date: 2010-01-28 17:09:35 +0000 (Thu, 28 Jan 2010)
Add gcc commands to build a plugin to the HowTo.
--- branches/geany-0.18.1/ChangeLog 2010-01-28 17:08:08 UTC (rev 4581)
+++ branches/geany-0.18.1/ChangeLog 2010-01-28 17:09:35 UTC (rev 4582)
@@ -1,3 +1,9 @@
+2010-01-18 Nick Treleaven <nick(dot)treleaven(at)btinternet(dot)com>
+ * doc/plugins.dox:
+ Add gcc commands to build a plugin to the HowTo.
2009-11-12 Nick Treleaven <nick(dot)treleaven(at)btinternet(dot)com>
* tagmanager/ctags.c, tagmanager/general.h:
--- branches/geany-0.18.1/doc/plugins.dox 2010-01-28 17:08:08 UTC (rev 4581)
+++ branches/geany-0.18.1/doc/plugins.dox 2010-01-28 17:09:35 UTC (rev 4582)
@@ -441,6 +441,21 @@
* some memory, you are right. But it should compile and load/unload in Geany nicely.
* Now you have the very basic layout of a new plugin. Great, isn't it?
+ * @section building Building
+ * First make plugin.o:
+ * @code gcc -c plugin.c -fPIC `pkg-config --cflags geany` @endcode
+ * Then make the plugin library plugin.so (or plugin.dll on Windows):
+ * @code gcc plugin.o -o plugin.so -shared `pkg-config --libs geany` @endcode
+ * If all went OK, put the library into one of the paths Geany looks for plugins,
+ * e.g. $prefix/lib/geany. See @ref paths "Installation paths" for details.
+ * @section realfunc Adding functionality
* Let's go on and implement some real functionality.
* As mentioned before, plugin_init() will be called when the plugin is loaded in Geany.
@@ -514,7 +529,8 @@
* memory once your plugin is unloaded, so you don't leave any memory leaks.
* Once this is done, your first plugin is ready. Congratulations!
- * The complete listing (without comments):
+ * @section listing Complete listing (without comments)
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
More information about the Commits