On 6. May, 2010, at 16:55 , Jed Brown wrote: > On Thu, 6 May 2010 16:42:13 +0200, Michael Wild <them...@gmail.com> wrote: >> Looks like the Fortran 90 issue can be solved with "order-only" inputs: >> >> a.f90 |> gfortran -c -o %o %f |> %f.o > > This line also produces a.mod.
Ugh, yes. So this should be (does tup accept absolute source file paths?) /path/to/a.f90 |> gfortran -c -o %o %f |> %B.o %B.mod > >> b.f90 | a.f90 |> gfortran -c -o %o %f |> %f.o > > Maybe you meant > > b.f90 | a.mod |> gfortran -c -o %o %f |> %f.o Obviously... > > Note that the dependency analysis also needs to be rerun when files > change because, e.g. editing a.f90 to include "use b" should create a > loop. Yet another reason not to use fortran... > > Jed Yes, currently circular dependencies are generated. But I consider this to be an error on the user side... Otherwise the dependency scanner doesn't need to rerun, since the file that was modified to use another module needs to be recompiled anyways, triggering a recompile for all the downstream files. Michael _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
