1. 24 Feb, 2019 3 commits
  2. 15 Feb, 2019 5 commits
    • Brad King's avatar
      CMake 3.14.0-rc2 · e6897c72
      Brad King authored
    • Brad King's avatar
      Merge branch 'try_compile-expand-compile-defs' into release-3.14 · 113a395e
      Brad King authored
      Merge-request: !2965
    • Brad King's avatar
      Merge branch 'FindLibXml2' into release-3.14 · dac6cf1b
      Brad King authored
      Merge-request: !2970
    • Saleem Abdulrasool's avatar
      FindLibXml2: Document LibXml2_FOUND as preferred case · fd86a4de
      Saleem Abdulrasool authored
      Both `LIBXML2_FOUND` and `LibXml2_FOUND` are provided but the modern
      convention is to use the case that matches the module name.
    • Brad King's avatar
      try_compile: Restore expansion of ;-list in COMPILE_DEFINITIONS · cde2596a
      Brad King authored
      The quoting added by commit 8c5221fb (try_compile: Preserve special
      characters in COMPILE_DEFINITIONS, 2019-01-21, v3.14.0-rc1~108^2~3)
      broke the case that the `COMPILE_DEFINITIONS` value contains a `;`.
      Without the quoting the `;` would be generated literally in an unquoted
      argument in the test `CMakeLists.txt` file and would then be expanded.
      With quoting the `;` is preserved, which is not the old behavior.
      Fix this by expanding the `;`-list ahead of time.  Add test cases for
      behavior with both `#` and `;`.
      This was noticed with the PGI compiler where we set
      `CMAKE_CXX*_STANDARD_COMPILE_OPTION` to values like `--c++17;-A`.  The
      symptom had also been observed while preparing commit ef8f2376
      (ParseImplicitIncludeInfo: add SunPro Fortran and PGI compiler, Cray
      fix, 2019-01-29, v3.14.0-rc1~26^2~2) but was not recognized at the time
      as a regression.  Revert the workaround added by that commit.
      Fixes: #18919
  3. 14 Feb, 2019 6 commits
  4. 13 Feb, 2019 9 commits
  5. 11 Feb, 2019 7 commits
  6. 08 Feb, 2019 7 commits
  7. 07 Feb, 2019 3 commits