summaryrefslogtreecommitdiff
path: root/Modules/CheckFortranSourceCompiles.cmake
Commit message (Collapse)AuthorAgeFilesLines
* Help:Check*: include CMAKE_REQUIRED_* vars to dedupescivision2023-03-141-41/+19
| | | | | | CMAKE_REQUIRED_FLAGS now notes that space-delimited string, not ;-list is required, which could be surprising compared to similar options that do use ;-list
* Help: CheckSource{Compiles,Runs}: fix typo and clarifyscivision2023-02-061-4/+8
|
* Help: Add `.. versionadded` directives to module docsNikita Nemkin2020-12-021-0/+2
| | | | Issue: #19715
* Modules: Do not implicitly add new functions via old Check ModulesRobert Maynard2020-10-261-2/+2
| | | | | | | | | | | | | 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
* CheckSource{Runs,Compiles}: Fix default Fortran source extensionMichael Hirsch2020-10-151-1/+3
| | | | | | | | | | | | | | | | In commit 357e2ef429 (CheckSoureRuns: Add a unified way to check if a source runs, 2020-09-14, v3.19.0-rc1~118^2), the default Fortran source file extension was accidentally changed from `.F90` to `.F`. Fix that. In commit 10ae907de0 (CheckSoureCompiles: Add a unified way to check if a source compiles, 2020-09-14, v3.19.0-rc1~118^2~1), the default Fortran source extension was correctly preserved as `.F`, but `.F90` is a better default both for consistency and modern usage. Use that for direct calls to the `check_source_compiles` macro. Update our original `check_fortran_source_compiles` implementation to use `.F` by default as it did before. Fixes: #21307
* CheckSoureCompiles: Add a unified way to check if a source compilesRobert Maynard2020-09-231-76/+2
|
* Help: Add Sphinx 'versionadded' directives to each top-level documentKitware Robot2020-07-061-0/+2
| | | | | | | Run the `Utilities/Sphinx/update_versions.py` script to add initial markup to every top-level document and find module. Issue: #19715
* CheckFortranSource*: Avoid passing -DVAR to linkerBrad King2020-02-281-4/+2
| | | | | | | | The test project is compiled with a `-DVAR` compiler flag where `VAR` is the result variable. Tell `try_compile` to add the flag through `add_definitions` instead of `CMAKE_Fortran_FLAGS` so that it is not used for linking. Otherwise some Fortran compilers (e.g. XL 15) do not like the flag when used to drive linking.
* Refactor: Use added message types in various modulesAlex Turbov2019-11-021-3/+3
| | | | Co-Authored-By: Craig Scott <craig.scott@crascit.com>
* Help: Add examples to CheckFortranSource{Runs,Compiles}Michael Hirsch, Ph.D2019-01-231-2/+14
|
* CheckFortranSourceRuns: Add module to check if Fortran code runsMichael Hirsch, Ph.D2019-01-101-1/+2
| | | | | Add a Fortran equivalent to the existing `Check{C,CXX}SourceRuns` modules.
* Check* functions family: add support for LINK_OPTIONSMarc Chevrier2018-12-011-0/+11
| | | | Fixes: #18521
* Help: Revise docs of modules AddFileDependencies..CheckFunctionExistsJoachim Wuttke (l)2018-10-191-14/+15
| | | | | | * Replace '::' by '.. code-block:: cmake' wherever it makes sense. * Convert to definition list where appropriate. * Prefer '<placeholder>' over 'placeholder'.
* Check*: Added include guardsCristian Adam2017-12-011-0/+1
|
* Check*Source{Compiles,Runs}: Rewrite docs for these modulesCraig Scott2017-06-241-29/+65
|
* Simplify CMake per-source license noticesBrad King2016-09-271-15/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | Per-source copyright/license notice headers that spell out copyright holder names and years are hard to maintain and often out-of-date or plain wrong. Precise contributor information is already maintained automatically by the version control tool. Ultimately it is the receiver of a file who is responsible for determining its licensing status, and per-source notices are merely a convenience. Therefore it is simpler and more accurate for each source to have a generic notice of the license name and references to more detailed information on copyright holders and full license terms. Our `Copyright.txt` file now contains a list of Contributors whose names appeared source-level copyright notices. It also references version control history for more precise information. Therefore we no longer need to spell out the list of Contributors in each source file notice. Replace CMake per-source copyright/license notice headers with a short description of the license and links to `Copyright.txt` and online information available from "https://cmake.org/licensing". The online URL also handles cases of modules being copied out of our source into other projects, so we can drop our notices about replacing links with full license text. Run the `Utilities/Scripts/filter-notices.bash` script to perform the majority of the replacements mechanically. Manually fix up shebang lines and trailing newlines in a few files. Manually update the notices in a few files that the script does not handle.
* CheckFortranSourceCompiles: Add support for custom source extensionBrad King2016-09-221-4/+11
| | | | | Fortran compilers interpret the source extension to decide whether to preprocess and what language level to use by default.
* CheckFortranSourceCompiles: Fix FAIL_REGEX documentation typoBrad King2016-09-221-1/+1
|
* Modules: Fix spelling of "succeeded" in check messagesTerrell Russell2015-10-061-1/+1
| | | | Change "succeded" to "succeeded" everywhere.
* Help: Document that the CHECK_* macros create cache variablesSebastian Leske2014-09-111-0/+1
| | | | Otherwise callers may expect to be able to re-use result variables.
* Add CheckFortranSourceCompiles module (#14656)Brad King2014-08-181-0/+110
Copy the CheckCSourceCompiles module and port it to Fortran. Extend the FortranOnly test to try using the new module. Suggested-by: Nicolas Bock <nicolasbock@gmail.com>