summaryrefslogtreecommitdiffstats
path: root/Modules
diff options
context:
space:
mode:
authorYurii Batrak <yuriib@met.no>2017-12-05 12:41:59 (GMT)
committerBrad King <brad.king@kitware.com>2017-12-14 13:22:07 (GMT)
commit7ab9a62572058d6cd8e5bf130d7aa27d5a2e50f2 (patch)
tree67cbcbe6c7972b4044a94516dd624351d59a93ed /Modules
parent5f2e2c387deb7f798cbc54d0980503e05873eaaa (diff)
downloadCMake-7ab9a62572058d6cd8e5bf130d7aa27d5a2e50f2.zip
CMake-7ab9a62572058d6cd8e5bf130d7aa27d5a2e50f2.tar.gz
CMake-7ab9a62572058d6cd8e5bf130d7aa27d5a2e50f2.tar.bz2
Makefiles: Drop 'requires' step and its supporting infrastructure
The 'requires' step was used to provide implicit dependencies between the generated Fortran module files and a Fortran target that needs these module files to ensure the correct compilation order. After recent refactoring to resolve all dependencies explicitly through `.mod.stamp` make targets, the separate 'requires' step is not needed anymore.
Diffstat (limited to 'Modules')
-rw-r--r--Modules/CMakeFortranInformation.cmake5
1 files changed, 0 insertions, 5 deletions
diff --git a/Modules/CMakeFortranInformation.cmake b/Modules/CMakeFortranInformation.cmake
index b315d33..d422578 100644
--- a/Modules/CMakeFortranInformation.cmake
+++ b/Modules/CMakeFortranInformation.cmake
@@ -67,11 +67,6 @@ if(CMAKE_USER_MAKE_RULES_OVERRIDE_Fortran)
set(CMAKE_USER_MAKE_RULES_OVERRIDE_Fortran "${_override}")
endif()
-
-# Fortran needs cmake to do a requires step during its build process to
-# catch any modules
-set(CMAKE_NEEDS_REQUIRES_STEP_Fortran_FLAG 1)
-
if(NOT CMAKE_Fortran_COMPILE_OPTIONS_PIC)
set(CMAKE_Fortran_COMPILE_OPTIONS_PIC ${CMAKE_C_COMPILE_OPTIONS_PIC})
endif()