summaryrefslogtreecommitdiffstats
path: root/Tests/FortranOnly
Commit message (Collapse)AuthorAgeFilesLines
* Ninja: Pass preprocessor definitions when compiling with Intel FortranBrad King2019-09-033-0/+14
| | | | | | | | The Intel Fortran compiler supports an extension that allows conditional compilation based on preprocessor definitions specified on the command line even when not preprocessing. Fixes: #19664
* VS: Fix Fortran target type selection with RC sourcesBrad King2019-03-012-1/+7
| | | | | | | | | | | | | The Intel Fortran `.vfproj` files do support both Fortran and the Windows Resource compiler (`.rc)` files. Prior to CMake 3.9 we did not support that, but commit 2c9f35789d (VS: Decide project type by linker lang as fallback, 2017-03-30, v3.9.0-rc1~340^2) accidentally enabled it. It was then broken by commit d3d2c3cd49 (VS: Fix Fortran target type selection when linking C++ targets, 2019-02-04, v3.14.0-rc1~13^2). Restore support for Fortran+RC in VS projects and add a test case. Fixes: #19002
* CheckFortranSourceRuns: Add module to check if Fortran code runsMichael Hirsch, Ph.D2019-01-101-2/+9
| | | | | Add a Fortran equivalent to the existing `Check{C,CXX}SourceRuns` modules.
* Various typo fixesLuz Paz2018-01-031-2/+2
| | | | Some are user-facing. Others are source comments.
* CheckFortranCompilerFlag: Add test caseBrad King2015-02-051-0/+7
| | | | Extend the FortranOnly test with a case covering this module.
* Makefile: Add assembly and preprocessed targets for FortranTim Gallagher2014-11-103-0/+38
| | | | Extend the FortranOnly test to cover "make <src>.i" targets.
* VS: Support Intel Fortran 15 .vfproj generation (#15175)Brad King2014-09-301-8/+9
| | | | | | | | | | | | | | | | This version of the Intel Fortran plugin to Visual Studio says: please make sure that $(OutDir), $(TargetName) and $(TargetExt) property values match the value specified in %(Link.OutputFile) We must set TargetName and TargetExt in addition to the existing setting for OutputDirectory. The settings do not appear to hurt older versions of Intel Fortran, so set them unconditionally. Extend the FortranOnly test to cover a corresponding use case by using the OUTPUT_NAME target property. Inspired-by: Ian Harvey <Ian.Harvey@megms.com.au>
* Add CheckFortranSourceCompiles module (#14656)Brad King2014-08-181-0/+22
| | | | | | | 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>
* Fortran: Add support for free- and fixed-form flagsBrad King2011-08-312-5/+7
| | | | | | | Define a "Fortran_FORMAT" target and source file property. Initialize the target property from a "CMAKE_Fortran_FORMAT" variable. Interpret values "FIXED" and "FREE" to indicate the source file format. Append corresponding flags to the compiler command line.
* Fix custom commands in VS2010 Fortran projects using CFG_INTDIR and test.Bill Hoffman2011-08-036-0/+73
For custom commands in VS2010 Fortran projects the INTDIR variable is different than in the rest of the solution because Intel fortran still uses the old VS project files even in VS2010. So, we replace $(Configuration) directly in the project files. I have also added a FortranOnly test that tests this feature and is run on any generator that has Fortran abilities.