On 02/03/2015 07:46 AM, Nicolas Bock wrote:
> please find attached a patch based on
> 460f7bcb7d11e905ee025c9d9cc9629d597fa91b.
Thanks. Was this based on CheckCCompilerFlag from that version too?
On 02/01/2015 04:18 AM, Rolf Eike Beer wrote:
> Also I don't know if it makes sense to check for certain flags that look
> specific to C++. Which compilers did you use to test?
Agreed. Do you have example failure messages from any compilers?
Local testing of GNU Fortran 4.9 shows that bad flags are rejected with
an error. Do we need the pattern matches for any Fortran compilers?
> + # Some compilers do not fail with a bad flag
> + FAIL_REGEX "command line option .* is valid for .* but not for C" # GNU
> + ${_CheckFortranCompilerFlag_COMMON_PATTERNS}
Certainly the "but not for C" message will not show up from a
Fortran compiler.
Thanks,
-Brad
--
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-developers
