| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | ExternalProject: Rerun download on SOURCE_DIR change | Craig Scott | 2022-02-01 | 1 | -5/+7 |
| | | | | Fixes: #21748 | ||||
| * | Tests: Fix typos and spelling in comments | Josef Angstenberger | 2021-05-07 | 1 | -1/+1 |
| | | |||||
| * | Tests: Remove RunCMake.ExternalProject unnecessary CMake version check | Brad King | 2020-09-15 | 1 | -2/+0 |
| | | |||||
| * | Tests: Remove workaround from RunCMake.ExternalProject MultiCommand case | Brad King | 2020-09-01 | 1 | -4/+0 |
| | | | | | | | Since commit 7249ba9677 (ExternalProject: Enforce that patch depends on update, 2020-04-03, v3.18.0-rc1~403^2) we do not need the workaround in the MultiCommand case. | ||||
| * | ExternalProject: Prevent COMMAND from being treated as a true keyword | Craig Scott | 2017-09-02 | 1 | -0/+30 |
| The known keywords for each function are obtained by scraping the documentation for lines matching a particular regular expression. In commit 8842a027 (ExternalProject: Improve documentation, 2017-07-09), the docs were overhauled and the COMMAND docs subsequently matched the regular expression when they shouldn't have. This made COMMAND appear as a true keyword, which thwarted the special handling logic elsewhere for the intended use of COMMAND arguments. This commit contains a workaround for issue #17229 to force a dependency of the patch step on the update step to ensure a predictable step order. Fixes: #17198 | |||||
