Foray Build Tool Project Started
in [Fortran]
|
Prev: Get system time
Next: the g0 edit descriptor
From: John Appleyard on 9 Jul 2008 17:40 Richard Maine wrote: > John Appleyard <spamtrap(a)polyhedron.com> wrote: > >> Polyhedron's automake does this. Note that Polyhedron's automake is not >> the same as the Linux automake (I believe we had the name in the public >> domain first - in this newsgroup as a matter of fact - but I've never >> bothered to sort it out with the open source guys) > > If you try to sort it out, you'll get off on the wrong foot talking to > them if you refer to it as the "Linux automake". That's the kind of > terminology that they tend to have pretty negative reacrtions to. I > don't personally support Stallman's insistance that one has to refer to > Linux as GNU/Linux because it uses so many GNU tools. That strikes me as > just his sour grapes. But renaming the individual GNU tools as Linux > ones just because they happen to be used in most/all Linux distributions > goes a bit much the other way in my opinion. > > The GNU automake well predates Linux and is used in plenty of other > operating systems as well. Well whatever you call it, it seems to have originated in September 1994 as an 11 line shell script. Linux was before that (1992?). The first record I have of our automake is in March 1994. -- JA
From: wim on 10 Jul 2008 14:34 On Jul 9, 8:44 pm, nos...(a)see.signature (Richard Maine) wrote: > Michael Prager <Mike.Prager.ind...(a)noaa.gov> wrote: > > Didn't you mention some time ago a make-makefile utility that > > you use successfully? > > I've used Makedepf90 (google for it). There are several others, but > that's the one that seemed to fit my particular needs best. Your mileage > may vary, etc. It has been long enough since I looked that I don't > recall what particular features pushed me to that one. Since version 2.6, cmake works also very good for Fortran: http://www.cmake.org Wim
From: Richard Maine on 10 Jul 2008 17:38 wim <wim.van.hoydonck(a)gmail.com> wrote: > On Jul 9, 8:44 pm, nos...(a)see.signature (Richard Maine) wrote: > > Michael Prager <Mike.Prager.ind...(a)noaa.gov> wrote: > > > Didn't you mention some time ago a make-makefile utility that > > > you use successfully? > > > > I've used Makedepf90 (google for it). There are several others, but > > that's the one that seemed to fit my particular needs best. Your mileage > > may vary, etc. It has been long enough since I looked that I don't > > recall what particular features pushed me to that one. > > Since version 2.6, cmake works also very good for Fortran: > > http://www.cmake.org I don't recall running into that one before. Interestingly (to me anyway), a quick search in the cmake wiki for Fortran material reveals that at least some of its Fortran parsing support came from makedepf90. -- Richard Maine | Good judgement comes from experience; email: last name at domain . net | experience comes from bad judgement. domain: summertriangle | -- Mark Twain
From: Michael Prager on 11 Jul 2008 12:20
nospam(a)see.signature (Richard Maine) wrote: > wim <wim.van.hoydonck(a)gmail.com> wrote: > > > On Jul 9, 8:44 pm, nos...(a)see.signature (Richard Maine) wrote: > > > Michael Prager <Mike.Prager.ind...(a)noaa.gov> wrote: > > > > Didn't you mention some time ago a make-makefile utility that > > > > you use successfully? > > > > > > I've used Makedepf90 (google for it). There are several others, but > > > that's the one that seemed to fit my particular needs best. Your mileage > > > may vary, etc. It has been long enough since I looked that I don't > > > recall what particular features pushed me to that one. > > > > Since version 2.6, cmake works also very good for Fortran: > > > > http://www.cmake.org > > I don't recall running into that one before. Interestingly (to me > anyway), a quick search in the cmake wiki for Fortran material reveals > that at least some of its Fortran parsing support came from makedepf90. Thanks to wim, thanks to Richard. Mike -- Mike Prager, NOAA, Beaufort, NC Address spam-trapped; remove color to reply. * Opinions expressed are personal and not represented otherwise. * Any use of tradenames does not constitute a NOAA endorsement. |