1. 28 Aug, 2013 1 commit
  2. 24 Jul, 2013 1 commit
    • Stephen Kelly's avatar
      Remove the LINK_LANGUAGE generator expression. · 4f6bd702
      Stephen Kelly authored and Brad King's avatar Brad King committed
      It accepted an optional argument to test for equality, but no way
      to get the linker language of a particular target.
      TARGET_PROPERTY provides this flexibility and STREQUAL provides
      the necessary API for equality test.
      Extend the CompileDefinitions test to cover accessing the
      property of another target.
  3. 28 Jun, 2013 1 commit
  4. 12 Jun, 2013 1 commit
  5. 11 Jun, 2013 1 commit
  6. 02 Jun, 2013 1 commit
  7. 24 May, 2013 1 commit
  8. 16 May, 2013 1 commit
    • Stephen Kelly's avatar
      Add the JOIN generator expression. · a7ba4520
      Stephen Kelly authored
      This generator expression joins a list with a separator. The separator
      may contain arbitrary content, such as commas, which is ordinarily a
      delimiter in the generator expression syntax.
  9. 07 May, 2013 1 commit
  10. 12 Mar, 2013 1 commit
  11. 25 Feb, 2013 1 commit
    • Stephen Kelly's avatar
      Revert "Add the TARGET_DEFINED generator expression" · cbf07569
      Stephen Kelly authored
      This reverts commit 2bee6f5b.
      This expression is not used, and has a semantic which is not completely
      optimal (namely considering utility targets to be targets, though
      usually we are interested in linkable targets).
      Remove it so that we have more freedom to define better expressions in
      the future.
  12. 13 Feb, 2013 1 commit
  13. 31 Jan, 2013 1 commit
    • Stephen Kelly's avatar
      Add the $<LINKED:...> generator expression. · 0b92602b
      Stephen Kelly authored
      This is both a short form of using a TARGET_DEFINED expression
      together with a TARGET_PROPERTY definition, and a way to strip
      non-target content from interface properties when exporting.
  14. 27 Jan, 2013 1 commit
  15. 24 Jan, 2013 1 commit
  16. 17 Jan, 2013 1 commit
    • Stephen Kelly's avatar
      Add the $<TARGET_POLICY> expression · 6c8d8afe
      Stephen Kelly authored
      This new expression allows checking how a policy was set when a target
      was created.  That information is only recorded for a subset of policies,
      so a whitelist is used.
  17. 13 Jan, 2013 1 commit
  18. 04 Jan, 2013 2 commits
    • Stephen Kelly's avatar
      Add the TARGET_NAME generator expression. · b0c8f73e
      Stephen Kelly authored
      It will be used as a preprocessing marker.
    • Stephen Kelly's avatar
      GenEx: Add expressions to specify build- or install-only values · b2f1700b
      Stephen Kelly authored
      This is for specifying INCLUDE_DIRECTORIES relevant to the build-location
      or the install location for example:
       set_property(TARGET foo PROPERTY
      A 'bar' target can then use:
       set_property(TARGET bar PROPERTY
      and it will work whether foo is in the same project, or an imported target
      from an installation location, or an imported target from a build location
      generated by the export() command.
      Because the generator expressions are only evaluated at build-time, these
      new expressions are equivalent to the ZeroNode and OneNode.
      The GeneratorExpression test is split into parts. Some shells can't run
      the custom command as it is getting too long.
  19. 29 Sep, 2012 1 commit
  20. 28 Sep, 2012 2 commits
  21. 15 Aug, 2012 2 commits
    • Brad King's avatar
      Add $<CONFIG:...> boolean query generator expression · 9d9f6167
      Brad King authored
      This expression evaluates to '1' or '0' to indicate whether the build
      configuration for which the expression is evaluated matches tha named
      configuration.  In combination with the "$<0:...>" and "$<1:...>"
      expressions this allows per-configuration content to be generated.
    • Brad King's avatar
      Add boolean generator expressions · ebf05abd
      Brad King authored
      Add generator expressions that combine and use boolean test results:
       $<0:...>         = empty string (ignores "...")
       $<1:...>         = content of "..."
       $<AND:?[,?]...>  = '1' if all '?' are '1', else '0'
       $<OR:?[,?]...>   = '0' if all '?' are '0', else '1'
       $<NOT:?>         = '0' if '?' is '1', else '1'
      These will be useful to evaluate (future) boolean query expressions and
      condition content on the results.  Include tests and documentation.
  22. 15 Dec, 2010 1 commit