summaryrefslogtreecommitdiffstats
path: root/Tests/RunCMake
Commit message (Collapse)AuthorAgeFilesLines
* try_compile: extend CMP0067 to honor language standards for CUDA.Robert Maynard2016-12-126-0/+23
|
* Merge topic 'try_compile-lang-std'Brad King2016-12-0717-0/+214
|\ | | | | | | | | | | | | f72ba42b try_compile: Add policy CMP0067 to honor language standards 45aa03b9 try_compile: Add options to specify language standards 3bb2051e try_compile: Stop processing when test build system fails to generate
| * try_compile: Add policy CMP0067 to honor language standardsBrad King2016-12-065-0/+90
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Projects use `try_compile` to check if they will be able to compile some particular source code. When a language standard variable like `CMAKE_CXX_STANDARD` is set, then the project intends to compile source code using a compiler mode for that standard. Therefore it makes sense for `try_compile` to use that standard in the test project too. Unfortunately this was not done when support for the `CMAKE_CXX_STANDARD` variable was first implemented. Add a policy to introduce the improved behavior in a compatible way. Closes: #16456
| * try_compile: Add options to specify language standardsBrad King2016-12-0615-0/+124
| | | | | | | | | | | | | | | | | | Give `try_compile` callers a way to control the `CXX_STANDARD`, `CXX_STANDARD_REQUIRED`, and `CXX_EXTENSIONS` properties of the generated test target (or the `C` equivalents) in order to compile a test source for a particular language standard. Issue: #16456
* | CPackRPM now supports multiple directives in CPACK_RPM_USER_FILELISTHarry Mallon2016-12-034-0/+28
|/ | | | | | | | * In older version "%dir %attr(-, root, root) foo" would put "%dir foo" in the final spec file. * Also added comment to describe this and advise not not to add trailing slashes to directories in USER_FILELIST. * Includes test in RunCMake CPack which now passes.
* Merge topic 'execute_process-encoding'Brad King2016-12-029-0/+26
|\ | | | | | | | | 2ed473b3 execute_process: Add ENCODING option for Windows child process output
| * execute_process: Add ENCODING option for Windows child process outputDāvis Mosāns2016-11-309-0/+26
| | | | | | | | Different applications can use different output encodings.
* | VS: Add target property VS_DEBUGGER_WORKING_DIRECTORYMichael Stürmer2016-11-303-0/+28
| |
* | Merge topic 'msbuild-customization'Brad King2016-11-304-0/+38
|\ \ | | | | | | | | | | | | e3909918 VS: Add option to customize vcxproj user props file
| * | VS: Add option to customize vcxproj user props fileMichael Stürmer2016-11-294-0/+38
| | | | | | | | | | | | | | | | | | Add a `VS_USER_PROPS_CXX` target property to set the user props file of the generated `.vcxproj` file to be something other than the default `$(UserRootDir)\\Microsoft.Cpp.$(Platform).user.props`.
* | | Make error message of standalone endwhile command consistentDaniel Pfeifer2016-11-291-1/+1
| |/ |/| | | | | with the error messages of endforeach, endmacro, endfunction, etc.
* | Merge topic 'vs-default-build-package'Brad King2016-11-293-0/+32
|\ \ | | | | | | | | | | | | 9e3164df VS: Add option to place `PACKAGE` target in solution default build
| * | VS: Add option to place `PACKAGE` target in solution default buildMichael Stürmer2016-11-293-0/+32
| |/ | | | | | | | | Add a `CMAKE_VS_INCLUDE_PACKAGE_TO_DEFAULT_BUILD` variable to control this behavior.
* | Merge topic 'try_compile-honor-CMAKE_WARN_DEPRECATED'Brad King2016-11-292-0/+20
|\ \ | | | | | | | | | | | | 6d604c49 try_compile: Honor CMAKE_WARN_DEPRECATED in test project
| * | try_compile: Honor CMAKE_WARN_DEPRECATED in test projectBrad King2016-11-222-0/+20
| | | | | | | | | | | | | | | | | | | | | | | | This causes the `-Wno-deprecated` option to be honored even inside a `try_compile` test project, which is needed to suppress all deprecation warnings as the option documents. Closes: #16446
* | | Tests: CPack test documentation faceliftDomen Vrankar2016-11-271-32/+136
| | |
* | | Tests: CPack/DEB test change prerequirements checkDomen Vrankar2016-11-274-6/+11
| | | | | | | | | | | | | | | | | | | | | Prerequirements should be searched for in generator prerequirements function and only checked for presence in configure file in per test prerequirements function.
* | | Tests: source CPack tests don't require build stageDomen Vrankar2016-11-272-3/+3
| | |
* | | Tests: CPack test set packaging typeDomen Vrankar2016-11-2725-158/+130
| | | | | | | | | | | | | | | | | | | | | | | | | | | CPack tests can now define one or more packaging types and that test will be executed once per generator per packaging type. This also enables us to set default values per packaging type for each generator which makes tests shorter.
* | | Tests: remove generator prefix from CPack test nameDomen Vrankar2016-11-2719-7/+7
| | |
* | | Tests: CPack test long_filenames prerequirementsDomen Vrankar2016-11-271-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | Fakeroot executable is already searched for in DEB packager tests prerequirements so the test prerequirement just has to check that it is present in config file and not search for it once more.
* | | Tests: CPack test use same content listDomen Vrankar2016-11-2722-107/+154
| | | | | | | | | | | | | | | | | | | | | | | | Content list for a certain test should be the same between different generators so whenever possible use a single expected files list per file for all generators.
* | | 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.
* | 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-151-1/+1
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | 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
| |
* | 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.
generated by cgit v0.12 at 2025-01-26 02:22:42 (GMT)