d192918586
The conversion of Check<Lang>CompilerFlag, SourceCompiles, and SourceRuns over to the new functions has the possibility of breaking projects that had functions with those existing names. To reduce the possibility of collisions we now have all the legacy code call functions that start with `cmake_`, and users will need to explicitly include the new modules to get the non-prefixed versions Fixes: #21359
93 lines
4.0 KiB
CMake
93 lines
4.0 KiB
CMake
# Distributed under the OSI-approved BSD 3-Clause License. See accompanying
|
|
# file Copyright.txt or https://cmake.org/licensing for details.
|
|
|
|
#[=======================================================================[.rst:
|
|
CheckFortranSourceRuns
|
|
----------------------
|
|
|
|
.. versionadded:: 3.14
|
|
|
|
Check if given Fortran source compiles and links into an executable and can
|
|
subsequently be run.
|
|
|
|
.. command:: check_fortran_source_runs
|
|
|
|
.. code-block:: cmake
|
|
|
|
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 ``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).
|
|
|
|
By default, the test source file will be given a ``.F90`` file extension. The
|
|
``SRC_EXT`` option can be used to override this with ``.<extension>`` instead.
|
|
|
|
The underlying check is performed by the :command:`try_run` command. The
|
|
compile and link commands can be influenced by setting any of the following
|
|
variables prior to calling ``check_fortran_source_runs()``:
|
|
|
|
``CMAKE_REQUIRED_FLAGS``
|
|
Additional flags to pass to the compiler. Note that the contents of
|
|
:variable:`CMAKE_Fortran_FLAGS <CMAKE_<LANG>_FLAGS>` and its associated
|
|
configuration-specific variable are automatically added to the compiler
|
|
command before the contents of ``CMAKE_REQUIRED_FLAGS``.
|
|
|
|
``CMAKE_REQUIRED_DEFINITIONS``
|
|
A :ref:`;-list <CMake Language Lists>` of compiler definitions of the form
|
|
``-DFOO`` or ``-DFOO=bar``. A definition for the name specified by
|
|
``<resultVar>`` will also be added automatically.
|
|
|
|
``CMAKE_REQUIRED_INCLUDES``
|
|
A :ref:`;-list <CMake Language Lists>` of header search paths to pass to
|
|
the compiler. These will be the only header search paths used by
|
|
``try_run()``, i.e. the contents of the :prop_dir:`INCLUDE_DIRECTORIES`
|
|
directory property will be ignored.
|
|
|
|
``CMAKE_REQUIRED_LINK_OPTIONS``
|
|
A :ref:`;-list <CMake Language Lists>` of options to add to the link
|
|
command (see :command:`try_run` for further details).
|
|
|
|
``CMAKE_REQUIRED_LIBRARIES``
|
|
A :ref:`;-list <CMake Language Lists>` of libraries to add to the link
|
|
command. These can be the name of system libraries or they can be
|
|
:ref:`Imported Targets <Imported Targets>` (see :command:`try_run` for
|
|
further details).
|
|
|
|
``CMAKE_REQUIRED_QUIET``
|
|
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.
|
|
|
|
#]=======================================================================]
|
|
|
|
include_guard(GLOBAL)
|
|
include(Internal/CheckSourceRuns)
|
|
|
|
macro(CHECK_Fortran_SOURCE_RUNS SOURCE VAR)
|
|
# Pass the SRC_EXT we used by default historically.
|
|
# A user-provided SRC_EXT argument in ARGN will override ours.
|
|
cmake_check_source_runs(Fortran "${SOURCE}" ${VAR} SRC_EXT "F90" ${ARGN})
|
|
endmacro()
|