It appears that setting CMAKE_Fortran_FLAGS doesn't work unless you
give it a different cache string name. For example, if I have a
CMakeLists.txt just containing the following:
project(Fortran)
set(CMAKE_Fortran_FLAGS "${CMAKE_Fortran_FLAGS} -static-libgfortran")
and run cmake, the resulting line in CMakeCache.txt reads:
//Flags for Fortran compiler
CMAKE_Fortran_FLAGS:STRING=
However, changing the flag setting command to:
set(CMAKE_Fortran_FLAGS "${CMAKE_Fortran_FLAGS} -static-libgfortran"
CACHE STRING "fortran flags" FORCE)
results in
//fortran flags
CMAKE_Fortran_FLAGS:STRING= -static-libgfortran
I get the same results whether I include ${CMAKE_Fortran_FLAGS} or
not. Is the CACHE STRING property really necessary, or am I missing
something else?
Cheers,
Chris
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
