[Geany] geany-dev, plugins

[Nick Treleaven]

On Tue, 4 Mar 2008 14:00:22 +0100
Enrico Tröger <enrico.troeger at uvena.de> wrote:

> On Tue, 4 Mar 2008 12:18:59 +0000, Nick Treleaven
> <nick.treleaven at btinternet.com> wrote:
> 
> > OK. But I think we should install the header files for plugins with
> > the usual 'make install'. This then shows the package maintainer
> > that they could make a -dev package.
> Sure, this is what I meant below. WE have to install the required
> headers with "make install" in some usual place
> ($prefix/include/geany).

OK, I just thought I'd make it clear ;-)

> > > The only thing we have to do is to refactor some of the sources
> > > so a -dev(el) package can be created in a sane way. A sane way
> > > means that only a few headers files are necessary to be used by
> > > plugins. At the moment, plugins can use all header files from
> > > Geany. This is the easy solution but would require a dev(el)
> > > package to include all Geany header files which contain parts of
> > > the plugin API. I think this is not what we should do.
> > 
> > It depends. I don't think it's really a problem for a -dev package
> > to include most of the headers. Also it's important to keep the
> > modularisation of headers and source in the core.
> Hmmm ok. But then we have to install the headers in a subdirectory
> like "geany". If we do it this way, it shouldn't be much work at all.

Yes, I think using a geany subdirectory is best.

Regards,
Nick