Hi,
since 2333, "make install" will also install all header files which can be used in plugins and additionally a pkg-config file is installed. This means for plugin authors, they can query the necessary CFLAGS and LDFLAGS for compiling their sources. This makes it quite easy to use the autotools for configuring the plugin sources. The package name for pkg-config is "geany".
This makes it also possible to create -dev or -devel packages of Geany which would allow a user to compile plugins for Geany without to have the full sources installed.
At the moment, all Geany header files are installed in $prefix/include/geany and a few Scintilla header files in $prefix/include/geany/scintilla and the tagmanager header files are installed in $prefix/include/geany/tagmanager. All include paths can be obtained with pkg-config --cflags geany
I think this is the cleanest solution. Or would it be better to have _all_ header files(Geany ones mixed with Scintilla and tagmanager) in $prefix/include/geany?
Additionally, I only added SciLexer.h, Scintilla.h and ScintillaWidget.h to the list of installed header files from Scintilla. But I think plugins won't use anything from the other files directly. Let me know if I'm wrong.
Attached is a patch against the geanyvc plugin which I used for testing ;-).
Regards, Enrico
On Thu, 13 Mar 2008 13:29:32 +0100 Enrico Tröger enrico.troeger@uvena.de wrote:
since 2333, "make install" will also install all header files which can be used in plugins and additionally a pkg-config file is installed.
Great work :)
...
At the moment, all Geany header files are installed in $prefix/include/geany and a few Scintilla header files in $prefix/include/geany/scintilla and the tagmanager header files are installed in $prefix/include/geany/tagmanager. All include paths can be obtained with pkg-config --cflags geany
I think this is the cleanest solution. Or would it be better to have _all_ header files(Geany ones mixed with Scintilla and tagmanager) in $prefix/include/geany?
I prefer it like it is, with separate directories.
Regards, Nick
On Thu, Mar 13, 2008 at 12:37 PM, Nick Treleaven nick.treleaven@btinternet.com wrote:
Great work :)
I agree :)
I prefer it like it is, with separate directories.
Me too.
- Jeff
On Thu, 13 Mar 2008 14:00:29 -0500 "Jeff Pohlmeyer" yetanothergeek@gmail.com wrote:
On Thu, Mar 13, 2008 at 12:37 PM, Nick Treleaven nick.treleaven@btinternet.com wrote:
Great work :)
I agree :)
I prefer it like it is, with separate directories.
Me too.
Yes, cool. It is possible to write ebuild, PKGBUILD and SPEC files for plugins now.
On Thu, 13 Mar 2008 22:04:33 +0200, Yura Siamashka yurand2@gmail.com wrote:
On Thu, 13 Mar 2008 14:00:29 -0500 "Jeff Pohlmeyer" yetanothergeek@gmail.com wrote:
On Thu, Mar 13, 2008 at 12:37 PM, Nick Treleaven nick.treleaven@btinternet.com wrote:
Great work :)
I agree :)
I prefer it like it is, with separate directories.
Me too.
Yes, cool. It is possible to write ebuild, PKGBUILD and SPEC files for plugins now.
That's feedback I like ;-).
Regards, Enrico
On Thu, 13 Mar 2008 13:29:32 +0100 Enrico Tröger enrico.troeger@uvena.de wrote:
Attached is a patch against the geanyvc plugin which I used for testing ;-).
Nice, thanks. ;-). commited in git.
Hi
I can't compile geanyprj with pkg-config because geany install doesn't include prefs.h. This make plugin macros "prefs" useless.
Please include it in install. Patch attached.
On Fri, 14 Mar 2008 00:15:40 +0200, Yura Siamashka yurand2@gmail.com wrote:
Hi
I can't compile geanyprj with pkg-config because geany install doesn't include prefs.h. This make plugin macros "prefs" useless.
Please include it in install. Patch attached.
Oops. I assumed I forget something ;-(. Done, thanks for the patch.
Regards, Enrico
On Thu, 13 Mar 2008 13:29:32 +0100, Enrico Tröger enrico.troeger@uvena.de wrote:
Hi,
since 2333, "make install" will also install all header files which can be used in plugins and additionally a pkg-config file is installed. This means for plugin authors, they can query the necessary CFLAGS and LDFLAGS for compiling their sources. This makes it quite easy to use the autotools for configuring the plugin sources. The package name for pkg-config is "geany".
Since SVN r2428 the pkgconfig file also contains the datadir and localedir.
Plugin authors can query these values with: pkg-config --variable=prefix geany pkg-config --variable=libdir geany pkg-config --variable=datadir geany pkg-config --variable=localedir geany
This should be used instead of the "geany --print-prefix" command which might be removed in future versions.
Regards, Enrico