summaryrefslogtreecommitdiffstats
path: root/Source/cmGeneratorExpressionDAGChecker.h
Commit message (Collapse)AuthorAgeFilesLines
* Genex: Extend EvaluatingLinkLibraries to also check the top target name.Stephen Kelly2013-06-241-1/+1
| | | | | This will allow testing whether we are evaluating the link libraries of a particular target.
* Use a preprocessor loop to manage the valid transitive properties.Stephen Kelly2013-06-101-3/+15
| | | | | Hopefully this will prevent regressions when adding further transitive properties in the future.
* Add COMPILE_OPTIONS target property.Stephen Kelly2013-06-021-0/+1
| | | | | | This method reads generator expressions from the COMPILE_OPTIONS target property, as well as INTERFACE_COMPILE_OPTIONS from linked dependents.
* Fix constness of accessors.Stephen Kelly2013-02-231-2/+2
|
* Optimize genex evaluation for includes and defines.Stephen Kelly2013-02-021-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | While porting boost to use these features, the generation step took too long (several minutes before I stopped it). The reason was that the boost libraries form a large interdependent mesh. The libraries list their dependencies in their INTERFACE such as: $<LINKED:boost::core>;$<LINKED:boost::config>;$<LINKED:boost::mpl> As boost::core already depends on the boost::config libraries, that expression has no impact on the end-content, as it is removed after the generation step. There is no DAG issue though, so the generator expression evaluation would fully evaluate them. In the case of the config library, it also depends on the core library, so all depends are followed through that again, despite the fact that they've just been evaluated. After this patch, the evaluation skips libraries if they have already been seen via depends or directly in the content. This patch keeps track of targets whose INTERFACE has been consumed already. The INCLUDE_DIRECTORIES and COMPILE_DEFINITIONS properties are whitelisted because repeated content will be stripped out later during generation. For other properties now and in the future, that may not be the case.
* Add API to check if we're reading a includes or defines property.Stephen Kelly2013-01-311-0/+2
| | | | This will allow the implementation of the LINKED generator expression.
* Make INTERFACE determined properties readable in generator expressions.Stephen Kelly2013-01-201-0/+3
| | | | | The properties are evaluated as link-dependent interface properties when evaluating the generator expressions.
* Make cycles in target properties ignored, not an error.Stephen Kelly2013-01-051-3/+9
| | | | | | | | | | | | | | | | Constructs such as these are an error as they are direct self-references: set_property(TARGET foo APPEND PROPERTY INCLUDE_DIRECTORIES $<TARGET_PROPERTY:foo,INCLUDE_DIRECTORIES>) set_property(TARGET foo APPEND PROPERTY INCLUDE_DIRECTORIES $<TARGET_PROPERTY:INCLUDE_DIRECTORIES>) However, this is an indirect self-reference in a cycle, and not an error: set_property(TARGET foo APPEND PROPERTY INCLUDE_DIRECTORIES $<TARGET_PROPERTY:bar,INCLUDE_DIRECTORIES>) set_property(TARGET bar APPEND PROPERTY INCLUDE_DIRECTORIES $<TARGET_PROPERTY:foo,INCLUDE_DIRECTORIES>)
* Add API to check that dependent target properties form a DAG.Stephen Kelly2012-09-281-0/+44
Initially this will only be used to check for self-references, but can be extended to check for cycles when chaining properties of other targets.
generated by cgit v0.12 at 2025-01-07 21:58:25 (GMT)