Hi!
Already for some decades I am searching for an IDE for fortran. Today I stumbled into Geany. At the moment I use a realively new fortran dialect on both Windows boxes and on linux boxes in combination with the g95 compiler and/or the Portland compiler pgf90.
I am wondering if someone has (good) experience with the combination Geany+g95 (on any machine).
Please let me know how to configure the system and let me know if this will result in anything beyond a syntax highlighting text-editor (i.e. including smart compilation, debugging, ...).
Thanks!
Arjan
____________________________________________________________________________
DISCLAIMER: http://www.rivm.nl/disclaimer.htm
Hi,
On Wed, 27 Aug 2008 09:52:27 +0200 Arjan van Dijk Arjan.van.Dijk@rivm.nl wrote:
...
I am wondering if someone has (good) experience with the combination Geany+g95 (on any machine).
Please let me know how to configure the system and let me know if
Have a look at: http://geany.uvena.de/manual/0.14/index.html#build-system
this will result in anything beyond a syntax highlighting text-editor (i.e. including smart compilation, debugging, ...).
I don't know Fortran myself, but Geany doesn't support smart compilation or debugging (apart from a plugin for GDB, which I guess doesn't support Fortran). Someone was working on a CMake plugin, but I think it hasn't been released yet.
But Geany does do more than syntax highlighting, e.g. tag navigation & symbol list.
Regards, Nick
Have a look at: http://geany.uvena.de/manual/0.14/index.html#build-system
I don't know Fortran myself, but Geany doesn't support smart compilation or debugging (apart from a plugin for GDB, which I guess doesn't support Fortran). Someone was working on a CMake plugin, but I think it hasn't been released yet.
I checked this and it all sounds very interesting. But.
1) When you/I use modules in fortran, then the order in which the source files are passed to the compiler does matter. This means that the classic way of writing a Makefile is not so easy anymore. There are tools like "makemakefile" that can check all dependencies in your sources and use this knowlegde to make a universal Makefile for you for the generation of .o-files associated with any source file in that directory, but then Geany should do the talking to this tool for me...
2) To tweak an interface between Geany and gdb for debugging modern fortran code is beyond my expertise. Particularly if it is not (yet) clear if gdb and g95 like one another. It is access to the debugger that I really miss in all (other) applications, so for me this is the ultimate bottleneck. If someone who has done it before (i.e. link Geany to g95) now stands up, I'll embrace him/her cordially. Otherwise, I think I'll wait and see what will come up in the future...
Regards,
Arjan
On Wed, 27 Aug 2008 14:17:26 +0200 Arjan van Dijk Arjan.van.Dijk@rivm.nl wrote:
- When you/I use modules in fortran, then the order in which the
source files are passed to the compiler does matter. This means that the classic way of writing a Makefile is not so easy anymore. There are tools like "makemakefile" that can check all dependencies in your sources and use this knowlegde to make a universal Makefile for you for the generation of .o-files associated with any source file in that directory, but then Geany should do the talking to this tool for me...
Well, it's not really Geany's philosophy to include build management tools, as this is specific to each filetype (but someone could implement a plugin to do it). Geany just provides configurable commands to run.
- To tweak an interface between Geany and gdb for debugging modern
fortran code is beyond my expertise. Particularly if it is not (yet) clear if gdb
I wasn't suggesting you do that ;-) I just wanted to mention the GDB plugin in case somehow that was helpful.
and g95 like one another. It is access to the debugger that I really miss in all (other) applications, so for me this is the ultimate bottleneck. If someone who has done it before (i.e. link Geany to g95) now stands up, I'll embrace him/her cordially. Otherwise, I think I'll wait and see what will come up in the future...
Regards, Nick