summaryrefslogtreecommitdiffstats
path: root/Source/cmForEachCommand.cxx
diff options
context:
space:
mode:
authorBrad King <brad.king@kitware.com>2009-12-10 17:16:38 (GMT)
committerBrad King <brad.king@kitware.com>2009-12-10 17:16:38 (GMT)
commit55275e017dfdd2826e2791ac16d29ea0cdfc55ac (patch)
tree37190e6c53b7547b362e5da3b88be38e164850a9 /Source/cmForEachCommand.cxx
parentfaf6d82bd6b6d31887f1f909d3b46b5fd130a435 (diff)
downloadCMake-55275e017dfdd2826e2791ac16d29ea0cdfc55ac.zip
CMake-55275e017dfdd2826e2791ac16d29ea0cdfc55ac.tar.gz
CMake-55275e017dfdd2826e2791ac16d29ea0cdfc55ac.tar.bz2
New decision method to enable Fortran tests
CMake does not enable Fortran for its own build, but it needs to find a Fortran compiler to know if it is possible to enable Fortran tests. Previously we searched for a hard-coded list of Fortran compilers which was duplicated from the CMakeDetermineFortranCompiler.cmake module. We now run CMake on a small test project that enables the Fortran language and reports the compiler it found. This represents a more realistic check of whether the Fortran tests will be able to find a compiler.
Diffstat (limited to 'Source/cmForEachCommand.cxx')
0 files changed, 0 insertions, 0 deletions