summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPetr Kmoch <petr.kmoch@gmail.com>2020-08-13 15:52:59 (GMT)
committerBrad King <brad.king@kitware.com>2020-08-17 19:27:52 (GMT)
commitc5407b95f083270108e434704413a727afd17660 (patch)
treeaf8f61fd68b6f9756cde24b865def1d592824c50
parent5748e76639822bf330986b0b77da6fd70f3de301 (diff)
downloadCMake-c5407b95f083270108e434704413a727afd17660.zip
CMake-c5407b95f083270108e434704413a727afd17660.tar.gz
CMake-c5407b95f083270108e434704413a727afd17660.tar.bz2
Help: Expand Fortran_MODULE_DIRECTORY documentation.
Document how Visual Studio generators append per-configuration directory to path where Fortran modules are created.
-rw-r--r--Help/prop_tgt/Fortran_MODULE_DIRECTORY.rst8
1 files changed, 8 insertions, 0 deletions
diff --git a/Help/prop_tgt/Fortran_MODULE_DIRECTORY.rst b/Help/prop_tgt/Fortran_MODULE_DIRECTORY.rst
index e061863..84029e4 100644
--- a/Help/prop_tgt/Fortran_MODULE_DIRECTORY.rst
+++ b/Help/prop_tgt/Fortran_MODULE_DIRECTORY.rst
@@ -11,6 +11,14 @@ corresponding to the target's source directory. If the variable
:variable:`CMAKE_Fortran_MODULE_DIRECTORY` is set when a target is created its
value is used to initialize this property.
+When using one of the :ref:`Visual Studio Generators` with the Intel Fortran
+plugin installed in Visual Studio, a subdirectory named after the
+configuration will be appended to the path where modules are created.
+For example, if ``Fortran_MODULE_DIRECTORY`` is set to ``C:/some/path``,
+modules will end up in ``C:/some/path/Debug`` (or
+``C:/some/path/Release`` etc.) when an Intel Fortran ``.vfproj`` file is
+generated, and in ``C:/some/path`` when any other generator is used.
+
Note that some compilers will automatically search the module output
directory for modules USEd during compilation but others will not. If
your sources USE modules their location must be specified by