summaryrefslogtreecommitdiffstats
path: root/Source/cmGeneratorExpressionEvaluator.h
Commit message (Collapse)AuthorAgeFilesLines
* Extract the ProcessArbitraryContent method.Stephen Kelly2013-05-161-0/+8
|
* Keep track of all targets seen while evaluating a genex.Stephen Kelly2013-02-221-1/+2
| | | | | As dependencies of the generator expression, these will re-exported in try_compile generated code.
* Cache context-independent includes on evaluation.Stephen Kelly2013-02-031-0/+1
| | | | | | | | | | Generator expressions whose output depends on the configuration now record that fact. The GetIncludeDirectories method can use that result to cache the include directories for later calls. GetIncludeDirectories is called multiple times for a target for each configuration, so this should restore performance for multi-config generators.
* Keep track of properties used to determine linker libraries.Stephen Kelly2013-01-081-0/+1
| | | | | Those properties can't later be implicitly defined by the interface of those link libraries.
* Make all relevant targets available in the genex context.Stephen Kelly2013-01-051-1/+3
| | | | | The current node being evaluated transitively in the generator expression must be available to resolve mapped configs.
* Merge topic 'generator-expression-fixes'Brad King2012-11-271-0/+8
|\ | | | | | | | | | | | | b581be0 Genex: Don't segfault on $<FOO,> 07749e3 Genex: Ensure that $<0:...> has a parameter. ee96dc7 Genex: Extract a method to parse parameters.
| * Genex: Extract a method to parse parameters.Stephen Kelly2012-11-261-0/+8
| |
* | Port cmGeneratorExpression to cmTarget from cmGeneratorTarget.Stephen Kelly2012-11-201-2/+1
|/ | | | | | | | | | | Following from the discussion here: http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/3615/focus=5170 (Re: Generator expressisons in target properties, 26 Oct 12:10) we can't split cmTarget API for linking into cmGeneratorTarget. In the future we will probably also need to move the include and compile definitions API back to cmTarget so that it can be used by export().
* Add API to check that dependent target properties form a DAG.Stephen Kelly2012-09-281-4/+8
| | | | | | 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.
* Add a generator expression for target properties.Stephen Kelly2012-09-281-1/+6
| | | | | | | | There are two overloads, so that it can use the operational target when a target property is being evaluated, and a target can alternatively be specified by name. At this point, the generators don't chain. That comes later.
* cmGeneratorExpression: Re-write for multi-stage evaluationStephen Kelly2012-09-181-0/+118
The expressions may be parsed and then cached and evaluated multiple times. They are evaluated lazily so that literals such as ',' can be treated as universal parameter separators, and can be processed from results without appearing literally, and without interfering with the parsing/evaluation of the entire expression.