diff options
| author | Brad King <brad.king@kitware.com> | 2021-06-14 20:25:02 (GMT) |
|---|---|---|
| committer | Brad King <brad.king@kitware.com> | 2021-06-15 13:11:06 (GMT) |
| commit | a35d1212760707b195f6c462aadae8383ffcdeca (patch) | |
| tree | d8486131dfa10b96e565645a68481efc6e634707 /Tests/Module/WriteCompilerDetectionHeader/main.cpp | |
| parent | 10b2e5346984d95c15d0cc38ddf5c5fad11a6a65 (diff) | |
| download | CMake-a35d1212760707b195f6c462aadae8383ffcdeca.zip CMake-a35d1212760707b195f6c462aadae8383ffcdeca.tar.gz CMake-a35d1212760707b195f6c462aadae8383ffcdeca.tar.bz2 | |
Ninja: Populate P1689R4 compiled-module-path field for Fortran
When scanning Fortran dependencies, we know the file path at which a
provided module file is written. Store it in the `compiled-module-path`
field as specified by P1689R4. Our collator in `cmake_ninja_dyndep` no
longer needs to assume that the module file path can be derived from the
logical module name. In the future, the Fortran dependency scanning may
be done by the compiler itself, in which case it will provide the value
of `compiled-module-path`.
Diffstat (limited to 'Tests/Module/WriteCompilerDetectionHeader/main.cpp')
0 files changed, 0 insertions, 0 deletions