summaryrefslogtreecommitdiffstats
path: root/Tests
Commit message (Collapse)AuthorAgeFilesLines
* Tests: CPack test unify expected file namingDomen Vrankar2016-11-2727-54/+122
| | | | | | | | | | | Each generator generates its own file format with different extensions but they all create those file names by a certain pattern and all of them require the same pieces for that pattern to work. Now we can only provide pieces once and and each generator will use those pieces to generate an expected file name.
* Tests: CPack test move and merge VerifyResultDomen Vrankar2016-11-2716-117/+110
| | | | | Merge VerifyResult of different generators pertest and move the file to its test dir.
* Tests: CPack test move per test prerequirementsDomen Vrankar2016-11-274-2/+2
| | | | | Move per test prerequirements into the belonging test.
* Tests: CPack test merge generator specificsDomen Vrankar2016-11-2721-104/+127
| | | | | Merge test generator specifics into test itself.
* Tests: CPack test move ExpectedFiles scriptDomen Vrankar2016-11-2735-105/+109
| | | | | Merge per generator ExpectedFiles scripts into one per test and move it to test dir.
* Tests: CPack test should always check test outputDomen Vrankar2016-11-274-7/+5
|
* Tests: CPack test move std error files to test filesDomen Vrankar2016-11-275-4/+4
|
* Tests: CPack move tests to separate dirDomen Vrankar2016-11-2720-1/+1
| | | | | | For greater transparency tests are moved to a subfolder with each test having its own dir.
* Tests: CPack test should use default package nameDomen Vrankar2016-11-2728-46/+18
| | | | | | | | Package names are irrelevant for most CPack tests so tests now set default package name that is created from test name and used if it is not explicitly provided in the test.
* Tests: CPack/RPM test introduction of default stderr test outputDomen Vrankar2016-11-2714-22/+3
|
* Tests: fix CPack test source packages missing generator typeDomen Vrankar2016-11-271-1/+1
| | | | | | Source packages testing for RunCMake CPack tests did not provide generator type to the project built from source package.
* Tests: CPack fix for invalid config file pathDomen Vrankar2016-11-271-2/+1
| | | | | Invalid config file path was passed to per test specific prerequirements script.
* Allow NO_SYSTEM_FROM_IMPORTED on imported INTERFACE librariesBrad King2016-11-211-0/+1
| | | | | | | | | Imported INTERFACE libraries can specify include directories via `INTERFACE_INCLUDE_DIRECTORIES` so the default behavior of treating them as system include directories applies. Allow users to turn this off by setting `NO_SYSTEM_FROM_IMPORTED` on such targets. Closes: #16443
* Merge topic 'capture-clang-tidy-errors'Brad King2016-11-216-1/+15
|\ | | | | | | | | | | | | 80ebc55a cmake: Report if the <LANG>_CLANG_TIDY tool exits with non-zero ce1abfa4 cmake: If ldd for LINK_WHAT_YOU_USE fails to run then report why 44de6157 cmake: Comment why we ignore the include-what-you-use return code
| * cmake: Report if the <LANG>_CLANG_TIDY tool exits with non-zeroBrad King2016-11-185-0/+13
| | | | | | | | | | | | | | | | When using `<LANG>_CLANG_TIDY` our internal launcher for the tool must capture its return code and stderr and report them on failure. Otherwise incorrect command lines silently fail. Closes: #16435
| * cmake: Comment why we ignore the include-what-you-use return codeBrad King2016-11-181-1/+2
| | | | | | | | | | | | | | | | The include-what-you-use tool always returns non-zero to indicate that it did not actually produce an object file as Clang would from the same command line. Add a comment explaining that this is why we ignore its return code. Also update our `pseudo_iwyu` test suite tool to always exit with an error too.
* | Tolerate removed/replaced CMakeCache.txt with old CMakeFiles/Brad King2016-11-173-0/+27
|/ | | | | | | | | | | Users or scripts commonly remove or replace `CMakeCache.txt` without also removing `CMakeFiles/`. In this case the information saved in the cache from platform information initialization is missing, so we need to re-initialize it. In such a case, remove the platform information directory so that re-initialization will occur and restore needed information to the cache. Closes: #14820
* Merge topic 'android-info-variables'Brad King2016-11-171-1/+33
|\ | | | | | | | | | | | | f7c5e970 Android: Add CMAKE_<LANG>_ANDROID_TOOLCHAIN_MACHINE d95e6dff Android: Add CMAKE_ANDROID_NDK_TOOLCHAIN_HOST_TAG variable 3d42a72b Android: Always set CMAKE_ANDROID_NDK_TOOLCHAIN_VERSION
| * Android: Add CMAKE_<LANG>_ANDROID_TOOLCHAIN_MACHINEBrad King2016-11-141-0/+17
| | | | | | | | | | | | | | | | Expose the binutils' machine name (typically used as a prefix on the tool names) publicly. This is expected to match the `gcc -dumpmachine` value. Suggested-by: Ruslan Baratov <ruslan_baratov@yahoo.com>
| * Android: Add CMAKE_ANDROID_NDK_TOOLCHAIN_HOST_TAG variableBrad King2016-11-141-0/+8
| | | | | | | | | | | | | | | | | | The NDK provides prebuilt toolchain files in directories named for the host architecture. The NDK build system calls this `HOST_TAG`. Expose the value publicly for use by clients that need to pass it to external tools. Suggested-by: Ruslan Baratov <ruslan_baratov@yahoo.com>
| * Android: Always set CMAKE_ANDROID_NDK_TOOLCHAIN_VERSIONBrad King2016-11-141-1/+8
| | | | | | | | | | | | | | | | | | When this variable is not set by the user or toolchain file, set it to the default selected. This will be useful for client code that needs to pass the value to an external tool that needs to find the same toolchain in the NDK. Leave it empty for a standalone toolchain. Suggested-by: Ruslan Baratov <ruslan_baratov@yahoo.com>
* | Merge topic 'improve_ctest_memcheck_output'Brad King2016-11-177-7/+21
|\ \ | | | | | | | | | | | | f0d50957 ctest: Improve output for `-T memcheck`
| * | ctest: Improve output for `-T memcheck`Bill Hoffman2016-11-177-7/+21
| | | | | | | | | | | | | | | Show how many defects each test that had a defect produced. Also tell the user where to find the full log files.
* | | Merge topic 'test_vs_targets_file_reference'Brad King2016-11-165-0/+61
|\ \ \ | |/ / |/| | | | | | | | c9560a9a Tests: Extend VS10Project to cover `.targets` file linking
| * | Tests: Extend VS10Project to cover `.targets` file linkingSoji Yamakawa2016-11-155-0/+61
| | | | | | | | | | | | | | | | | | With VS generators for 2010 and above, passing a `.targets` file to `target_link_libraries` is expected to generate content in the `.vcxproj` file to import the targets file. Add a test to cover this.
* | | Merge topic 'add-SHA-3'Brad King2016-11-1514-1/+44
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | f636d1e7 Help: Add notes for topic 'add-SHA-3' cb5dba8e Tests: Add SHA-3 algorithm coverage to CPack checksum test a9fa6099 ExternalProject: Add support for SHA-3 algorithms b4ffd26f ExternalData: Add support for SHA-3 algorithms 60939702 file: Add support for SHA-3 algorithms 92f95aed string: Add support for SHA-3 algorithms c326209f cmCryptoHash: Add support for SHA-3 algorithms 979e8ba6 Help: De-duplicate and spell out supported hash algorithms 7a79f7e3 librhash: Activate SHA-3 implementation 87584b5e Merge branch 'upstream-librhash' into add-SHA-3 7fcbd47e librhash 2016-11-06 (de79828d) c50c32a3 librhash: Update import script to add SHA-3 implementation
| * | | Tests: Add SHA-3 algorithm coverage to CPack checksum testBrad King2016-11-111-1/+1
| | | |
| * | | ExternalData: Add support for SHA-3 algorithmsBrad King2016-11-113-0/+3
| | | |
| * | | file: Add support for SHA-3 algorithmsBrad King2016-11-105-0/+20
| | | |
| * | | string: Add support for SHA-3 algorithmsBrad King2016-11-105-0/+20
| | | |
* | | | ExternalProject: Fix UPDATE_DISCONNECTED with empty update stepsBrad King2016-11-151-0/+1
| |_|/ |/| | | | | | | | | | | | | | | | | | | | | | | When `UPDATE_DISCONNECTED` is enabled the post-update steps unconditionally depend on a `skip-update` step instead of `update`. Make `skip-update` available whenever `UPDATE_DISCONNECTED` is enabled, whether there is a real update step or not. Closes: #16428
* | | Merge topic 'swig_add_library'Brad King2016-11-141-2/+11
|\ \ \ | |_|/ |/| | | | | | | | | | | | | | | | | | | | a57e7630 Help: Add notes for topic 'swig_add_library' 013193d0 SwigTest: Update for swig_add_library and add lua example ec1d585c UseSWIG: Do not set PREFIX property for SHARED and STATIC lua libraries 4c5b3c1c UseSWIG: Do not set NO_SONAME property for SHARED and STATIC libraries d0a9d8bb UseSWIG: Add swig_add_library macro.
| * | SwigTest: Update for swig_add_library and add lua exampleDaniele E. Domenichelli2016-11-111-2/+11
| |/
* | Merge topic 'cdash_version_check'Brad King2016-11-112-0/+2
|\ \ | | | | | | | | | | | | | | | d3633731 Do not query CDash for version f725b20b Update tests that expect uncompressed output
| * | Update tests that expect uncompressed outputZack Galbreath2016-11-082-0/+2
| | | | | | | | | | | | Pass --no-compressed-output to ctest for tests that expect uncompressed output.
* | | Merge topic 'ctest_memcheck_defect_count'Brad King2016-11-118-2/+46
|\ \ \ | | | | | | | | | | | | | | | | 3a523eec ctest_memcheck: Add DEFECT_COUNT option to capture defect count
| * | | ctest_memcheck: Add DEFECT_COUNT option to capture defect countBetsy McPhail2016-11-098-2/+46
| | | |
* | | | Merge topic 'ExternalProject-GIT_CONFIG'Brad King2016-11-111-0/+17
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | 2be9d85a ExternalProject: Allow passing config flags to git clone
| * | | | ExternalProject: Allow passing config flags to git cloneChristian Fetzer2016-11-091-0/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add a `GIT_CONFIG` parameter that allows to specify `--config` flags that are passed to the git clone command. This can be used to specify for example `core.autocrlf=true`. The `--config` parameter is supported since Git 1.7.7.
* | | | | Features: Suppress c_static_assert test coverage on Intel <= 15Brad King2016-11-101-0/+9
| |_|_|/ |/| | | | | | | | | | | It works on some pre-15.0.2 versions but not others.
* | | | Merge topic 'import-librhash'Brad King2016-11-104-0/+38
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | cd8a57ae Add option to build CMake against a system librhash 71180fc8 FindLibRHash: Add module to find the librhash package 3216e94c Remove unused cm_sha2 infrastructure 5420278d Port hash computation to cmCryptoHash 9a596b33 cmCryptoHash: Re-implement in terms of librhash 47f91a61 cmCryptoHash: Avoid using subclasses at client sites d0ff3e70 librhash: Port to KWIML for ABI and integer type information 465a85fb librhash: Avoid signed left-shift overflow fc2cb74f librhash: Implement bswap_32 as a function even in strict C90 mode 0bd333bc librhash: Implement bswap_64 even in strict C90 mode 7189d62c librhash: Use __builtin_bswap{32,64} on Clang af7ebf8a librhash: Install COPYING file with CMake documentation bb01f20e librhash: Disable warnings to avoid changing 3rd party code 31bb727f librhash: Build the library within CMake 53048afa librhash: Remove source fragments not needed for CMake 5cb1b345 Merge branch 'upstream-librhash' into import-librhash ...
| * | | FindLibRHash: Add module to find the librhash packageBrad King2016-11-104-0/+38
| |/ / | | | | | | | | | | | | | | | Add it to a private source directory that is not installed so that we can use it for building CMake itself. This will allow it to mature before being distributed publicly.
* | | Merge topic 'drop-kwstyle'Brad King2016-11-091-14/+0
|\ \ \ | | | | | | | | | | | | | | | | 36f9f0f8 Drop KWStyle checks in favor of clang-format and Git hooks
| * | | Drop KWStyle checks in favor of clang-format and Git hooksBrad King2016-11-081-14/+0
| | |/ | |/| | | | | | | | | | | | | We now define code layout by clang-format and enforce whitespace with Git hooks. There is no need to run KWStyle anymore, as all we used it to check was line length anyway.
* | | Merge topic 'imported-interface-libname'Brad King2016-11-0914-2/+173
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | 09cda9d5 Allow imported INTERFACE libraries to specify a link library name 1d1f1eeb cmTarget: Refactor GetMappedConfig to choose location property up front 479932fa cmTarget: Add comment clarifying interface library special case 925e4270 cmTarget: Clarify comments in GetMappedConfig
| * | Allow imported INTERFACE libraries to specify a link library nameBrad King2016-11-0914-2/+173
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add an `IMPORTED_LIBNAME[_<CONFIG>]` target property to specify a library name to be placed on the link line in place of an interface library since it has no library file of its own. Restrict use of the property to imported `INTERFACE` libraries. This will be particularly useful for find modules that need to provide imported libraries from system SDKs where the full path to the library file is not known. Now such find modules will be able to provide an imported interface library and set `IMPORTED_LIBNAME` to refer to the SDK library by name. Issue: #15267
* | CPack/RPM test for Suggests tagAlexander Adam2016-11-054-0/+41
|/ | | | | | | Suggests tag was not present in older versions of rpmbuild so we test that the rpm package is always generated either with Suggests tag present or skipped if not supported.
* Features: Test cycle diagnostic with language standard meta-featureBrad King2016-11-022-3/+3
| | | | | | | The `cxx_static_assert` feature may be available in C++ 98 mode of some compilers or not available at all in others. Intstead of using an individual feature to test cyclic requirement of a feature requiring C++ 11, use the `std_cxx_11` meta-feature that has exactly this meaning.
* Features: Test feature propagation with language standard meta-featureBrad King2016-11-021-4/+4
| | | | | | | The `cxx_static_assert` feature may be available in C++ 98 mode of some compilers or not available at all in others. Intstead of using an individual feature to test propagation of a feature requiring C++ 11, use the `std_cxx_11` meta-feature that has exactly this meaning.
* Features: Add meta-features requesting awareness of a particular standardBrad King2016-11-021-0/+2
| | | | | | | | | | A common use case of `target_compile_features` is simply to specify that the compiler should be run in a mode that is aware of e.g. C++11. Some projects simply specify a particular C++11-only feature to request this. Provide a first-class way to do this by naming features after the corresponding language standard. Record them as always available in the corresponding standard level so that requesting them always ensures that standard (or higher) is used.
generated by cgit v0.12 at 2025-02-06 12:21:20 (GMT)