mirror of
https://github.com/Kitware/CMake.git
synced 2026-04-20 21:28:23 -05:00
81aaad0c73
b93982fMerge branch 'dev/fix-variable-watch-crash' into cmake-syntaxc50f7edcmListFileLexer: Modify flex output to avoid Borland warningbf73264Warn about unquoted arguments that look like long brackets58e5241Warn about arguments not separated by whitespacee75b69fcmListFileCache: Convert CMake language parser to classe945949Add RunCMake.Syntax test cases for command invocation styles0546484cmListFileArgument: Generalize 'Quoted' bool to 'Delimeter' enum28685adcmListFileLexer: Split normal and legacy unquoted arguments1eafa3ecmListFileLexer: Fix line number after backslash in stringf3155cdAdd RunCMake.Syntax test to cover argument parsing
If you think about adding a new testcase then here is a small checklist you can run through to find a proper place for it. Go through the list from the beginning and stop once you find something that matches your tests needs, i.e. if you will test a module and only need the configure mode use the instructions from section 2, not 3. 1. Your testcase can run in CMake script mode, i.e. "cmake -P something" Put your test in Tests/CMakeTests/ directory as a .cmake.in file. It will be put into the test binary directory by configure_file(... @ONLY) and run from there. Use the AddCMakeTest() macro in Tests/CMakeTests/CMakeLists.txt to add your test to the test runs. 2. Your test needs CMake to run in configure mode, but will not build anything This includes tests that will build something using try_compile() and friends, but nothing that expects add_executable(), add_library(), or add_test() to run. If the test configures the project only once and it must succeed then put it into the Tests/CMakeOnly/ directory. Create a subdirectory named like your test and write the CMakeLists.txt you need into that subdirectory. Use the add_CMakeOnly_test() macro from Tests/CMakeOnly/CMakeLists.txt to add your test to the test runs. If the test configures the project with multiple variations and verifies success or failure each time then put it into the Tests/RunCMake/ directory. Read the instructions in Tests/RunCMake/CMakeLists.txt to add a test. 3. If you are testing something from the Modules directory Put your test in the Tests/Modules/ directory. Create a subdirectory there named after your test. Use the ADD_TEST_MACRO macro from Tests/CMakeLists.txt to add your test to the test run. If you have put your stuff in Tests/Modules/Foo then you call it using ADD_TEST_MACRO(Module.Foo Foo). 4. You are doing other stuff. Find a good place ;) In doubt mail to cmake-developers@cmake.org and ask for advise.