mirror of
https://github.com/Kitware/CMake.git
synced 2026-01-17 20:20:23 -06:00
2119c33b7e
A main scenario where this is needed is when a git operation needs the password to a private key and asks for it on the console. Without this change, such operations can appear to hang indefinitely with no prompt if QUIET is in effect (which it is by default). Another scenario this addresses is when progress of a download or update should be shown. Without this change, all such progress is buffered with some generators and will only be shown at the end, which defeats the purpose of logging any progress to begin with. Relates: #18238
30 lines
1.0 KiB
CMake
30 lines
1.0 KiB
CMake
include(RunCMake)
|
|
|
|
unset(RunCMake_TEST_NO_CLEAN)
|
|
|
|
run_cmake(MissingDetails)
|
|
run_cmake(DirectIgnoresDetails)
|
|
run_cmake(FirstDetailsWin)
|
|
run_cmake(DownloadTwice)
|
|
run_cmake(SameGenerator)
|
|
run_cmake(VarDefinitions)
|
|
run_cmake(GetProperties)
|
|
run_cmake(DirOverrides)
|
|
run_cmake(UsesTerminalOverride)
|
|
|
|
# We need to pass through CMAKE_GENERATOR and CMAKE_MAKE_PROGRAM
|
|
# to ensure the test can run on machines where the build tool
|
|
# isn't on the PATH. Some build slaves explicitly test with such
|
|
# an arrangement (e.g. to test with spaces in the path). We also
|
|
# pass through the platform and toolset for completeness, even
|
|
# though we don't build anything, just in case this somehow affects
|
|
# the way the build tool is invoked.
|
|
run_cmake_command(ScriptMode
|
|
${CMAKE_COMMAND}
|
|
-DCMAKE_GENERATOR=${RunCMake_GENERATOR}
|
|
-DCMAKE_GENERATOR_PLATFORM=${RunCMake_GENERATOR_PLATFORM}
|
|
-DCMAKE_GENERATOR_TOOLSET=${RunCMake_GENERATOR_TOOLSET}
|
|
-DCMAKE_MAKE_PROGRAM=${RunCMake_MAKE_PROGRAM}
|
|
-P ${CMAKE_CURRENT_LIST_DIR}/ScriptMode.cmake
|
|
)
|