Revision: 4531 http://geany.svn.sourceforge.net/geany/?rev=4531&view=rev Author: ntrel Date: 2010-01-18 16:55:49 +0000 (Mon, 18 Jan 2010)
Log Message: ----------- Add gcc commands to build a plugin to the HowTo.
Modified Paths: -------------- trunk/ChangeLog trunk/doc/plugins.dox
Modified: trunk/ChangeLog =================================================================== --- trunk/ChangeLog 2010-01-17 21:55:46 UTC (rev 4530) +++ trunk/ChangeLog 2010-01-18 16:55:49 UTC (rev 4531) @@ -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. + + 2010-01-17 Enrico Tröger <enrico(dot)troeger(at)uvena(dot)de>
* scripts/plugin_test.c:
Modified: trunk/doc/plugins.dox =================================================================== --- trunk/doc/plugins.dox 2010-01-17 21:55:46 UTC (rev 4530) +++ trunk/doc/plugins.dox 2010-01-18 16:55:49 UTC (rev 4531) @@ -481,6 +481,20 @@ } * @endcode * + * @section building Building + * @code gcc -c plugin.c -fPIC `pkg-config --cflags geany` @endcode + * + * to make plugin.o, then: + * + * @code gcc plugin.o -o plugin.so -shared `pkg-config --libs geany`@endcode + * + * to make the plugin library plugin.so (or plugin.dll on Windows). + * + * Then just put the library into one of the paths Geany looks for plugins in, e.g. $prefix/lib/geany. + * See @ref paths "Installation paths" for details. + * + * @section realfunc Real functionality + * * If you think this plugin seems not to implement any functionality right now and only wastes * 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?
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.