On 27/10/2014 13:17, Brad King wrote:
Hi Brad,
On 10/24/2014 04:29 PM, Bill Somerville wrote:
Sorry, I am struggling with this. I have copied the
Darwin-GNU-Fortran.cmake file into my project modules directory and
patched it as you suggested.
Sorry, I meant the Modules directory of your CMake installation.
The good news is that it works when I patch the file in the actual CMake
installation
Great. I've applied the patch here:
OS X: Detect deployment target flags from GNU Fortran compilers
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=4fc3367f
although there is an oddity, when I configure the project I
see the messages from those two new function calls in the Fortran checks
but strangely I don't see similar messages from the C and C++ compiler
checks, yet they all seem to work adding the correct options.
The messages will only appear the first time CMake runs in a given
build tree. After that the result is stored in a persistent location
to be re-used on future runs. The C and C++ ones were probably already
cached.
Nope, just checked again with a fresh build directory. The C & C++
compilers are clang so I am guessing that whatever does the compiler
tests for them doesn't print message about version & SDK choices.
No problem, it all seems to work fine with those changes.
Thanks again for the quick response.
-Brad
Regards
Bill.
--
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://public.kitware.com/mailman/listinfo/cmake
