summaryrefslogtreecommitdiffstats
path: root/Tests
Commit message (Collapse)AuthorAgeFilesLines
* Make CMAKE_HOST_SYSTEM_NAME available in scripting contextGregor Jasny2017-02-191-1/+0
|
* Merge topic 'install_name_policy'Brad King2017-02-1713-0/+59
|\ | | | | | | | | | | | | | | 1ba91291 Add policy CMP0068 separate install_name and RPATH settings on macOS f7b9bf41 Apple: Add BUILD_WITH_INSTALL_NAME_DIR target property 4bff2d14 Apple: Refactor support for using INSTALL_NAME_DIR. 624fb9d7 Help: Format BUILD_WITH_INSTALL_RPATH documentation
| * Add policy CMP0068 separate install_name and RPATH settings on macOSClinton Stimpson2017-02-1413-0/+59
| | | | | | | | | | | | | | | | BUILD_WITH_INSTALL_RPATH, SKIP_BUILD_RPATH, CMAKE_SKIP_RPATH and CMAKE_SKIP_INSTALL_RPATH no longer any effect on the install name of a target on macOS. Fixes: #16589
* | Merge topic 'vs-refactor-toolset-parsing'Brad King2017-02-1611-3/+48
|\ \ | | | | | | | | | | | | | | | f773933f VS: Refactor generator toolset parsing d9e2b9a9 Tests: Split out RunCMake.GeneratorToolset Xcode checks
| * | VS: Refactor generator toolset parsingBrad King2017-02-158-2/+30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We parse `CMAKE_GENERATOR_TOOLSET` values of the forms: * `toolset` * `toolset,host=x64` * `host=x64` Generalize the parsing to support the forms: * `toolset` * `toolset[,key=value]*` * `key=value[,key=value]*` Disallow duplicate keys. Require all but the first field to be of `key=value` form.
| * | Tests: Split out RunCMake.GeneratorToolset Xcode checksBrad King2017-02-154-1/+18
| | | | | | | | | | | | This will allow the behavior of VS and Xcode generators to differ.
* | | Merge topic 'cuda-msvc-flags'Brad King2017-02-165-5/+5
|\ \ \ | | | | | | | | | | | | | | | | | | | | 55fb46d2 CUDA: Fix default compiler flags on Windows d7c80f60 CUDA: Fix test cases to not override CUDA flags
| * | | CUDA: Fix test cases to not override CUDA flagsBrad King2017-02-155-5/+5
| | | | | | | | | | | | | | | | Append to `CMAKE_CUDA_FLAGS` instead of overwriting it.
* | | | Merge topic 'cuda-with-c'Brad King2017-02-154-0/+43
|\ \ \ \ | |/ / / | | / / | |/ / |/| | | | | 1c60231c CUDA: Link to standard system libraries when linking as CUDA 8d75d8dc Tests: Add case for CUDA with C but not C++
| * | CUDA: Link to standard system libraries when linking as CUDABrad King2017-02-141-0/+8
| | | | | | | | | | | | | | | | | | | | | On Windows with MSVC-like host compilers we must honor the standard libraries chosen by the `Platform/Windows-MSVC` module. Otherwise C code linked into the CUDA binary that expects to have these libraries available may not link.
| * | Tests: Add case for CUDA with C but not C++Brad King2017-02-144-0/+35
| | | | | | | | | | | | An executable using CUDA and C should link as CUDA.
| * | Tests: Run clang-format on CUDA codeBrad King2017-02-1416-86/+59
| | |
* | | Tests: Run clang-format on CUDA codeBrad King2017-02-1416-133/+91
| | |
* | | Merge branch 'backport-clang-format-cuda' into clang-format-cudaBrad King2017-02-142-0/+18
|\ \ \ | |/ /
| * | clang-format.bash: Format CUDA source files tooBrad King2017-02-142-0/+18
| | | | | | | | | | | | | | | | | | Add `.clang-format` configuration files for Cuda test directories that use `Standard: Cpp11`. Otherwise clang-format splits the triple angle brackets used for CUDA kernels.
* | | Merge topic 'cmake_provide_include_dir_for_toolkit'Brad King2017-02-144-0/+31
|\ \ \ | |/ / | | | | | | | | | 44f3acb2 CUDA: Detect the toolkit include directories
| * | CUDA: Detect the toolkit include directoriesRobert Maynard2017-02-104-0/+31
| | | | | | | | | | | | | | | The `nvcc -v` output provides what include directories need to be added to use the CUDA toolkit from other languages ( C/C++ ).
* | | Tests/Cuda: Select a CUDA device supporting compute 3.0Pierre Moreau2017-02-102-0/+46
| | |
* | | Tests/Cuda: Return a non-zero code if errors occurredPierre Moreau2017-02-102-6/+8
| | |
* | | Tests/Cuda: Use memory allocated on the GPU in the kernelsPierre Moreau2017-02-102-10/+45
| | |
* | | Tests/Cuda: Add missing separable compilation propertyPierre Moreau2017-02-101-0/+2
| | | | | | | | | | | | | | | | | | | | | This resulted in `mixed_kernel()` returning an "invalid device function" at runtime for `file1_func()`. Suggested-by: Robert Maynard
* | | Tests/Cuda: Fix missing CUDA static library at runtime on macOSPierre Moreau2017-02-101-0/+6
| | | | | | | | | | | | Suggested-by: Robert Maynard
* | | Tests/Cuda: Output error messages to std::cerr instead of std::coutPierre Moreau2017-02-101-2/+2
| | |
* | | Tests/Cuda: Print asynchronous error messages, if anyPierre Moreau2017-02-103-0/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As kernel launches are asynchronous, a `cudaGetLastError()` right after the kernel launch might be executed while the kernel is still running. Synchronizing the device will ensure that all the work is completed before progressing further on, and allows to catch errors that were previously missed. The `cudaGetLastError()` after the `cudaDeviceSynchronize()` is there to reset the error variable to `cudaSuccess`.
* | | Tests/Cuda: Print error message if mixed_kernel failedPierre Moreau2017-02-101-0/+7
| | |
* | | Tests/Cuda: Add identifiers to error messagesPierre Moreau2017-02-102-2/+4
| | |
* | | Tests/Cuda: Print error message if an error occurredPierre Moreau2017-02-102-2/+2
| | | | | | | | | | | | Fixes c59811a2 "CUDA: Tests now state why they are failing when no CUDA card is found."
* | | Merge topic 'vs-nasm'Brad King2017-02-105-1/+35
|\ \ \ | | | | | | | | | | | | | | | | 5ba2c9e5 VS: Add support for ASM_NASM language
| * | | VS: Add support for ASM_NASM languageEvgeny Fimochkin2017-02-075-1/+35
| |/ / | | | | | | | | | Fixes: #16469
* | | Tests: Fix `file://` URLs given to curlBrad King2017-02-106-6/+24
| |/ |/| | | | | | | | | | | Since upstream curl commit curl-7_52_0~131 (URL-parser: for file://[host]/ URLs, the [host] must be localhost, 2016-11-11) we can no longer use URLs of the form `file://c:/...` on Windows. These worked only accidentally before. Use `file:///c:/...` instead.
* | Merge topic 'determine_id_without_user_specified_flags'Brad King2017-02-071-2/+2
|\ \ | | | | | | | | | | | | 72ed051b CMakeDetermineCompilerId: check with and without user-specified flags
| * | CMakeDetermineCompilerId: check with and without user-specified flagsMichael Maltese2017-02-061-2/+2
| |/ | | | | | | | | | | | | | | | | | | | | Clang may raise an error when passed a `-march=` option that doesn't correspond to the current target triple. CMake cannot pass the target triple when determining the compiler id because it doesn't know how yet, but it does pass along user-specified flags. This breaks when those user-specified flags include `-march=`. Fix this use case by also trying to find the compiler id without the user-specified flags. Fixes: #16587
* | FeatureSummary: Add FeatureSummary_<TYPE>_DESCRIPTION global propertiesDaniele E. Domenichelli2017-02-063-0/+250
| | | | | | | | | | | | The global property FeatureSummary_<TYPE>_DESCRIPTION can be defined for each type to replace the type name with the specified string whenever the package type is used in an output string.
* | FeatureSummary: Add DEFAULT_DESCRIPTION option to feature_summaryDaniele E. Domenichelli2017-02-063-0/+129
|/ | | | | If enabled and only one package type is selected, it will print the default title for the selected package type.
* AndroidTestUtilities: do not require ExternalData unconditionallyZack Galbreath2017-02-043-0/+19
| | | | | | | | | | | | Attempting to use AndroidTestUtilities to simply install some local files on device can result in the following error: Neither ExternalData_URL_TEMPLATES nor ExternalData_OBJECT_STORES is set We no longer require these ExternalData-specific variables to be set if no such remote data files are requested. Fixes: #16529
* Tests/Module/WCDH: only use -Werror=undef compiler flag if actually supportedRolf Eike Beer2017-02-021-1/+5
|
* Tests/Module/WCDH: write multi_file_compiler_detection.h before using itRolf Eike Beer2017-02-021-11/+11
| | | | | | | | This was broken in commit 98e6d1e5e426c491e04faa746c11746002e6a69d (Tests/Module/WCDH: make it work with only C features defined) when all C tests were made accessible even if no C++ features are available, but the header was only created if C++ features are available. Fix it by creating the header unconditionally before any checks on the available features.
* Merge topic 'WCDH_allow_unsupported'Brad King2017-02-012-60/+86
|\ | | | | | | | | | | | | | | 1679fecb CompileFeatures Test: make sure the target "CompileFeatures" is always defined 98e6d1e5 Tests/Module/WCDH: make it work with only C features defined c8703e9d WCDH: optionally omit error code for unknown compilers or compiler versions 0de9c398 WCDH: add macro to write simple replacement defines
| * CompileFeatures Test: make sure the target "CompileFeatures" is always definedRolf Eike Beer2017-01-301-10/+8
| | | | | | | | | | | | Everything in there guards against unsupported compilers already, so no need to skip the whole file if no features are defined. This in turn allows to have a simpler fallback in case there is no C++ auto_type feature available.
| * Tests/Module/WCDH: make it work with only C features definedRolf Eike Beer2017-01-301-51/+51
| |
| * WCDH: optionally omit error code for unknown compilers or compiler versionsRolf Eike Beer2017-01-301-1/+29
| | | | | | | | | | | | This allows one to generate a header that will basically always work. In case an unknown compiler or compiler version is encountered it simply falls back to the unsupported case.
* | Merge topic 'topic-reproducible-build'Brad King2017-01-312-0/+2
|\ \ | | | | | | | | | | | | 5181f1f8 Tests: make tests pass with SOURCE_DATE_EPOCH set
| * | Tests: make tests pass with SOURCE_DATE_EPOCH setBernhard M. Wiedemann2017-01-302-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | Fix tests to account for commit 243aed52 (cmTimestamp: Support SOURCE_DATE_EPOCH to override current time, 2017-01-25). In openSUSE we are running the test-suite as part of the build and that failed in these two places when building everything with `SOURCE_DATE_EPOCH` set.
* | | Merge topic '16432-static-frameworks'Brad King2017-01-318-71/+109
|\ \ \ | |_|/ |/| | | | | | | | | | | | | | | | | | | | 071f8e78 Apple: Add support for static frameworks d525754e Xcode: Refactor RunCMake.Framework test to prepare for static frameworks 45405f00 Xcode: Ignore Xcode project warning until issue is fixed 50e1c105 Makefile: For static libraries remove only the "real" lib before creating 8643ca75 Makefile: Re-order list of files to clean
| * | Apple: Add support for static frameworksGregor Jasny2017-01-316-41/+94
| | | | | | | | | | | | Closes: #16432
| * | Xcode: Refactor RunCMake.Framework test to prepare for static frameworksGregor Jasny2017-01-262-33/+18
| | |
| * | Xcode: Ignore Xcode project warning until issue is fixedGregor Jasny2017-01-261-1/+1
| | | | | | | | | | | | Issue: #15272
* | | Merge topic 'FeatureSummary_enhancement'Brad King2017-01-3042-8/+518
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 560574b0 FeatureSummary: Update release notes 3cfde818 FeatureSummary: Refactor to use global properties for package types f0165eb6 FeatureSummary: Allow lists of dependencies in ADD_FEATURE_INFO 9da7bf08 FeatureSummary: Add QUIET_ON_EMPTY option to feature_summary 4cf4aceb FeatureSummary: Add unit tests 614a97a5 FeatureSummary: Do not force OPTIONAL type in SET_PACKAGE_PROPERTIES 65a0bfd8 FeatureSummary: Add deprecation warnings to deprecated commands 4da3cae9 FeatureSummary: Clean printed output
| * | | FeatureSummary: Refactor to use global properties for package typesDaniele E. Domenichelli2017-01-2618-0/+208
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | These new global properties were added: * FeatureSummary_PKG_TYPES: Package types accepted by FeatureSummary (default REQUIRED RECOMMENDED OPTIONAL RUNTIME). * FeatureSummary_REQUIRED_PKG_TYPES: Package types that will cause FeatureSummary to abort when called with FATAL_ON_MISSING_REQUIRED_PACKAGES and a package in these categories is missing (default REQUIRED). * FeatureSummary_DEFAULT_PKG_TYPE: Default package type assigned when not explicitly assigned by the user (default OPTIONAL). This allows to add and remove new package types that can be printed selectively using the "WHAT" argument.
| * | | FeatureSummary: Allow lists of dependencies in ADD_FEATURE_INFODaniele E. Domenichelli2017-01-263-0/+23
| | | |
generated by cgit v0.12 at 2025-01-13 11:48:19 (GMT)