-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Is it possible to build an older version of Geanyvc-plugin to use with Geany 0.14, I want to do this so that I can use Geany-debug and Geanyvc at the same time :-)
If this is possible, which version of geanyvc should I use and where can I get the source for that version of Geanyvc?
/Micke
Micke Nordin schrieb:
Is it possible to build an older version of Geanyvc-plugin to use with Geany 0.14, I want to do this so that I can use Geany-debug and Geanyvc at the same time :-)
I'm using both with the SVN version. Are there known problems which hold you back from using geany-debug with a recent Geany version?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I'm using both with the SVN version. Are there known problems which hold you back from using geany-debug with a recent Geany version?
Yes, the website says that it can only be used with 0.14:
http://www.geany.org/Support/Plugins
But I did try to download the tarball and build it using the geany 0.15 sources (which of course did not work, as the website had allready told me). But maybe I missunderstood and there is an alternate way for me to download sources for the debugger plugin that will work in geany 0.15? Will the svn version work for instance (I guess I'll just try and see what happenes)?
The reason I would prefer the 0.14 version of geany is that I can apt-get that one from the Ubuntu repositories, and 0.15 I can get from getdeb, which is not as convinient as getting it from the Ubuntu repos, but still better than building geany from sources :-) But if I can get all plugins to work only from the latest sources, that's what i'll do then of course.
On Thu, 11 Dec 2008 16:47:07 +0100 Micke Nordin mickewiki@gmail.com wrote:
Will the svn version work for instance (I guess I'll just try and see what happenes)?
Plugin SVN will probably only work with Geany SVN, but you could try it, or find an older revision that works with 0.15.
Regards, Nick
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Nick Treleaven skrev:
Plugin SVN will probably only work with Geany SVN, but you could try it, or find an older revision that works with 0.15.
I must be realy, realy stupid.
Now I have compiled geany, geanydbg and geanyvc from svn and I can choose both geanyvc and geanydbg from the plugin-manager. I find geanyvc under the tool-menu, but I get no debugging tab, like I used to have back in geany 0.14. Has the debugger moved or have I made som kind of misstake installing?
It seems strange to me that I can choose the plugin, but it doesnt show up anywhere...
/Micke
Am Donnerstag, den 11.12.2008, 19:51 +0100 schrieb Micke Nordin:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Nick Treleaven skrev:
Plugin SVN will probably only work with Geany SVN, but you could try it, or find an older revision that works with 0.15.
I must be realy, realy stupid.
Now I have compiled geany, geanydbg and geanyvc from svn and I can choose both geanyvc and geanydbg from the plugin-manager. I find geanyvc under the tool-menu, but I get no debugging tab, like I used to have back in geany 0.14. Has the debugger moved or have I made som kind of misstake installing?
IIRC there is a difference between geanydbg and geanydebug. You may want to get geanydebug instead of geanydbg.
It seems strange to me that I can choose the plugin, but it doesnt show up anywhere...
/Micke -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAklBYUYACgkQzdNqVVhZvLwmSgCgkwQe0k+3JpfZw34Y/9kgpPhL o0kAoIDsB83WWnIK5vDwPk1KfWz2qcug =2AKQ -----END PGP SIGNATURE-----
Geany mailing list Geany@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany
On Thu, 11 Dec 2008 19:51:50 +0100 Micke Nordin mickewiki@gmail.com wrote:
Plugin SVN will probably only work with Geany SVN, but you could try it, or find an older revision that works with 0.15.
I must be realy, realy stupid.
No, it's not your fault. It's difficult for users to install geany-plugins because we haven't made an official release.
Now I have compiled geany, geanydbg and geanyvc from svn and I can choose both geanyvc and geanydbg from the plugin-manager. I find geanyvc under the tool-menu, but I get no debugging tab, like I used to have back in geany 0.14. Has the debugger moved or have I made som kind of misstake installing?
It seems strange to me that I can choose the plugin, but it doesnt show up anywhere...
As Dominic said, the geanydbg 'DBG' plugin is not what you want.
@Yura: Could you rename this to 'External Debugger' and geanydebug to 'GDB' to avoid confusion?
Now, you might not see the geanydebug plugin because you don't have GLib 2.14 - check Help->Debug Messages, it might say:
12:53:09: INFO : Can't load plugin: /usr/local/lib/geany/geanydebug.so: undefined symbol: g_string_append_vprintf
This is because it currently requires GLib 2.14. I think I can fix this, there was a patch but it didn't get applied.
Regards, Nick
On Fri, 12 Dec 2008 13:07:27 +0000 Nick Treleaven nick.treleaven@btinternet.com wrote:
12:53:09: INFO : Can't load plugin: /usr/local/lib/geany/geanydebug.so: undefined symbol: g_string_append_vprintf
This is because it currently requires GLib 2.14. I think I can fix this, there was a patch but it didn't get applied.
I just applied the patch for the plugin. Try 'svn up' and rebuild, reinstall. Hopefully you will get a 'Debugger' plugin in the Plugin Manager.
Regards, Nick
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Nick Treleaven skrev:
No, it's not your fault. It's difficult for users to install geany-plugins because we haven't made an official release.
Official releases (and perhaps nightly snapshots) would be a realy good idea for the plugins, and also a full list of plugins on the geany website would be good, it seems not all avalible plugins are listed there.
As Dominic said, the geanydbg 'DBG' plugin is not what you want.
Yupp, I've got it up and running now.
@Yura: Could you rename this to 'External Debugger' and geanydebug to 'GDB' to avoid confusion?
Yea, perhaps a more clear name to differentiate between the plugins (along with some documentation) would be good. Is it possible to get involved with documentation of the plugins?
Also a feuture request, on a side note: I found that I can use gcj to build java-code and then use the debugger-plugin to debug javaprograms from geany, wich is excellent of course. Would it be possible to add build arguments to the "java-mode" as well, beside the compile options, in the build-menu (making the java-mode more similar to the c++-mode for example? To compile and build java with Geany I now have to put this rather complex string into the compile options: gcj -c -g -O "%f" && gcj --main="%e" -o "%e" "%e".o
Also having a dropdown menu where I can choose from different compilers would be good, so that I could easily switch between javac and gcj :)
/Micke
On Fri, 12 Dec 2008 16:20:44 +0100 Micke Nordin mickewiki@gmail.com wrote:
Is it possible to get involved with documentation of the plugins?
Yes, that'd be great. You'd need to talk to the maintainer of any plugin you want to write documentation for - I think Yura Siamashka is the maintainer of the GeanyDebug GDB plugin. I'm the de-facto maintainer for GeanyLua (but it already has documentation in SVN).
Or/also general docs for geany-plugins would be good too IMO. You could join the geany-devel list and start a thread.
The 'internal' plugins distributed with Geany are also missing some documentation from the manual: http://www.geany.org/manual/dev/index.html#plugin-documentation
Also a feuture request, on a side note: I found that I can use gcj to build java-code and then use the debugger-plugin to debug javaprograms from geany, wich is excellent of course. Would it be possible to add build arguments to the "java-mode" as well, beside the compile options, in the build-menu (making the java-mode more similar to the c++-mode for example? To compile and build java with Geany I now have to put this rather complex string into the compile options: gcj -c -g -O "%f" && gcj --main="%e" -o "%e" "%e".o
Check the manual, it should be possible to add a linker= command to your local filetypes.java, then the dialog will also show it.
Also having a dropdown menu where I can choose from different compilers would be good, so that I could easily switch between javac and gcj :)
Well, Geany will only run commands, not understand build systems, but we are working on making commands more configurable.
Regards, Nick
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Nick Treleaven skrev:
Check the manual, it should be possible to add a linker= command to your local filetypes.java, then the dialog will also show it.
This was realy easy once I had read manual :-), thanks for pointing me there
Well, Geany will only run commands, not understand build systems, but we are working on making commands more configurable.
What I ment was that I'd like to have the ability to specify two (or more) compiler=/linker=/run_cmd= sections in filetypes.* and then be able to choose which ones to use in a drop down menu, or by checking a radiobutton or something. (Luxury problems, I know, not very high up on the todo-list :-)
Another thing I found now is the "%e" doesen't return filename without filename extension as it does for c++-files, instead it returns filename + .class, so I have to build my executables with gcj - --main="%e" -o "%e.class" "%e.o" in order to be able to run gcj-built java-program with "./%e". Is this also me, doing something wrong?
/Micke
On Sat, 13 Dec 2008 14:44:29 +0100, Micke Nordin mickewiki@gmail.com wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Nick Treleaven skrev:
Check the manual, it should be possible to add a linker= command to your local filetypes.java, then the dialog will also show it.
This was realy easy once I had read manual :-), thanks for pointing me there
Well, Geany will only run commands, not understand build systems, but we are working on making commands more configurable.
What I ment was that I'd like to have the ability to specify two (or more) compiler=/linker=/run_cmd= sections in filetypes.* and then be able to choose which ones to use in a drop down menu, or by checking a
This is what is going to change as Nick mentioned.
Another thing I found now is the "%e" doesen't return filename without filename extension as it does for c++-files, instead it returns filename + .class, so I have to build my executables with gcj
- --main="%e" -o "%e.class" "%e.o" in order to be able to run gcj-built
java-program with "./%e". Is this also me, doing something wrong?
Hmm, it shouldn't append ".class" to %e, it only does this while preparing the execution to verify that the current source file already has been compiled (which means for javac a .class file exists). When using gcj, you get .o files, IIRC and so Geany's builtin smartness about this fails badly.
Maybe we should remove this check or we perform this check only if filetype is Java and compiler command contains "javac" assuming that this will use .class files. But this seems like another ugly hack with potential to be error-prone.
Regards, Enrico
On Sun, 14 Dec 2008 18:41:46 +0100 Enrico Tröger enrico.troeger@uvena.de wrote:
Hmm, it shouldn't append ".class" to %e, it only does this while preparing the execution to verify that the current source file already has been compiled (which means for javac a .class file exists). When using gcj, you get .o files, IIRC and so Geany's builtin smartness about this fails badly.
Maybe we should remove this check or we perform this check only if filetype is Java and compiler command contains "javac" assuming that this will use .class files. But this seems like another ugly hack with potential to be error-prone.
I think we could remove the check and just let the java interpreter issue a 'class not found' error. Same for executables/scripts, just let the interpreter say 'unknown command'. Then the user can make the run command do anything they like ;-)
Regards, Nick
On Mon, 15 Dec 2008 12:41:04 +0000, Nick Treleaven nick.treleaven@btinternet.com wrote:
On Sun, 14 Dec 2008 18:41:46 +0100 Enrico Tröger enrico.troeger@uvena.de wrote:
Hmm, it shouldn't append ".class" to %e, it only does this while preparing the execution to verify that the current source file already has been compiled (which means for javac a .class file exists). When using gcj, you get .o files, IIRC and so Geany's builtin smartness about this fails badly.
Maybe we should remove this check or we perform this check only if filetype is Java and compiler command contains "javac" assuming that this will use .class files. But this seems like another ugly hack with potential to be error-prone.
I think we could remove the check and just let the java interpreter issue a 'class not found' error. Same for executables/scripts, just let the interpreter say 'unknown command'. Then the user can make the run command do anything they like ;-)
Yes, it's probably better. Done so in SVN, I hope I didn't break too much :).
Regards, Enrico
On Fri, 12 Dec 2008 13:07:27 +0000 Nick Treleaven nick.treleaven@btinternet.com wrote:
@Yura: Could you rename this to 'External Debugger' and geanydebug to 'GDB' to avoid confusion?
Ok, I will rename them.