New in version 3.14.
Check if given Fortran source compiles and links into an executable and can subsequently be run.
check_fortran_source_runs(<code> <resultVar> [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 be a Fortran program containing at least an
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.
<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).
By default, the test source file will be given a
.F90file extension. The
SRC_EXToption can be used to override this with
The underlying check is performed by the
try_run()command. The compile and link commands can be influenced by setting any of the following variables prior to calling
Additional flags to pass to the compiler. Note that the contents of
CMAKE_Fortran_FLAGSand its associated configuration-specific variable are automatically added to the compiler command before the contents of
A ;-list of compiler definitions of the form
-DFOO=bar. A definition for the name specified by
<resultVar>will also be added automatically.
If this variable evaluates to a boolean true value, all status messages associated with the check will be suppressed.
The check is only performed once, with the result cached in the variable named by
<resultVar>. Every subsequent CMake run will re-use this cached value rather than performing the check again, even if the
<code>changes. In order to force the check to be re-evaluated, the variable named by
<resultVar>must be manually removed from the cache.