summaryrefslogtreecommitdiffstats
path: root/Modules/CheckFortranSourceRuns.cmake
diff options
context:
space:
mode:
authorBrad King <brad.king@kitware.com>2019-01-24 15:36:33 (GMT)
committerKitware Robot <kwrobot@kitware.com>2019-01-24 15:36:40 (GMT)
commit378473f9f184000cb768c1b99e6242e054787f34 (patch)
treea7d2c19901784f4ec584f2872a3004c8fb94fe27 /Modules/CheckFortranSourceRuns.cmake
parent1d02491950b0aa05d2053e7fa32b39dca31e537b (diff)
parent3d63d3ce2fd6064433e2cff9469260aec9deb116 (diff)
downloadCMake-378473f9f184000cb768c1b99e6242e054787f34.zip
CMake-378473f9f184000cb768c1b99e6242e054787f34.tar.gz
CMake-378473f9f184000cb768c1b99e6242e054787f34.tar.bz2
Merge topic 'fortran-docs'
3d63d3ce2f Help: Add examples to CheckFortranSource{Runs,Compiles} Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !2843
Diffstat (limited to 'Modules/CheckFortranSourceRuns.cmake')
-rw-r--r--Modules/CheckFortranSourceRuns.cmake16
1 files changed, 14 insertions, 2 deletions
diff --git a/Modules/CheckFortranSourceRuns.cmake b/Modules/CheckFortranSourceRuns.cmake
index 58d90d7..13fdb0b 100644
--- a/Modules/CheckFortranSourceRuns.cmake
+++ b/Modules/CheckFortranSourceRuns.cmake
@@ -16,8 +16,20 @@ subsequently be run.
[SRC_EXT <extension>])
Check that the source supplied in ``<code>`` can be compiled as a Fortran source
- file, linked as an executable and then run. The ``<code>`` must contain at
- least ``program; end program`` statements. If the ``<code>`` could be built and run
+ file, linked as an executable and then run. The ``<code>`` must be a Fortran program
+ containing at least an ``end`` statement--for example:
+
+ .. code-block:: cmake
+
+ check_fortran_source_runs("real :: x[*]; call co_sum(x); end" F2018coarrayOK)
+
+ This command can help avoid costly build processes when a compiler lacks support
+ for a necessary feature, or a particular vendor library is not compatible with
+ the Fortran compiler version being used. Some of these failures only occur at runtime
+ instead of linktime, and a trivial runtime example can catch the issue before the
+ main build process.
+
+ If the ``<code>`` could be built and run
successfully, the internal cache variable specified by ``<resultVar>`` will
be set to 1, otherwise it will be set to an value that evaluates to boolean
false (e.g. an empty string or an error message).