On 11 March 2010 11:40, Chuck Tilbury chucktilbury@gmail.com wrote:
On Wed, Mar 10, 2010 at 6:16 PM, Lex Trotman elextr@gmail.com wrote:
<snip>
Aha,
I assume this means that you have more than one Geany at different prefixes?
There is a problem with plugins in that situation, the autoconf/make builder gets the wrong prefix and so makes the plugins with the wrong version. But since you made the demoplugin separately it works ok.
This bug has been raised to the autoconf maintainer but I've not seen it fixed. AFAIK the WAF builder works ok so you might want to use that.
Cheers Lex
PS ignore my comment about .lo and .la files, I wasn't paying attention, they are of course libtool files. But they "shouldn't" be needed to run just to link.
So I will clean out the previous install and reinstall. That should fix the issue, correct?
The only files that I know of are in these areas: /usr/bin/geany /usr/lib/geany/ /usr/lib/geany-plugins/ /home/me/.config/geany/
Is there anything else?
-=c=-
You could try make uninstall :-)
Well a nice clean install allways helps :-), but it HAS to be the same version as you are building the plugin for since the autotools is hard coded to use the standard Geany prefix for plugins.
As I said above I am told by "Prolific Plugin Programmers" that the waf version will handle plugins properly to any prefix, but I havn't used it yet.
Cheers Lex
PS please reply to the list, not to me, so other people can see and interrupt any time either of us is talking garbage :-)
On Wed, Mar 10, 2010 at 7:52 PM, Lex Trotman elextr@gmail.com wrote:
On 11 March 2010 11:40, Chuck Tilbury chucktilbury@gmail.com wrote:
On Wed, Mar 10, 2010 at 6:16 PM, Lex Trotman elextr@gmail.com wrote:
<snip>
Aha,
I assume this means that you have more than one Geany at different prefixes?
There is a problem with plugins in that situation, the autoconf/make builder gets the wrong prefix and so makes the plugins with the wrong version. But since you made the demoplugin separately it works ok.
This bug has been raised to the autoconf maintainer but I've not seen it fixed. AFAIK the WAF builder works ok so you might want to use that.
Cheers Lex
PS ignore my comment about .lo and .la files, I wasn't paying attention, they are of course libtool files. But they "shouldn't" be needed to run just to link.
So I will clean out the previous install and reinstall. That should fix the issue, correct?
The only files that I know of are in these areas: /usr/bin/geany /usr/lib/geany/ /usr/lib/geany-plugins/ /home/me/.config/geany/
Is there anything else?
-=c=-
You could try make uninstall :-)
Well a nice clean install allways helps :-), but it HAS to be the same version as you are building the plugin for since the autotools is hard coded to use the standard Geany prefix for plugins.
As I said above I am told by "Prolific Plugin Programmers" that the waf version will handle plugins properly to any prefix, but I havn't used it yet.
Cheers Lex
PS please reply to the list, not to me, so other people can see and interrupt any time either of us is talking garbage :-) ((sorry, I thought I was.))
My problem was that I first installed the Ubuntu package from the package repository. It worked fine, but there was the build confusion. I removed the package and then did a "make uninstall" to get it right. I built it from the source available in the web page and the demo plugin now loads and seems fine.
I had another problem with building the add-ons, though. After taking care of the dependencies given by ./configure, I tried to get and build the geany-plugins-0.18 files and many of the plugins refused to build because of inaccessible header files. I created a directory of /usr/include/geany and copied the files from .../geany_svn/src/*.h there, but there are still others that appear to be missing and that I don't have installed anywhere. The plugins that failed are: # addons \ # geanydoc \ # geanylipsum \ # geanylua \ The others seem OK. Sorry, I don't have time to give more information. :( I gotta think that this is probably a issue that has already been looked at.
It looks like I have enough to get started on a macro recorder. Am I correct in thinking that the demo plugin has the correct message loop that I want to tap into?
Thanks, -=chuck=-
On 11 March 2010 13:13, Chuck Tilbury chucktilbury@gmail.com wrote:
On Wed, Mar 10, 2010 at 7:52 PM, Lex Trotman elextr@gmail.com wrote:
On 11 March 2010 11:40, Chuck Tilbury chucktilbury@gmail.com wrote:
On Wed, Mar 10, 2010 at 6:16 PM, Lex Trotman elextr@gmail.com wrote:
<snip>
Aha,
I assume this means that you have more than one Geany at different prefixes?
There is a problem with plugins in that situation, the autoconf/make builder gets the wrong prefix and so makes the plugins with the wrong version. But since you made the demoplugin separately it works ok.
This bug has been raised to the autoconf maintainer but I've not seen it fixed. AFAIK the WAF builder works ok so you might want to use that.
Cheers Lex
PS ignore my comment about .lo and .la files, I wasn't paying attention, they are of course libtool files. But they "shouldn't" be needed to run just to link.
So I will clean out the previous install and reinstall. That should fix the issue, correct?
The only files that I know of are in these areas: /usr/bin/geany /usr/lib/geany/ /usr/lib/geany-plugins/ /home/me/.config/geany/
Is there anything else?
-=c=-
You could try make uninstall :-)
Well a nice clean install allways helps :-), but it HAS to be the same version as you are building the plugin for since the autotools is hard coded to use the standard Geany prefix for plugins.
As I said above I am told by "Prolific Plugin Programmers" that the waf version will handle plugins properly to any prefix, but I havn't used it yet.
Cheers Lex
PS please reply to the list, not to me, so other people can see and interrupt any time either of us is talking garbage :-) ((sorry, I thought I was.))
My problem was that I first installed the Ubuntu package from the package repository. It worked fine, but there was the build confusion. I removed the package and then did a "make uninstall" to get it right. I built it from the source available in the web page and the demo plugin now loads and seems fine.
I had another problem with building the add-ons, though. After taking care of the dependencies given by ./configure, I tried to get and build the geany-plugins-0.18 files and many of the plugins refused to build because of inaccessible header files. I created a directory of /usr/include/geany and copied the files from .../geany_svn/src/*.h there, but there are still others that appear to be missing and that I don't have installed anywhere. The plugins that failed are: # addons \ # geanydoc \ # geanylipsum \ # geanylua \ The others seem OK. Sorry, I don't have time to give more information. :( I gotta think that this is probably a issue that has already been looked at.
Don't know, maybe someone else can help. Or maybe these plugins are not (yet) compatible with the SVN version??
It looks like I have enough to get started on a macro recorder.
For development should be ok if you do it like the demoplugin, ie make myplugin; cp myplugin.so prefix/plugins
Am I correct in thinking that the demo plugin has the correct message loop
that I want to tap into?
I presume you mean the on_editor_notify function.
If so no, lots of key presses don't get there, for example all Geany defined keybindings, see on_key_press_event in keybindings.c and you will see that keybindings don't get to fall through to the editor.
My plan was to use gtk emission hooks see http://www.geany.org/manual/gtk/gobject/gobject-Signals.html#g-signal-add-em... to get the keypress events, and then replay the events using one of the g_signal_emit variants.
Thats as far as my thinking got
Cheers Lex
Thanks, -=chuck=-
Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
On Wed, 10 Mar 2010 20:13:59 -0600 Chuck Tilbury chucktilbury@gmail.com wrote:
I had another problem with building the add-ons, though. After taking care of the dependencies given by ./configure, I tried to get and build the geany-plugins-0.18 files and many of the plugins refused to build because of inaccessible header files. I created a directory of /usr/include/geany and copied the files from .../geany_svn/src/*.h there, but there are still others that appear to be missing and that I don't have installed anywhere. The plugins that failed are: # addons \ # geanydoc \ # geanylipsum \ # geanylua \ The others seem OK. Sorry, I don't have time to give more information. :( I gotta think that this is probably a issue that has already been looked at.
You need geany-plugins SVN for geany SVN to be compatible.
g-p 0.18 is only compatible with geany 0.18, 0.18.x.
Regards, Nick
On Wed, 10 Mar 2010 20:13:59 -0600 Chuck Tilbury chucktilbury@gmail.com wrote:
On Wed, Mar 10, 2010 at 7:52 PM, Lex Trotman elextr@gmail.com wrote: I removed the package and then did a "make uninstall" to get it right. I built it from the source available in the web page and the demo plugin now loads and seems fine.
Which version of Geany did you install?
I had another problem with building the add-ons, though. After taking care of the dependencies given by ./configure, I tried to get and build the geany-plugins-0.18 files and many of the plugins refused to build because of inaccessible header files.
If you are using Geany 0.19 it most likely will not compile 0.18th release plugins. You will also need to configure and build current svn version of geany-plugins.
I created a directory of /usr/include/geany and copied the files from .../geany_svn/src/*.h there, but there are still others that appear to be missing and that I don't have installed anywhere. The plugins that failed are: # addons \ # geanydoc \ # geanylipsum \ # geanylua \
This shouldn't be needed, as make install is doing this already.
It looks like I have enough to get started on a macro recorder. Am I correct in thinking that the demo plugin has the correct message loop that I want to tap into?
The demo plugi is a first step into building a plugin. Reading http://www.geany.org/manual/reference/howto.html might also be a good idea for the start.
Of course, reading all the plugins inside geany-plugins in case of any qeustion might can help you - as well as asking on geany-devel mailing list ;)
Cheers, Frank