mirror of
https://github.com/Kitware/CMake.git
synced 2026-01-29 10:31:03 -06:00
1561748496
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
25 lines
880 B
CMake
25 lines
880 B
CMake
include(RunCMake)
|
|
|
|
run_cmake(NoOptions)
|
|
run_cmake(SourceEmpty)
|
|
run_cmake(SourceMissing)
|
|
run_cmake(CMAKE_CACHE_ARGS)
|
|
run_cmake(CMAKE_CACHE_DEFAULT_ARGS)
|
|
run_cmake(CMAKE_CACHE_mix)
|
|
run_cmake(NO_DEPENDS)
|
|
run_cmake(Add_StepDependencies)
|
|
run_cmake(Add_StepDependencies_iface)
|
|
run_cmake(Add_StepDependencies_iface_step)
|
|
run_cmake(Add_StepDependencies_no_target)
|
|
run_cmake(UsesTerminal)
|
|
|
|
# Run both cmake and build steps. We always do a clean before the
|
|
# build to ensure that the download step re-runs each time.
|
|
set(RunCMake_TEST_BINARY_DIR ${RunCMake_BINARY_DIR}/MultiCommand-build)
|
|
set(RunCMake_TEST_NO_CLEAN 1)
|
|
file(REMOVE_RECURSE "${RunCMake_TEST_BINARY_DIR}")
|
|
file(MAKE_DIRECTORY "${RunCMake_TEST_BINARY_DIR}")
|
|
run_cmake(MultiCommand)
|
|
run_cmake_command(MultiCommand-clean ${CMAKE_COMMAND} --build . --target clean)
|
|
run_cmake_command(MultiCommand-build ${CMAKE_COMMAND} --build .)
|