- 26 Mar, 2018 1 commit
-
-
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.
-
- 19 Mar, 2018 3 commits
-
-
Brad King authored
-
- 16 Mar, 2018 3 commits
-
-
Brad King authored
Features recorded by commit v3.6.0-rc1~120^2~5 (Features: Record standards and features for Intel C++ on UNIX, 2016-04-28) for the Intel compiler left out initializer list support because our test case in `Tests/CompileFeatures/cxx_generalized_initializers.cpp` caused an internal compiler error. It turns out this is because the Intel compiler asserts the `initializer_list` constructor signatures to verify that they match its own `<initializer_list>` header. It was our dummy implementation used to test the language feature without any headers that caused the ICE. Revise it to use a constructor signature accepted by the Intel compiler. Fixes: #17829
- 15 Mar, 2018 1 commit
-
-
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
-
- 14 Mar, 2018 4 commits
-
- 13 Mar, 2018 3 commits
-
-
Brad King authored
Merge-request: !1836
-
A mistyped length calculation will memset across stack frame when the user's terminal width is larger than 270.
- 12 Mar, 2018 6 commits
-
-
-
Since commit v3.11.0-rc1~433^2~2 (Teach target_* commands to set INTERFACE properties of IMPORTED targets, 2017-09-18) it is now possible to use the customary `target_*` commands for adjusting the settings of an IMPORTED target. Update documentation accordingly.
- 09 Mar, 2018 1 commit
-
-
Brad King authored
-
- 07 Mar, 2018 5 commits
-
-
Brad King authored
* upstream-KWSys: KWSys 2018-03-07 (2ad561e7)
-
Code extracted from: https://gitlab.kitware.com/utils/kwsys.git at commit 2ad561e78b0d99f083f1213e403d5a8a90e0e134 (master). Upstream Shortlog ----------------- Brad King (4): 6e190d9a Fix include directory usage requirement for build tree 6d4e9fde SystemInformation: Android has no getifaddrs prior to API 24 0a0974d0 SystemTools: Restore unconditional caching in GetActualCaseForPath a241fd13 SystemTools: Remove caching from public GetActualCaseForPath
- 06 Mar, 2018 4 commits
-
-
Calling `std::string::front()` on an empty string results in an undefined behavior by the C++ standard. In gcc8 it causes an assertion to fail. This adds a check to `AUTOGEN` if a file to read is empty and in case avoids the use of an empty `std::string` buffer. Closes #17793
- 27 Feb, 2018 1 commit
-
-
Brad King authored
-
- 26 Feb, 2018 4 commits
-
-
Brad King authored
Refactoring in commit v3.11.0-rc1~293^2~4 (Modules: Remove paths set as global Unix prefixes, 2017-11-20) removed `PATH_SUFFIXES` options that appeared to be used to cover subdirectories of the `PATHS` options that were also removed. However, the path suffixes also apply to other search paths and so should not be removed. Restore them. Fixes: #17760
-
The test was expecting timestamps on day 1 in 1970 to start at 86400 but they actually started at 0. This worked without `SOURCE_DATE_EPOCH=1` because after 1972, leap days compensated the offset. Fixes: #17762
- 23 Feb, 2018 1 commit
-
- 22 Feb, 2018 3 commits
-
-
Gregor Jasny authored
In case CMAKE_XCODE_GENERATE_TOP_LEVEL_PROJECT_ONLY has been enabled generate only the root-level ZERO_CHECK target so targets in subdirectories pick up the root generator target of ZERO_CHECK. For the case that CMAKE_XCODE_GENERATE_TOP_LEVEL_PROJECT_ONLY is not enabled more investigation and a proper and final fix is still needed. Issue: 14297
-