summaryrefslogtreecommitdiffstats
path: root/Tests/RunCMake/CPack/README.txt
diff options
context:
space:
mode:
authorDomen Vrankar <domen.vrankar@gmail.com>2017-11-19 13:22:17 (GMT)
committerDomen Vrankar <domen.vrankar@gmail.com>2017-11-19 13:55:00 (GMT)
commit325f34d1507d391e5125d0a57e3575ecbe4e6f13 (patch)
treec4cac16ab6654628a712e198fdc6ec74438dfa27 /Tests/RunCMake/CPack/README.txt
parent176281e131f244bfc987a696951a87ea9b909840 (diff)
downloadCMake-325f34d1507d391e5125d0a57e3575ecbe4e6f13.zip
CMake-325f34d1507d391e5125d0a57e3575ecbe4e6f13.tar.gz
CMake-325f34d1507d391e5125d0a57e3575ecbe4e6f13.tar.bz2
CPack tests: add possibility for expecting config developer warnings
Diffstat (limited to 'Tests/RunCMake/CPack/README.txt')
-rw-r--r--Tests/RunCMake/CPack/README.txt10
1 files changed, 9 insertions, 1 deletions
diff --git a/Tests/RunCMake/CPack/README.txt b/Tests/RunCMake/CPack/README.txt
index 5ca1216..2e2abdf 100644
--- a/Tests/RunCMake/CPack/README.txt
+++ b/Tests/RunCMake/CPack/README.txt
@@ -96,6 +96,14 @@ the test has to run some functions after CPack.cmake is included. In such cases
a function run_after_include_cpack can be declared in test.cmake file and that
function will run after the inclusion of CPack.cmake.
+NOTE: During CMake configure stage developer warnings may be expected. In such
+cases an expected output regular expression can be provided by creating
+'<test_name>/configure-stdout.txt' and/or '<test_name>/configure-stderr.txt'
+file. There are also more specialized versions of the file available:
+- configure-${PACKAGING_TYPE}-${SUBTEST_SUFFIX}-std${o}.txt
+- configure-${SUBTEST_SUFFIX}-std${o}.txt
+- configure-${PACKAGING_TYPE}-std${o}.txt
+
build phase (optional and not available for source package tests)
-----------------------------------------------------------------
@@ -165,7 +173,7 @@ This phase is executed if '<test_name>/VerifyResult.cmake' script exists.
VerifyResult.cmake script also automatically prints out standard output and
standard error from CPack execution phase that is compared with
'<test_name>/<generator_name>-stdout.txt' regular expression and
-and '<test_name>/<generator_name>-stderr.txt' regular expresson respectively.
+'<test_name>/<generator_name>-stderr.txt' regular expresson respectively.
NOTE: For subtests generator name can also be suffixed with subtest name and/or
packaging type (MONOLITHIC, COMPONENT, GROUP) and in such cases the
preferences of which file will be used are as follows: