summaryrefslogtreecommitdiffstats
path: root/Tests
Commit message (Collapse)AuthorAgeFilesLines
* ExternalData: Add support for custom algorithm-to-URL mappingBrad King2015-02-2513-0/+48
| | | | | | | | | Allow URL templates to contain a %(algo:<key>) placeholder that is replaced by mapping the canonical hash algorithm name through a map defined by the <key>. Extend the Module.ExternalData test to cover the behavior. Extend the RunCMake.ExternalData test to cover error cases.
* Merge topic 'osx-framework-search-platform-SDKs'Brad King2015-02-243-1/+10
|\ | | | | | | | | 0ee2a004 OS X: Add platform-specific Frameworks search path
| * OS X: Add platform-specific Frameworks search pathGregor Jasny2015-02-233-1/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Otherwise find_library is unable to lookup the XCTest framework which is not located in the SDK serach path: In the 10.10 SDK the SDK frameworks are located here: $DEVELOPER_DIR/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.10.sdk/System/Library/Frameworks whereas the Platform SDKs are located here: $DEVELOPER_DIR/Platforms/MacOSX.platform/Developer/Library/Frameworks Signed-off-by: Gregor Jasny <gjasny@googlemail.com>
* | Merge topic 'FeatureSummary-no-duplicates'Brad King2015-02-243-0/+13
|\ \ | | | | | | | | | | | | 38ef2b73 FeatureSummary: Print each feature info only once
| * | FeatureSummary: Print each feature info only onceGregor Jasny2015-02-233-0/+13
| |/ | | | | | | | | | | | | If a feature is added multiple times via ADD_FEATURE_INFO it should appear only once in FEATURE_SUMMARY. Signed-off-by: Gregor Jasny <gjasny@googlemail.com>
* | Merge topic 'rpm_at_in_path'Brad King2015-02-242-2/+26
|\ \ | | | | | | | | | | | | 5857ca5e CPackRPM: Drop explicit handling of '@' symbols that breaks them (#14782)
| * | CPackRPM: Drop explicit handling of '@' symbols that breaks them (#14782)Domen Vrankar2015-02-242-2/+26
| |/ | | | | | | | | | | | | | | | | | | The change in commit v2.8.12~218^2 (CPackRPM protect '@' character in filename processed in the spec file, 2013-07-05) was not necessary after commit v2.8.12~439^2 (Add support for componentized USER spec file, 2013-04-01). The latter replaced ${VAR} references in the spec file template string with \@VAR\@ references, thus protecting '@' symbols automatically. This caused CPackRPM to break paths with @ symbols. Revert the change to fix the behavior, and add a test case.
* | Merge topic 'ctest-output-options'Brad King2015-02-2440-1/+265
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ff1ddd2a ctest_upload: Add QUIET option 0b87b2a3 ctest_memcheck: Add QUIET option fc58bdb9 ctest_coverage: Add QUIET option 876a680d ctest_test: Add QUIET option 49ba4545 ctest_build: Add QUIET option f999dc0b ctest_configure: Add QUIET option 645ad117 ctest_update: Add QUIET option 19d1a559 ctest_start: Add QUIET option 1643b905 ctest_submit: Add QUIET option 12db1139 CTest: Add cmCTestOptionalLog macro
| * | ctest_upload: Add QUIET optionZack Galbreath2015-02-236-0/+31
| | |
| * | ctest_memcheck: Add QUIET optionZack Galbreath2015-02-233-1/+3
| | |
| * | ctest_coverage: Add QUIET optionZack Galbreath2015-02-236-0/+37
| | |
| * | ctest_test: Add QUIET optionZack Galbreath2015-02-236-0/+34
| | |
| * | ctest_build: Add QUIET optionZack Galbreath2015-02-236-0/+43
| | |
| * | ctest_configure: Add QUIET optionZack Galbreath2015-02-236-0/+39
| | |
| * | ctest_update: Add QUIET optionZack Galbreath2015-02-232-0/+39
| | |
| * | ctest_start: Add QUIET optionZack Galbreath2015-02-236-0/+30
| | | | | | | | | | | | | | | This suppresses all non-error messages that would have otherwise been printed by this function.
| * | ctest_submit: Add QUIET optionZack Galbreath2015-02-234-0/+9
| | | | | | | | | | | | | | | Specifying this option prevents CTest from printing any non-error messages to the console for this call to ctest_submit().
* | | Merge topic 'test-RunCMake-refactor-ctest'Brad King2015-02-24149-120/+104
|\ \ \ | |/ / | | / | |/ |/| | | | | | | | | | | | | | | | | e2b9e7f7 Tests: Drop unnecessary stderr matching from RunCMake.ctest_memcheck 7ce9f6e2 Tests: Teach RunCMake to tolerate 'Error kstat returned' lines in test output 69de0f7e Tests: Teach RunCMake to tolerate Guard Malloc lines in test output 57f2aa7c Tests: Teach RunCMake to tolerate BullseyeCoverage lines in test output b04c8ec3 Tests: Match curl error in RunCMake.ctest_submit FailDrop-* cases 1d82105e Tests: Rename RunCMake.{CTestMemcheck => ctest_memcheck} d7662141 Tests: Rename RunCMake.{CTestSubmit => ctest_submit} 9b50388b Tests: Split RunCTest helper out of RunCMake.CTest(Submit|Memcheck) 76e7c22b Tests: Rename RunCMake.CTestMemcheck internals to match CTestSubmit
| * Tests: Drop unnecessary stderr matching from RunCMake.ctest_memcheckBrad King2015-02-235-15/+0
| | | | | | | | | | | | | | | | The Dummy*-stderr.txt files were needed only to match platform-specific memcheck tooling output and verify that stderr is otherwise empty. Now that the RunCMake infrastructure knows how to strip such lines before matching, we can simply drop these files and use the default empty string match.
| * Tests: Teach RunCMake to tolerate 'Error kstat returned' lines in test outputBrad King2015-02-231-1/+1
| | | | | | | | | | | | | | | | | | | | When RunCMake tests run on Solaris, the output may contain unexpected lines of the form "Error kstat returned...". These lines are printed by SystemInformationImplementation::RunProcess when called from SystemInformationImplementation::ParseValueFromKStat (see issue #12066). Until someone investigates why kstat returns values outside the range it documents, simply remove such lines from the actual output before matching it against the expected output.
| * Tests: Teach RunCMake to tolerate Guard Malloc lines in test outputBrad King2015-02-231-1/+1
| | | | | | | | | | | | | | When RunCMake tests run under Xcode Guard Malloc, Guard Malloc may add lines of the form "<tool>(<pid>) malloc:..." to the output. Remove such lines from the actual output before matching it against the expected output.
| * Tests: Teach RunCMake to tolerate BullseyeCoverage lines in test outputBrad King2015-02-231-1/+1
| | | | | | | | | | | | When RunCMake tests run under dynamic analysis, Bullseye may add lines of the form "BullseyeCoverage..." to the output. Remove such lines from the actual output before matching it against the expected output.
| * Tests: Match curl error in RunCMake.ctest_submit FailDrop-* casesBrad King2015-02-233-3/+3
| | | | | | | | | | Port the regexes over from the CTestTestFailedSubmit tests for ftp, http, and https. No such match is needed for the other protocols.
| * Tests: Rename RunCMake.{CTestMemcheck => ctest_memcheck}Brad King2015-02-1985-30/+30
| | | | | | | | Follow the convention of naming tests after the command they test.
| * Tests: Rename RunCMake.{CTestSubmit => ctest_submit}Brad King2015-02-1962-37/+37
| | | | | | | | Follow the convention of naming tests after the command they test.
| * Tests: Split RunCTest helper out of RunCMake.CTest(Submit|Memcheck)Brad King2015-02-194-31/+30
| | | | | | | | | | Provide the "run_ctest" macro for use in other tests that also want to cover running "ctest" scripts.
| * Tests: Rename RunCMake.CTestMemcheck internals to match CTestSubmitBrad King2015-02-194-12/+12
| |
* | Merge topic 'rpm_package_architecture'Brad King2015-02-232-0/+14
|\ \ | | | | | | | | | | | | | | | | | | | | | b6f94e6b Help: Add notes for topic 'rpm_package_architecture' f174b919 Tests: CpackRPM test component architecture 3aa9f89d CPackRPM: Support rpm architecture in components 761562fe CPackRPM: Fix CPACK_RPM_PACKAGE_ARCHITECTURE
| * | Tests: CpackRPM test component architectureJoshua A Clayton2015-02-232-0/+14
| | | | | | | | | | | | Test creating rpms of type "noarch", native, and "armv7hf"
* | | Merge topic 'rpm_run_tests_on_other_platforms'Brad King2015-02-231-1/+1
|\ \ \ | | | | | | | | | | | | | | | | 8c0474cd CPackRPM: run tests on more platforms than just Linux
| * | | CPackRPM: run tests on more platforms than just LinuxDomen Vrankar2015-02-231-1/+1
| |/ / | | | | | | | | | | | | Lift the restriction that limits use of CPackRPM tests to Linux OS only because RPM can also be used on e.g. AIX which is Unix OS.
* | | Merge topic 'use-algorithms'Brad King2015-02-231-1/+1
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | bb9d71b4 Replace loops with algorithms. 4afe6c26 cmAlgorithms: Add cmReverseRange adaptor. a3a0a8c2 cmAlgorithms: Add cmFindNot algorithm. 8c74a41f cmRST: Replace two erase with a rotate and larger erase. 61fe1919 cmAlgorithms: Update concept requirement to FowardIterator 09d6125b cmAlgorithms: Move cmRotate out of 'implementation detail' namespace. 8ed6ecac cmRST: Move two algorithms beside each other. dfe49c20 cmRST: Use std::min where appropriate. 21b0654a cmGlobalGenerator: Convert set insert algorithm to vector algorithms. 416df93a Convert some raw loops to cmWrap. 37b88d34 cmAlgorithms: Add cmWrap. a2818093 Use cmJoin where possible. 76207b08 cmCacheManager: Replace loop with algorithm. 60c3bb73 cmGlobalGenerator: Replace loop with algorithm. 05fec779 cmTarget: Port loop to algorithm. 9c225767 cmGlobalGenerator: Replace set::insert algorithm with cmRemoveDuplicates. ...
| * | | cmGlobalGenerator: Convert set insert algorithm to vector algorithms.Stephen Kelly2015-02-201-1/+1
| | | | | | | | | | | | | | | | Adjust test for new error output.
* | | | Merge topic 'private-FindJsonCpp'Brad King2015-02-231-0/+3
|\ \ \ \ | |_|/ / |/| | | | | | | | | | | | | | | a41d621d bootstrap: Add --(no-)system-jsoncpp options a5768442 FindJsonCpp: Drop new module due to upstream jsoncpp providing package
| * | | FindJsonCpp: Drop new module due to upstream jsoncpp providing packageBrad King2015-02-201-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since jsoncpp 0.7.0 (2014-11-20) the upstream may provide a CMake package configuration file such that find_package(jsoncpp) will find a jsoncppConfig.cmake file. In order to avoid conflicting with this (especially on case-insensitive filesystems), and since we always prefer projects to provide package config files (that they maintain), it is better to not provide FindJsonCpp publicly. Move FindJsonCpp into a private source directory that is not installed so that we can still use it for building CMake itself. Reported-by: Ryan Pavlik <ryan.pavlik@gmail.com>
* | | | Merge topic 'find-command-prefix-from-PATH'Brad King2015-02-2015-0/+54
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | ffc06c12 Teach find_(library|file|path) to get prefixes from PATH (#15370)
| * | | | Teach find_(library|file|path) to get prefixes from PATH (#15370)Brad King2015-02-1915-0/+54
| | |/ / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The find_package command already knows how to compute installation prefixes from PATH. Use the same approach to establish prefixes for find_library, find_file, and find_path to use to look in directories like "<prefix>/lib[/<arch>]" and "<prefix>/include" for libraries and headers. This will reduce the amount of configuration end users need to do to establish a work environment rooted under a specific prefix.
* | | | Fortran: Test that CMAKE_Fortran_COMPILER_VERSION is set (#15372)Brad King2015-02-191-9/+1
|/ / / | | | | | | | | | | | | Update the CMakeOnly.CompilerIdFortran test to require that the variable is set instead of just warning. We already require it for C and CXX.
* | | Tests: Consolidate detection of 'rpmbuild'Brad King2015-02-132-11/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | Several tests use slight variations of the same logic to enable CPack RPM tests. Consolidate this logic into one check before any tests are added. Look for 'rpmbuild' only on Linux and only when the test build tree does not have spaces in the path. In particular, this will make the result available in time for the RunCMake.CPackRPM test to be activated even if CMake is configured exactly once.
* | | Xcode: Teach XCODE_ATTRIBUTE target properties about generator expressionsGregor Jasny2015-02-126-0/+24
| | | | | | | | | | | | Signed-off-by: Gregor Jasny <gjasny@googlemail.com>
* | | install: Allow generator expressions in TARGETS DESTINATION (#14317)Brad King2015-02-119-3/+25
| |/ |/| | | | | | | | | | | | | | | | | | | | | This will allow per-config destinations for targets in EXPORT sets. Using multiple install(TARGETS) with separate CONFIGURATIONS is rejected as a target appearing more than once in an export set. Now instead one can write install(TARGETS foo EXPORT exp DESTINATION lib/$<CONFIG>) to get a single logical membership of the target in the export set while still having a per-config destination.
* | Merge topic 'export-interface-source-files'Brad King2015-02-1165-218/+365
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | f7e33820 Add release notes for export-interface-source-files. 6da65b39 Allow export of targets with INTERFACE_SOURCES. 736bcb96 Tests: Move IfacePaths test stderr files. d9f8390d Tests: Run IfacePaths tests with a parameter. cc152094 Tests: Split part of include_directories test to a generic location.
| * | Allow export of targets with INTERFACE_SOURCES.Stephen Kelly2015-02-1027-17/+143
| | | | | | | | | | | | | | | | | | Use the same rules for paths in source and binary dirs in installed INTERFACE_SOURCES as are used for INTERFACE_INCLUDE_DIRECTORIES.
| * | Tests: Move IfacePaths test stderr files.Stephen Kelly2015-02-1011-0/+1
| | | | | | | | | | | | | | | Rename the files with a property-specific name, so that additional properties can be easily tested.
| * | Tests: Run IfacePaths tests with a parameter.Stephen Kelly2015-02-099-21/+35
| | | | | | | | | | | | | | | | | | Run the tests for the INCLUDE_DIRECTORIES INTERFACE property in a specific build location, and update the stderr expectation to match the new output.
| * | Tests: Split part of include_directories test to a generic location.Stephen Kelly2015-02-0940-157/+163
| | | | | | | | | | | | | | | | | | | | | | | | | | | The moved tests are related to paths in INTERFACE_INCLUDE_DIRECTORIES in general, and when exporting, and covering cases of the install location being within the build or source prefix etc. Other build properties containing paths should have similar tests, so this allows some parameterization while keeping the preparation of the various directory structures.
* | | Merge topic 'test-RunCMake-updates'Brad King2015-02-1059-61/+18
|\ \ \ | |/ / | | | | | | | | | | | | | | | c0d8e715 RunCMake: Allow specifying the stderr file for a test. 68d29f51 RunCMake: Allow specifying the directory to run tests in. 1c3918ff RunCMake: Remove unneeded files.
| * | RunCMake: Allow specifying the stderr file for a test.Stephen Kelly2015-02-091-1/+4
| | |
| * | RunCMake: Allow specifying the directory to run tests in.Stephen Kelly2015-02-091-3/+14
| | |
| * | RunCMake: Remove unneeded files.Stephen Kelly2015-02-0957-57/+0
| | | | | | | | | | | | | | | The default expectation of RunCMake tests is empty content, so there is no need to specify it.