List of gfortran-ready libraries and packages

[Dennis Wassel]

2010/10/1 Magnus Hagdorn <Magnus.Hagdorn@marsupium.org>:
> On Fri, 2010-10-01 at 22:36 +0200, FX wrote:
> I have used Photran/Eclipse and I must say, I don't like it. It forces
> you into its way of doing things, which doesn't work when you have a
> large project consisting of Fortran, C and Python code all built by
> autotools.

I second that opinion. Even when not using autotools, but some
hand-made make machinery (including cross-language or cross-compiling
stuff), importing a mature existing project into Photran+eclipse is a
major pain. I tried a few times, but I frustration always won before I
reached the part where using the IDE could actually make life easier
for me. So I always end up with bash, emacs and gdb again.

> But then maybe I have been using command line tools and
> editors for far too long to get used to clickety-click interfaces. So, I
> use emacs/vi to edit files, grep to find stuff, svn for version control
> and meld to check before I commit something. I must say I life without
> meld would be difficult.

Dunno about meld (looks cool though), but yeah, that about sums it up
for me as well.

> However, I'd be very interested to hear what others have to say because
> I have to look after other users which are currently using MS Visual
> Studio which I'd like to tempt away to something less awkward.

To me, concerning look-and-feel, eclipse is closest to Visual Studio,
not by a large margin over Code::Blocks, though. NetBeans
looked-and-felt pretty different and awkard the last time I looked.
eclipse also seems to attract the biggest developer and user community
(maybe even by far), but this is an educated guess rather than based
on hard figures.
I quickly lost my patience when trying NetBeans, because its handling
was awkard, and even quicker with Code::Blocks, because it had a nasty
habit of randomly crahsing on me.

HTH
Dennis