1. 28 Apr, 2021 1 commit
  2. 31 Mar, 2021 1 commit
  3. 28 Jan, 2021 1 commit
  4. 27 Jan, 2021 1 commit
  5. 18 Jun, 2020 1 commit
  6. 21 May, 2020 2 commits
  7. 28 Feb, 2020 1 commit
    • Brad King's avatar
      CheckFortranSource*: Avoid passing -DVAR to linker · 1bc52141
      Brad King authored
      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.
  8. 13 Nov, 2019 1 commit
  9. 03 Sep, 2019 1 commit
  10. 01 Mar, 2019 1 commit
    • Brad King's avatar
      VS: Fix Fortran target type selection with RC sources · 0b82f56a
      Brad King authored
      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 2c9f3578 (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 d3d2c3cd (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
  11. 10 Jan, 2019 1 commit
  12. 03 Jan, 2018 1 commit
  13. 05 Feb, 2015 1 commit
  14. 10 Nov, 2014 1 commit
  15. 30 Sep, 2014 1 commit
    • Brad King's avatar
      VS: Support Intel Fortran 15 .vfproj generation (#15175) · a128129a
      Brad King authored
      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: default avatarIan Harvey <Ian.Harvey@megms.com.au>
  16. 18 Aug, 2014 1 commit
  17. 31 Aug, 2011 1 commit
    • Brad King's avatar
      Fortran: Add support for free- and fixed-form flags · 5c0c635a
      Brad King authored
      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.
  18. 03 Aug, 2011 1 commit
    • Bill Hoffman's avatar
      Fix custom commands in VS2010 Fortran projects using CFG_INTDIR and test. · 3c53fbb1
      Bill Hoffman authored
      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.