[Geany-devel] Plugins build system

Nick Treleaven nick.treleaven at xxxxx
Fri Jun 6 16:04:20 UTC 2008

On Fri, 6 Jun 2008 16:26:21 +0300
"Yura Siamashka" <yurand2 at gmail.com> wrote:

> Hi
> >> First it was easier than I expected but it's still not working as
> >> I'd wish.
> >> Basically it's enough to create a simple configure.in and list the
> >> plugins' makefiles in it. autogen.sh does the rest by walking any
> >> subdirectories and init them if there is a configure.in is found.
> >> Then the configure script is created in the top level directory
> >> and it works fine, make will then build each plugin below.
> >> So far it's pretty cool.
> One configure.in is not very good solution, IMHO.
> While it is good that geany depend only on GTK+, such restriction not
> good for plugins.
> This single configure script will be VERY complex (probably hard to
> maintain)  because different plugins depend on different libraries:

As I mentioned, this is already done for audacious-plugins, and IIRC for
Pidgin, and I expect other plugin projects too. If anyone is aware
of other projects that do this differently, please let us know.

One thing that might be confusing - a geany-plugins build system would
only be for plugins that want to use it - if you just want SVN, there
would be no need to use anything above your plugin's directory.

> lua, python, ruby, gnome, kde, oracle etc. It is expected that some
> plugins will not compile on all platform, also it is expected that
> some libraries can't be linked together with other.

You could write the configure script so if Lua is not installed, just
don't build the Lua plugin, and so on.


More information about the Devel mailing list