summaryrefslogtreecommitdiffstats
path: root/Modules
diff options
context:
space:
mode:
authorMichael Hirsch <scivision@users.noreply.gitlab.kitware.com>2021-08-11 17:40:14 (GMT)
committerMichael Hirsch <scivision@users.noreply.gitlab.kitware.com>2021-08-11 17:44:43 (GMT)
commitd62d0f048fdb073bab6bdb9b0055d97d0f9c8569 (patch)
tree06d43c23fd66a9e33a8b97d274efc63d4b5cf361 /Modules
parent8fddc2bb2fe3d3e7debc32f1e6f8f6e376a303b8 (diff)
downloadCMake-d62d0f048fdb073bab6bdb9b0055d97d0f9c8569.zip
CMake-d62d0f048fdb073bab6bdb9b0055d97d0f9c8569.tar.gz
CMake-d62d0f048fdb073bab6bdb9b0055d97d0f9c8569.tar.bz2
Help: CheckFortranFunctionExists: recommend more general CheckSourceCompiles
CheckFortranFunctionExists is really only relevant to Fortran 77 code. Fortran 90 and newer users should use CheckSourceCompiles instead.
Diffstat (limited to 'Modules')
-rw-r--r--Modules/CheckFortranFunctionExists.cmake6
1 files changed, 6 insertions, 0 deletions
diff --git a/Modules/CheckFortranFunctionExists.cmake b/Modules/CheckFortranFunctionExists.cmake
index ad72e2f..8f1ca9d 100644
--- a/Modules/CheckFortranFunctionExists.cmake
+++ b/Modules/CheckFortranFunctionExists.cmake
@@ -20,6 +20,12 @@ Check if a Fortran function exists.
``<result>``
variable to store the result; will be created as an internal cache variable.
+.. note::
+
+ This command does not detect functions in Fortran modules. In general it is
+ recommended to use :module:`CheckSourceCompiles` instead to determine if a
+ Fortran function or subroutine is available.
+
The following variables may be set before calling this macro to modify
the way the check is run: