summaryrefslogtreecommitdiffstats
path: root/Tests/RunCMake/CMP0028
Commit message (Collapse)AuthorAgeFilesLines
* Tests: Rename RunCMake.{CMP0028 => LinkItemValidation}Brad King2021-12-2021-127/+0
| | | | Generalize the test name to prepare for cases beyond CMP0028.
* CMP0028: Report the target whose link interface has an offending itemBrad King2021-12-164-12/+36
| | | | | | | | | | | | Previously items linked via the link interface of a dependency were reported in CMP0028 messages as if directly linked by a target. Clarify the messages to indicate that an offending item is actually in the link interface of a given target, regardless of its consumer. Move the check to the end of generation and look through the final set of link implementations and link interfaces that were used for generation. This avoids repeating messages on link interfaces that have multiple consumers.
* CMP0028: Report backtrace to link item rather than target creationBrad King2021-12-164-8/+8
| | | | | | Now that we have proper backtraces for both `LINK_LIBRARIES` and `INTERFACE_LINK_LIBRARIES` entries, we can report them in error messages.
* Tests/RunCMake: Update cmake_minimum_required versionsBrad King2020-06-181-1/+1
| | | | Use 3.3 or 2.8.12 where possible.
* Add deprecation warnings for policies CMP0036 and belowBrad King2017-04-212-0/+20
| | | | | | The OLD behaviors of all policies are deprecated, but only by documentation. Add an explicit deprecation diagnostic for some policies to encourage projects to port away from setting policies to OLD.
* RunCMake: Remove unneeded files.Stephen Kelly2015-02-092-2/+0
| | | | | The default expectation of RunCMake tests is empty content, so there is no need to specify it.
* Tests: Simplify and document policy scopes in RunCMake.CMP* testsBrad King2014-03-061-1/+1
| | | | | Drop unnecessary NO_POLICY_SCOPE options. Document why the remaining options are necessary.
* CMP0028: Trigger on libraries from INTERFACE of dependencies.Stephen Kelly2014-02-0910-0/+43
|
* cmTarget: Fix typoStephen Kelly2013-12-192-2/+2
| | | | 'a ALIAS' -> 'an ALIAS'
* Consider targets with double colons to be IMPORTED or ALIAS targets.Stephen Kelly2013-10-2112-0/+42
Introduce a policy to control the behavior. The AliasTargets unit test already tests that using a double-semicolon in the name is not an error. Change the ExportImport test to use a namespace with a double-semicolon too.