| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
The current node being evaluated transitively in the generator
expression must be available to resolve mapped configs.
|
|\
| |
| |
| |
| |
| |
| | |
b581be0 Genex: Don't segfault on $<FOO,>
07749e3 Genex: Ensure that $<0:...> has a parameter.
ee96dc7 Genex: Extract a method to parse parameters.
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
| |
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().
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
| |
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.
|
|
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.
|