summaryrefslogtreecommitdiffstats
path: root/Tests/RunCMake/install/RunCMakeTest.cmake
Commit message (Collapse)AuthorAgeFilesLines
* export: Do not fail generation for separate namelink only caseDeniz Bahadir2020-12-011-0/+1
| | | | | | | | Update the change from commit 64690f6df0 (export: Do not fail generation for namelink-only case, 2020-10-09, v3.19.0-rc1~7^2) to also handle separate namelink-only and namelink-skip calls. Fixes: #21529
* export: Do not fail generation for namelink-only caseDeniz Bahadir2020-10-091-0/+2
|
* ISPC: Support generation for multiple instruction setsRobert Maynard2020-09-041-0/+5
|
* Tests: Factor out RunCMake.file-GET_RUNTIME_DEPENDENCIES testBrad King2020-06-161-39/+0
| | | | Move the `file(GET_RUNTIME_DEPENDENCIES)` cases out of `RunCMake.install`.
* Tests: Fix RunCMake.install LDFLAGS treatmentBrad King2020-05-261-2/+1
| | | | | | In commit d806bd2e8c (Tests: Update test suite to run in an Anaconda environment, 2020-03-30) an extra `}` was left in the value of the modified `LDFLAGS`. Remove it. While at it, simplify the code.
* Tests: Update test suite to run in an Anaconda environmentRobert Maynard2020-05-211-0/+7
|
* file: GetRuntimeDependencies use CMAKE_OBJDUMP when applicableRobert Maynard2020-04-061-0/+1
| | | | | | | | | On machines where the gnu bin utils are prefixed, or suffixed the file(GET_RUNTIME_DEPENDENCIES ) command would fail without explicitly setting the location of objdump. Now we pre-populate the variables used to find objdump based on the gnu bin utils, so that these use cases are better supported
* Tests: Disable test on problematic versions of install_name_toolKyle Edwards2020-01-271-4/+6
| | | | | | | According to https://cmake.org/pipermail/cmake-developers/2015-September/026462.html, there is a bug in Xcode 7.0's install_name_tool that manifests when we try to test file(GET_RUNTIME_DEPENDENCIES). Add a cache option to disable this test.
* cmInstallTargetGenerator: Add tests for the RPATH_CHANGE ruleDennis Klein2019-06-131-0/+16
|
* file: Add GET_RUNTIME_DEPENDENCIES modeKyle Edwards2019-06-101-0/+30
| | | | Co-Authored-by: Bryon Bean <bryon.bean@kitware.com>
* install: Do not crash on imported global targetBrad King2019-03-071-0/+1
| | | | | | | | | | | Since commit e89ad0f94e (install: Allow installing targets created in another directory, 2018-06-18, v3.13.0-rc1~407^2) the `install(TARGETS)` command may find a global-scoped target outside the calling directory. Ignore an `IMPORTED GLOBAL` target if it is found in this way. Imported targets cannot be installed, and trying to do so violates internal invariants. Fixes: #19022
* install: Teach CODE,SCRIPT modes to evaluate generator expressionsJon Chronopoulos2018-12-221-0/+3
| | | | | | | This also introduces CMP0087 which will keep the OLD behaviour of not evaluating generator expressions Fixes: #15785
* install: Add sane set of defaults for DESTINATION and file type parametersKyle Edwards2018-11-071-0/+46
| | | | | | | | | | | | If the user does not specify a DESTINATION for a target type, the install() command checks to see if the appropriate variable from GNUInstallDirs is set. If it is not, then it uses an appropriate hard-coded guess. In addition, for FILES and DIRECTORY, the user can specify a file type instead of a DESTINATION, and the command will use the appropriate variable from GNUInstallDirs, or a hard-coded guess if it is not set.
* install: Revert CODE,SCRIPT support for generator expressionsBrad King2018-10-111-2/+0
| | | | | | | | | | | | | | | | Revert commit v3.13.0-rc1~441^2 (install: Teach CODE,SCRIPT modes to evaluate generator expressions, 2018-05-29). Unfortunately it has been found to break existing code in a real project, e.g. install(CODE [[ message("$<FOOBAR>") ]]) Address this regression by reverting support for the 3.13 release series. Support can be restored later with a policy for compatibility. Issue: #15785 Fixes: #18435
* Tests: Add test for install(SCRIPT ... COMPONENT)Kyle Edwards2018-07-171-0/+1
|
* Tests: Add test for InstallRequiredSystemLibrariesKyle Edwards2018-07-171-0/+1
|
* Tests: Add test for install(TARGETS) RPATH functionalityKyle Edwards2018-07-171-0/+1
|
* Tests: Add test for install(FILES) with PERMISSIONSKyle Edwards2018-07-171-0/+1
|
* Tests: Add test for installing parts of targets in different directoriesKyle Edwards2018-07-171-0/+1
|
* Tests: Add test for install(DIRECTORY) with PATTERN and REGEXKyle Edwards2018-07-171-0/+1
|
* Tests: Add test for CONFIGURATIONS parameter of install()Kyle Edwards2018-07-171-0/+1
|
* Tests: Add test for install(<SCRIPT|CODE>)Kyle Edwards2018-07-171-0/+1
|
* Tests: Add test for <PRE|POST>_INSTALL_SCRIPTKyle Edwards2018-07-171-0/+1
|
* Tests: Add test for deprecated install_*() commandsKyle Edwards2018-07-171-0/+2
|
* Tests: Add tests for *OUTPUT_NAME propertiesKyle Edwards2018-07-171-0/+4
|
* Tests: Add test for install(DIRECTORY ... OPTIONAL)Kyle Edwards2018-07-171-0/+1
|
* Tests: Add tests for install(<TARGETS|FILES> ... OPTIONAL)Kyle Edwards2018-07-171-0/+2
|
* install: Allow installing targets created in another directoryZack Galbreath2018-06-181-0/+2
| | | | | | | | Previously, `install(TARGETS)` would only accept targets created in the same directory scope. Relax this restriction by searching the global scope when determining whether or not a target exists. Fixes: #14444
* install: Teach CODE,SCRIPT modes to evaluate generator expressionsJon Chronopoulos2018-06-071-0/+2
| | | | Fixes: #15785
* install: add test for new NAMELINK_COMPONENT parameterKyle Edwards2018-05-031-0/+7
|
* Tests: Add case for install(FILES) with TARGET_OBJECTSBrad King2017-04-261-0/+4
|
* Tests: Generalize RunCMake.install internal infrastructureBrad King2017-04-261-6/+10
| | | | Allow `run_install_test` to be used for simpler cases.
* Merge topic 'install-EXCLUDE_FROM_ALL'Brad King2016-02-091-0/+45
|\ | | | | | | | | | | | | 586e56d0 Help: Add notes for topic 'install-EXCLUDE_FROM_ALL' d321c196 Tests: Add cases for install() command EXCLUDE_FROM_ALL option 18ce97c4 install: Add EXCLUDE_FROM_ALL option (#14921)
| * Tests: Add cases for install() command EXCLUDE_FROM_ALL optionBrad King2016-02-041-0/+45
| |
* | install(EXPORT): Fix crash on target in another directoryBrad King2016-02-051-0/+1
|/ | | | | | | | | | | | | | | | Refactoring merged by commit v3.5.0-rc1~299 (Merge topic 'use-generator-target', 2015-10-20) in and around commit v3.5.0-rc1~299^2~13 (cmExportSet: Store a cmGeneratorTarget, 2015-10-17) changed export sets to delay looking up actual targets and stores only their names. However, in InstallCommand::HandleExportMode we need to lookup targets immediately to check them for EXPORT_LINK_INTERFACE_LIBRARIES. The check was accidentally made local to the current directory, so if an export set contains a target from another directory the lookup fails and CMake crashes. Fix the check to look up the target name globally, and tolerate when no target is found just in case. Reported-by: Kelly Thompson <kgt@lanl.gov>
* install: Allow generator expressions in DIRECTORYYves Frederix2016-01-131-0/+1
| | | | | Teach install(DIRECTORY) to support generator expressions in the list of directories, much like install(FILES) already supports.
* install: Allow generator expressions in DIRECTORY DESTINATIONRobert Goulet2015-09-241-0/+1
|
* Tests: Cover install(FILES) with a genex DESTINATIONBrad King2015-09-231-0/+1
|
* install: Disallow installing export() result.Stephen Kelly2015-05-141-0/+3
|
* install: Allow generator expressions in TARGETS DESTINATION (#14317)Brad King2015-02-111-0/+1
| | | | | | | | | | | | 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.
* install(DIRECTORY): Add MESSAGE_NEVER option to avoid output (#13761)Brad King2014-06-241-0/+2
| | | | | | | | | | | | Installing large directories, e.g., the output of a doxygen run, prints one line per file resulting in too much noise in the build output. Add an option to the install(DIRECTORY) command to not print anything upon make install. Extend the RunCMake.install test with cases covering MESSAGE_NEVER behavior of the install(DIRECTORY) command. Suggested-by: Stefan Eilemann <Stefan.Eilemann@epfl.ch>
* install: Add CMAKE_INSTALL_MESSAGE variable (#13761)Brad King2014-06-241-0/+1
| | | | | | | | | Create a variable to allow users to control which installation messages are printed. In particular, provide a "LAZY" setting that prints "Installing" messages but not "Up-to-date" messages. This is desirable for incremental re-installations. Suggested-by: J Decker <d3ck0r@gmail.com>
* file(INSTALL): Report existing DIRECTORY as Up-to-dateBrad King2014-06-241-0/+1
| | | | | | | | | | | Teach cmFileCopier::InstallDirectory to detect whether the destination directory exists. If so, report it as "Up-to-date" instead of "Installing". This resolves message asymmetry with file installations. Extend the RunCMake.file and RunCMake.install tests to check the installation output on both the first and second run. Suggested-by: J Decker <d3ck0r@gmail.com>
* InstallRules: added new variable to disable generation of install rulesNils Gladitz2014-01-081-0/+4
The boolean variable CMAKE_SKIP_INSTALL_RULES allows disabling generation of install rules for projects which don't want them.
generated by cgit v0.12 at 2025-09-09 18:15:22 (GMT)