diff options
| author | Brad King <brad.king@kitware.com> | 2013-12-05 17:44:32 (GMT) |
|---|---|---|
| committer | Brad King <brad.king@kitware.com> | 2013-12-05 17:52:11 (GMT) |
| commit | ef7c11ee31b371bd07bc32991a671da757602213 (patch) | |
| tree | 5e367a108d14fa19e4dd81d2f2bc82524c007e28 /Tests/Fortran | |
| parent | e4201248ce76be40c109b67e68a4e295d709e2dc (diff) | |
| download | CMake-ef7c11ee31b371bd07bc32991a671da757602213.zip CMake-ef7c11ee31b371bd07bc32991a671da757602213.tar.gz CMake-ef7c11ee31b371bd07bc32991a671da757602213.tar.bz2 | |
Tests: Fix standalone build of tests with nested projects
Since commit fd6076d0 (Tests: Pass CMAKE_MAKE_PROGRAM instead of
--build-makeprogram, 2013-11-15) the ExportImport, Fortran, and
MacRuntimePath tests use the value of CMAKE_TEST_MAKEPROGRAM as the
CMAKE_MAKE_PROGRAM for their nested projects configurations.
Teach these tests to initialize CMAKE_TEST_MAKEPROGRAM when it is
not provided, such as when building the tests manually.
Diffstat (limited to 'Tests/Fortran')
| -rw-r--r-- | Tests/Fortran/CMakeLists.txt | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/Tests/Fortran/CMakeLists.txt b/Tests/Fortran/CMakeLists.txt index 8f165ce..adc4308 100644 --- a/Tests/Fortran/CMakeLists.txt +++ b/Tests/Fortran/CMakeLists.txt @@ -1,5 +1,9 @@ cmake_minimum_required (VERSION 2.6) project(testf C CXX Fortran) +if(NOT DEFINED CMAKE_TEST_MAKEPROGRAM AND NOT CMAKE_GENERATOR MATCHES "Visual Studio") + set(CMAKE_TEST_MAKEPROGRAM "${CMAKE_MAKE_PROGRAM}") +endif() + message("CTEST_FULL_OUTPUT ") set(CMAKE_VERBOSE_MAKEFILE 1) message("ENV_FLAGS = $ENV{FFLAGS}") |