summaryrefslogtreecommitdiffstats
path: root/Tests/RunCMake/target_link_options
Commit message (Collapse)AuthorAgeFilesLines
* LINK_OPTIONS: ensure correct dollar escapingMarc Chevrier2023-07-174-1/+10
| | | | | | Ensure correct escaping for Ninja and Makefile generators. Fixes: #25049
* CUDA: Support CMP0105 on ClangRaul Tambre2021-11-083-31/+34
| | | | | | | Add link flags during the "device compile" step. Enabled the relevant tests. The disable reasons regarding separable compilation were outdated and the actual failure case was device link flags support.
* CUDA Device link: Ensure all link options are correctly formattedMarc Chevrier2021-03-314-0/+20
| | | | Fixes: #21994
* CUDA: Don't RunCMake generate separable compilation tests on ClangRaul Tambre2020-06-031-15/+18
| | | | | | Building these targets was already previously disabled in RunCMakeTest.cmake. Now with us throwing an error for separable compilation during generation on Clang we also need to stop them from being generated.
* Tests: Restore NVCC-specific CUDA testsBrad King2020-05-201-1/+1
| | | | | | | | | | | | | | | | | In commit a653ca9504 (Tests: Update CUDA tests to work with Clang, 2020-03-27) some tests were conditioned using `CMAKE_CUDA_COMPILER_ID`. That is not defined when configuring CMake itself, so it accidentally turned off NVCC-specific CUDA tests altogether. Convert the conditions to check `CMake_TEST_CUDA` for `Clang` instead. That option is added explicitly to builds where we want the tests to run, so we can set it to a value indicating the CUDA compiler vendor. In commit a653ca9504 (Tests: Update CUDA tests to work with Clang, 2020-03-27) the NVCC-specific `CudaOnly.GPUDebugFlag` test was accidentally broken by removing a space when appending `-G` to the CUDA flags. This was covered by the test not running. Restore the space. Fixes: #20727
* Tests: Update CUDA tests to work with ClangRaul Tambre2020-05-151-4/+8
|
* CUDA: Device linking use now link optionsMarc Chevrier2020-04-199-1/+65
| | | | | | | | | | properties LINK_OPTIONS and INTERFACE_LINK_OPTIONS are propagated to the device link step. To control which options are selected for normal link and device link steps, the $<DEVICE_LINK> and $<HOST_LINK> generator expressions can be used. Fixes: #18265
* Genex: Add generator expressions $<DEVICE_LINK> and $<HOST_LINK>Marc Chevrier2020-04-197-0/+54
| | | | | | These generator expressions can only be used in link options properties. These expressions return the arguments respectively for device and host link step, otherwise return an empty string.
* Genex: Add $<LINK_LANGUAGE:...> and $<LINK_LANG_AND_ID:...>Marc Chevrier2020-02-2625-0/+178
| | | | | | This MR may help to solve issues #19757 and #18008 Fixes: #19965
* Ninja: Add multi-config variantKyle Edwards2019-12-131-2/+9
| | | | Co-Authored-by: vector-of-bool <vectorofbool@gmail.com>
* Link properties: must be transitive over private dependency on static libraryMarc Chevrier2019-12-121-3/+6
| | | | | | Ensure transitivity over multiple static libraries. Fixes: bbba701899 (Link properties: must be transitive over private dependency on static library, 2019-12-06)
* Link properties: must be transitive over private dependency on static libraryMarc Chevrier2019-12-098-0/+52
| | | | Fixes: #20022
* cmTargetPropCommandBase: check keywords after parsingBen Boeckel2018-10-262-5/+0
| | | | | | | | | | | | | The following was disallowed: add_library(iface INTERFACE) target_link_libraries(iface PUBLIC) just due to the mention of the `PUBLIC` keyword. Instead, only error if there are actually `PUBLIC` dependencies specified (and analogously for other restrictions). Update tests to expect this new behavior.
* Tests: add tests for empty-value keyword arguments in target_*Ben Boeckel2018-10-264-0/+12
| | | | | | Not all of these commands accept non-compilable (i.e., IMPORTED) targets, so those calls are currently just commented out. If they ever do start to accept them, the tests should be enabled.
* LINK_OPTIONS property: add test for static library.Marc Chevrier2018-08-154-0/+15
| | | | | | | Check that property INTERFACE_LINK_OPTIONS is correctly propagated from static libraries. Issue: #18251
* target_link_options: Add test to verify static library behaviorRobert Maynard2018-08-094-0/+16
| | | | Issue: #18251
* LINK_OPTIONS: Add support of "LINKER:" prefixMarc Chevrier2018-06-069-29/+97
|
* LINK_OPTIONS: Add new family of propertiesMarc Chevrier2018-06-0615-0/+154
This family enable to manage link flags Three new properties: * directory property: LINK_OPTIONS * target properties: LINK_OPTIONS and INTERFACE_LINK_OPTIONS Two new commands * add_link_options(): to populate directory property * target_link_options(): to populate target properties Fixes: #16543
generated by cgit v0.12 at 2024-11-11 17:54:46 (GMT)