summaryrefslogtreecommitdiffstats
path: root/Tests/FortranModules/CMakeLists.txt
diff options
context:
space:
mode:
authorBrad King <brad.king@kitware.com>2020-02-28 15:22:23 (GMT)
committerBrad King <brad.king@kitware.com>2020-02-28 15:37:11 (GMT)
commit210b0b99a96a37cb19de7e703c12f99a4a925926 (patch)
tree42535cdd045049f9ac04b86d791fa309c08260cc /Tests/FortranModules/CMakeLists.txt
parent2a9cf889178dfc202ec84f1fece8a68594cc3566 (diff)
downloadCMake-210b0b99a96a37cb19de7e703c12f99a4a925926.zip
CMake-210b0b99a96a37cb19de7e703c12f99a4a925926.tar.gz
CMake-210b0b99a96a37cb19de7e703c12f99a4a925926.tar.bz2
XL: Fix using Fortran modules from their output directory
The XL Fortran compiler's `-qmoddir=` 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 XL Fortran compiler so that it will be searched when using modules too. This fixes our `FortranModules` test's coverage of submodules on Ninja + XL. That test places module files in a subdirectory that with Ninja is not the current working directory when the compiler runs. Fixes: #20400
Diffstat (limited to 'Tests/FortranModules/CMakeLists.txt')
0 files changed, 0 insertions, 0 deletions