Re: [CMake] Fortran 90 module output directories, dependency analysis

2010-06-01 Thread Kelly Thompson
On Tuesday, June 01, 2010 at 11:48 AM, Brad King wrote: > You can delete the object file the provides the module. > > > Perhaps that scenario where > > module files are deleted independent of the object/libraries is > > artificial, but it's not really correct for the build to break if they > > ar

Re: [CMake] Fortran 90 module output directories, dependency analysis

2010-06-01 Thread Jed Brown
On Tue, 01 Jun 2010 13:48:21 -0400, Brad King wrote: > You can delete the object file the provides the module. That doesn't seem to be enough if there is another target that depends on the module. E.g. if I delete petscmat.mod and CMakeFiles/.../petscmatmod.F.o, then run 'make all', I get an err

Re: [CMake] Fortran 90 module output directories, dependency analysis

2010-06-01 Thread Brad King
Jed Brown wrote: > There is still the issue that module files don't get rebuild if they are > deleted, > > make[2]: *** No rule to make target `include/petscmat.mod', needed by > `CMakeFiles/petscdm.dir/src/dm/f90-mod/petscdmmod.F.o'. Stop. > make[1]: *** [CMakeFiles/petscdm.dir/all] Error 2 >

Re: [CMake] Fortran 90 module output directories, dependency analysis

2010-06-01 Thread Jed Brown
On Tue, 01 Jun 2010 13:02:29 -0400, Brad King wrote: > Jed Brown wrote: > > Is there a way to specify where generated *.mod files will be placed? > > Something analogous to CMAKE_LIBRARY_OUTPUT_DIRECTORY? > > http://www.cmake.org/cmake/help/cmake-2-8-docs.html#prop_tgt:Fortran_MODULE_DIRECTORY *

Re: [CMake] Fortran 90 module output directories, dependency analysis

2010-06-01 Thread Brad King
Jed Brown wrote: > Is there a way to specify where generated *.mod files will be placed? > Something analogous to CMAKE_LIBRARY_OUTPUT_DIRECTORY? http://www.cmake.org/cmake/help/cmake-2-8-docs.html#prop_tgt:Fortran_MODULE_DIRECTORY -Brad ___ Powered by

Re: [CMake] Fortran 90 module output directories, dependency analysis

2010-06-01 Thread Jed Brown
On Tue, 1 Jun 2010 08:43:43 -0600, "Kelly Thompson" wrote: > This can be done using a Fortran compile option. For gfortran, add the > option "-M" to CMAKE_Fortran_FLAGS. Sure, however 1. One should use -J instead because (since 4.0), "-M is deprecated to avoid conflicts with existing GCC o

Re: [CMake] Fortran 90 module output directories, dependency analysis

2010-06-01 Thread Kelly Thompson
cmake@cmake.org > Subject: [CMake] Fortran 90 module output directories, dependency analysis > > Is there a way to specify where generated *.mod files will be placed? > Something analogous to CMAKE_LIBRARY_OUTPUT_DIRECTORY? > > Also, I notice that if I delete a module file, the

[CMake] Fortran 90 module output directories, dependency analysis

2010-05-31 Thread Jed Brown
Is there a way to specify where generated *.mod files will be placed? Something analogous to CMAKE_LIBRARY_OUTPUT_DIRECTORY? Also, I notice that if I delete a module file, the build fails (unlike everything else where it will be properly regenerated). This is with a plain Makefile build, cmake-2.