Merge topic 'ctest-remove-declarative-script-mode'

267b42bccc CTest: Remove declarative scripting mode

Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: scivision <michael@scivision.dev>
Merge-request: !9868
This commit is contained in:
Brad King
2024-10-11 13:21:34 +00:00
committed by Kitware Robot
23 changed files with 38 additions and 616 deletions
+3 -4
View File
@@ -9,7 +9,6 @@ runs a :option:`ctest -S` script
script_file_name2 ... [RETURN_VALUE var])
Runs a script or scripts much like if it was run from :option:`ctest -S`.
If no argument is provided then the current script is run using the current
settings of the variables. If ``NEW_PROCESS`` is specified then each
script will be run in a separate process.If ``RETURN_VALUE`` is specified
the return value of the last script run will be put into ``var``.
If ``NEW_PROCESS`` is specified then each script will be run in a separate
process. If ``RETURN_VALUE`` is specified the return value of the last script
run will be put into ``var``.
@@ -0,0 +1,14 @@
ctest-remove-declarative-script-mode
------------------------------------
* CTest's declarative scripting mode has been removed. This mode used to be
triggered by a :option:`ctest -S` script which did not call any
:ref:`CTest Commands` unless :variable:`CTEST_RUN_CURRENT_SCRIPT` was
explicitly set to ``OFF``. This feature was undocumented and was not covered
by any unit tests.
* The :variable:`CTEST_RUN_CURRENT_SCRIPT` variable no longer has any special
meaning.
* The :command:`ctest_run_script` command may no longer be called without any
arguments.
+2 -4
View File
@@ -1,7 +1,5 @@
CTEST_RUN_CURRENT_SCRIPT
------------------------
.. versionadded:: 3.11
Setting this to 0 prevents :manual:`ctest(1)` from being run again when it
reaches the end of a script run by calling :option:`ctest -S`.
Removed. This variable once supported an undocumented feature that has since
been removed.