mirror of
https://github.com/Kitware/CMake.git
synced 2026-03-15 14:00:40 -05:00
80112daMerge topic 'AutomocUseTargetProperties' into export-sets955b966exports: add a test for exporting dependent targets6f50a04exports: define a CMAKE_FIND_PACKAGE_NAME var set by find_package()0cfd055exports: move the handling of missing targets into subclasses190f2c8exports: fix build with MSVC68b5f448exports: first try at error handling if a target is missing87f4c01exports: accept a missing target if it is exported exactly once999061aexports: store pointers to all installations of each export set64b3a6cexports: cmGlobalGenerator::ExportSets destructor will clear it81cdab5exports: Hold an ExportSet pointer in cm*Export*Generator5c898fbexports: Add cmExportSetMap classd13ec1aexports: Create class cmExportSet4e2347cexports: Rename cmGlobalGenerator::AddTargetToExport{s,}e846e70exports: Remove cmTargetExport constructor81c66c8exports: Move cmTargetExport to a dedicated header fileae4ab62find_package: add support for a <package>_NOT_FOUND_MESSAGE variable ...
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.