1. 11 Feb, 2019 2 commits
    • Juuso "Linda" Lapinlampi's avatar
      Help: Fix elseif/endif typo · 572b4fd8
      Juuso "Linda" Lapinlampi authored
      In CMake 3.13.x, we had this evaluation for if() conditions:
      
          if(a) elseif(b) else(a) endif(a)
      
      The sensible intention of the change in commit c2efb3ef (Help: Revise
      docs on Scripting Commands, 2018-10-16, v3.14.0-rc1~505^2) was:
      
      > "endif", "endfunction" etc: Explain that the argument is optional and
      > maintained for compatibility only
      
      Instead of "endif", it ended up being written to the documentation as
      "elseif" by the commit author (oops) to if()'s page.
      
          if(a) elseif(a!?) else() endif(a?)
      
      Truthfully, endif()'s parameter should be an optional verbatim repeat
      and not elseif()'s. If it wasn't, elseif() would be described to be the
      same as if(). The rightful intended description is:
      
          if(a) elseif(b) else() endif()
      
      Fix that typo.
      572b4fd8
    • Fred Baksik's avatar
      2d701b78
  2. 08 Feb, 2019 2 commits
  3. 07 Feb, 2019 1 commit
  4. 06 Feb, 2019 4 commits
  5. 05 Feb, 2019 1 commit
  6. 04 Feb, 2019 3 commits
  7. 01 Feb, 2019 1 commit
  8. 31 Jan, 2019 1 commit
  9. 30 Jan, 2019 4 commits
  10. 29 Jan, 2019 2 commits
  11. 28 Jan, 2019 5 commits
  12. 26 Jan, 2019 1 commit
  13. 25 Jan, 2019 2 commits
    • Kyle Edwards's avatar
      ad0853b3
    • Ben Boeckel's avatar
      Help: prefer commit hashes in commit references · 939dc9a5
      Ben Boeckel authored
      The logic is that the describe output is readily available using `git
      tag --contains` locally. In addition, for a hypothetical commit which
      landed in both v3.9.4 and v3.10.1, there is no "better" tag to refer to.
      since v3.10.0's relation to such a commit is unclear either way.
      
      Also mention that a `Fixes` trailer is preferred if the mention is just
      to indicate a commit which introduced an error rather than writing a
      complete sentence about it.
      939dc9a5
  14. 24 Jan, 2019 3 commits
  15. 23 Jan, 2019 2 commits
  16. 22 Jan, 2019 1 commit
  17. 21 Jan, 2019 2 commits
  18. 18 Jan, 2019 1 commit
    • Andrew Paprocki's avatar
      Fortran: Add compiler ID/Version generator expressions · a0809142
      Andrew Paprocki authored
      Adds `Fortran_COMPILER_ID` and `Fortran_COMPILER_VERSION` generator
      expression support to match equivalent `C_COMPILER_ID`,
      `CXX_COMPILER_ID`, `C_COMPILER_VERSION`, and `CXX_COMPILER_VERSION`
      support.
      
      This is very helpful in the case where the C/C++ compiler suite is a
      different type of compiler from the platform Fortran compiler and
      projects use generator expressions to assign compiler flags and
      definitions.  (e.g. `GNU` C/C++ and `SunPro` Fortran on Linux)
      a0809142
  19. 17 Jan, 2019 2 commits