summaryrefslogtreecommitdiffstats
path: root/Tests/RunCMake/CompatibleInterface/RunCMakeTest.cmake
Commit message (Collapse)AuthorAgeFilesLines
* cmTarget: Test impliedByUse number-compatible properties.Stephen Kelly2014-01-041-0/+1
| | | | | | | | | Test that it is an error to read a number-compatible property to determine the link implementation. An alternative would be to consider the value to be "0", however, that is too arbitrary given the use-cases of this feature. Values from this feature may be used in setting a define, where "0" may have special or invalid meaning and should be explicit.
* cmTarget: Fix the property compatibility error messageStephen Kelly2014-01-041-0/+1
| | | | | | | Don't refer to 'both', but a 'mixture'. List all compatible interface property types possible. Add another test for a mixture of three compatibilities.
* cmTarget: Require a compatible INTERFACE_AUTOUIC_OPTIONS from dependencies.Stephen Kelly2013-12-081-0/+5
| | | | | | | | | Revert the origin-tracking infrastructure from commit 98093c45 (QtAutoUic: Add INTERFACE_AUTOUIC_OPTIONS target property., 2013-11-20). Use the compatibility-tracking for compatible strings instead. If two different dependencies require different AUTOUIC_OPTIONS, cmake will now appropriately issue an error.
* cmTarget: Report origin of COMPATIBLE_INTERFACE properties.Stephen Kelly2013-12-081-0/+1
|
* Ensure type specific compatible interface properties do not intersect.Stephen Kelly2013-02-071-0/+1
| | | | | Before, the boolean version would always win, and the string one would be ignored.
* Add the COMPATIBLE_INTERFACE_STRING property.Stephen Kelly2013-01-241-0/+4
|
* Make INTERFACE determined properties readable in generator expressions.Stephen Kelly2013-01-201-0/+6
The properties are evaluated as link-dependent interface properties when evaluating the generator expressions.