1. 16 Apr, 2018 1 commit
    • Roland Schulz's avatar
      FindOpenMP: Fix support for Intel on Windows · 0c7433e8
      Roland Schulz authored
      The change in commit v3.11.0-rc1~334^2 (FindOpenMP: Use NO_DEFAULT_PATH
      where appropriate, 2017-11-15) broke partial support for Intel on Windows.
      Since `OpenMP_${LANG}_IMPLICIT_LINK_DIRS` is empty for this compiler
      the `find_library` call without `NO_DEFAULT_PATH` worked accidentally
      in environments with the needed libraries in the search path already.
      Fix support for Intel on Windows by simply removing our explicit search
      for the `libiomp5md` library.  In cases that it is needed, the compiler
      already inserts metadata in `.obj` files to tell the MSVC linker to use
      the library.
      Suggested-by: Christian Pfeiffer's avatarChristian Pfeiffer <cpfeiffer@live.de>
      Fixes: #17910
  2. 28 Mar, 2018 1 commit
  3. 27 Mar, 2018 3 commits
  4. 26 Mar, 2018 2 commits
    • Brad King's avatar
    • Brad King's avatar
      Revert "Remove CTestTestfile.cmake when BUILD_TESTING is OFF" · 70c50aa2
      Brad King authored
      Revert commit v3.8.0-rc1~305^2 (Remove CTestTestfile.cmake when BUILD_TESTING
      is OFF, 2016-11-14) again.  We reverted it once in commit v3.8.0-rc3~22^2
      (Revert "Remove CTestTestfile.cmake when BUILD_TESTING is OFF", 2017-03-06) but
      it was accidentally restored by commit v3.11.0-rc1~387^2 (server: add
      "ctestInfo" request to get test info, 2017-10-25), perhaps due to conflict
      resolution during rebase.
      We cannot remove `CTestTestfile.cmake` when testing is off because it breaks
      projects that never enable testing but create their own `CTestTestfile.cmake`
      manually instead.  Revert the change again and add a test case.
  5. 21 Mar, 2018 3 commits
  6. 20 Mar, 2018 1 commit
  7. 19 Mar, 2018 3 commits
  8. 16 Mar, 2018 3 commits
  9. 15 Mar, 2018 1 commit
    • Craig Scott's avatar
      GoogleTest: Rename TIMEOUT parameter to avoid clash · 96fdde26
      Craig Scott authored
      In gtest_discover_tests(), the TIMEOUT keyword was making it
      impossible to set the TIMEOUT test property via the PROPERTIES
      keyword. This would be a frequent case, but it doesn't complain
      and instead silently does something different to what would
      normally be expected. The TIMEOUT keyword has been renamed
      to DISCOVERY_TIMEOUT, thereby removing the clash.
      This is a breaking change. 3.10.1 and 3.10.2 were the only versions
      that supported the TIMEOUT keyword and uses of it were likely
      not working as intended.
      Fixes: #17801
  10. 14 Mar, 2018 4 commits
  11. 13 Mar, 2018 3 commits
  12. 12 Mar, 2018 6 commits
  13. 09 Mar, 2018 1 commit
  14. 07 Mar, 2018 5 commits
  15. 06 Mar, 2018 3 commits