summaryrefslogtreecommitdiffstats
path: root/Tests/Module/WriteCompilerDetectionHeader/multi_files.cpp
diff options
context:
space:
mode:
authorBrad King <brad.king@kitware.com>2021-02-22 14:37:07 (GMT)
committerBrad King <brad.king@kitware.com>2021-02-22 14:38:12 (GMT)
commitec030877a2df35bea000b5037724c763fe690350 (patch)
tree20d4674c6a6fad39ecd2ff578c27466abfbe62e0 /Tests/Module/WriteCompilerDetectionHeader/multi_files.cpp
parent48410610a6636a73d4313479b7799c542b0d4553 (diff)
downloadCMake-ec030877a2df35bea000b5037724c763fe690350.zip
CMake-ec030877a2df35bea000b5037724c763fe690350.tar.gz
CMake-ec030877a2df35bea000b5037724c763fe690350.tar.bz2
NAG: Fix using Fortran modules from their output directory
The NAG Fortran compiler's `-mdir` flag sets the module output directory but does not add the directory to the search path for using modules. This is inconsistent with other compilers like the GNU Fortran compiler's `-J` flag that does both. In order to make these consistent, add the module output directory with a `-I` flag on the NAG Fortran compiler so that it will be searched when using modules too. We already do this for the XL Fortran compiler since commit 210b0b99a9 (XL: Fix using Fortran modules from their output directory, 2020-02-28, v3.18.0-rc1~640^2~1).
Diffstat (limited to 'Tests/Module/WriteCompilerDetectionHeader/multi_files.cpp')
0 files changed, 0 insertions, 0 deletions