[Geany-devel] Plugins build system

Nick Treleaven nick.treleaven at xxxxx
Fri Jun 6 13:12:02 UTC 2008

On Fri, 6 Jun 2008 13:28:03 +0100
Nick Treleaven <nick.treleaven at btinternet.com> wrote:

> Hmm, I wonder what other projects do.
> One thing I've thought about is just to have a single configure.in for
> all plugins, with some way to tell ./configure which plugins to build,
> perhaps a way to only build one or a named set to build. This might
> have the advantage of a single config.h and translation support. The
> disadvantage might not be important - that to build you have to have
> all the plugins on disk, you can't just checkout a single plugin
> folder. If you have an option like
> --enable-plugins='spellcheck,geanydoc', this might not be a problem.

(http://audacious-media-player.org/index.php?title=Downloads) does
this, a single configure.ac. It has separate arguments for plugins,
like --enable-esd. It doesn't use 

It also uses buildsys to generate the autotools files:

I couldn't find much descriptive info about it, but it seems to be like
wxWidgets' Bakefile system. The advantage of this is that users can have
less dependencies - e.g. just use a free IDE to build on Windows, but
I'm not sure if it would help in our case.

Mainly I just wanted to mention that it uses a unified configure
script, and a common po/ directory.


More information about the Devel mailing list