mirror of
https://github.com/Kitware/CMake.git
synced 2026-04-20 21:28:23 -05:00
de53eb18ab
cd8a57aeAdd option to build CMake against a system librhash71180fc8FindLibRHash: Add module to find the librhash package3216e94cRemove unused cm_sha2 infrastructure5420278dPort hash computation to cmCryptoHash9a596b33cmCryptoHash: Re-implement in terms of librhash47f91a61cmCryptoHash: Avoid using subclasses at client sitesd0ff3e70librhash: Port to KWIML for ABI and integer type information465a85fblibrhash: Avoid signed left-shift overflowfc2cb74flibrhash: Implement bswap_32 as a function even in strict C90 mode0bd333bclibrhash: Implement bswap_64 even in strict C90 mode7189d62clibrhash: Use __builtin_bswap{32,64} on Clangaf7ebf8alibrhash: Install COPYING file with CMake documentationbb01f20elibrhash: Disable warnings to avoid changing 3rd party code31bb727flibrhash: Build the library within CMake53048afalibrhash: Remove source fragments not needed for CMake5cb1b345Merge branch 'upstream-librhash' into import-librhash ...
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.