> > Why doesn't automake have dependency tracking for preprocessed > Fortran? > > Because nobody has implemented it yet. > > Well, I guess dependency tracking could be implemented similarly to how > it is done for C and C++. Using makedepend could be a start, sure, but > testing for a depmode would be better; e.g., some gfortran versions > support the much nicer gcc3 depmode. > > Actually, I'd consider module dependency tracking support a very > interesting Fortran feature for Automake as well. > > Cheers, > Ralf
Ok, so how does one go about developing this sort of thing for Automake? I'm certainly interested -- having time to do the work is always the issue, right? I've found a number of tools which claim to do dependency tracking: Foray http://code.google.com/p/foraytool/ Makedepf90 http://personal.inet.fi/private/erikedelmann/makedepf90 TCBuild http://macresearch.org/tcbuild-new-build-tool-fortran (precursor to foray?) mkmf http://www.gfdl.noaa.gov/~vb/mkmf.html fmkmf http://www.geos.ed.ac.uk/homes/hcp/fmkmf/ But what would be the best strategy for Automake? I've seen discussion of this earlier: http://www.mail-archive.com/automake@gnu.org/msg00682.html In short, I'm asking for advice. If I want the best chances of getting this feature (include as well as module dependency tracking in Fortran 77/90) into Automake, what's the suggested way to implement it? Jeff
