1. 19 Dec, 2013 3 commits
  2. 27 Nov, 2013 1 commit
  3. 25 Nov, 2013 1 commit
    • Stephen Kelly's avatar
      INTERFACE_LIBRARY: Avoid codepaths which set unneeded properties. · 0bfcb450
      Stephen Kelly authored
      As an INTERFACE_LIBRARY has no direct link dependencies, we can
      short-circuit in cmGeneratorExpressionEvaluator and
      in cmGlobalGenerator::CheckLocalGenerators.
      As they do not generate any output directly, any generate- or install-
      related code acn also be short-circuited. Many of the local generators
      already do this.
      Because only INTERFACE related properties make sense on INTERFACE_LIBRARY
      targets, avoid setting other properties, for example via defaults.
  4. 21 Nov, 2013 1 commit
  5. 09 Nov, 2013 2 commits
  6. 01 Nov, 2013 1 commit
    • Brad King's avatar
      Genex: Reject $<TARGET_FILE:...> for object libraries (#14532) · d9605897
      Brad King authored
      Teach the cmGeneratorExpressionEvaluator filesystem artifact logic
      to reject OBJECT_LIBRARY targets since they have no main artifact.
      Without the explicit rejection evaluation falls through to an
      internal CMake error message in cmTarget::GetOutputInfo.
      Extend the RunCMake.GeneratorExpression test to cover these cases.
  7. 31 Oct, 2013 1 commit
    • Stephen Kelly's avatar
      cmTarget: Make GetProperty() const. · c4373b33
      Stephen Kelly authored
      This has follow-on effects for other methods and classes. Further
      work on making the use of const cmTarget pointers common can be
      done, particularly with a view to generate-time methods.
  8. 24 Oct, 2013 1 commit
    • Stephen Kelly's avatar
      cmTarget: Add interface for compatible numeric properties · ff6c4013
      Stephen Kelly authored
      When using the boost MPL library, one can set a define to increase
      the limit of how many variadic elements should be supported. The
      default for BOOST_MPL_LIMIT_VECTOR_SIZE is 20:
      If the foo library requires that to be set to 30, and the independent
      bar library requires it to be set to 40, consumers of both need to set
      it to 40.
       add_library(foo INTERFACE)
       set_property(TARGET foo PROPERTY INTERFACE_boost_mpl_vector_size 30)
       set_property(TARGET foo PROPERTY COMPATIBLE_INTERFACE_NUMBER_MAX boost_mpl_vector_size)
       target_compile_definitions(foo INTERFACE BOOST_MPL_LIMIT_VECTOR_SIZE=$<TARGET_PROPERTY:boost_mpl_vector_size>)
       add_library(bar INTERFACE)
       set_property(TARGET bar PROPERTY INTERFACE_boost_mpl_vector_size 40)
       # Technically the next two lines are redundant, but as foo and bar are
       # independent, they both set these interfaces.
       set_property(TARGET bar PROPERTY COMPATIBLE_INTERFACE_NUMBER_MAX boost_mpl_vector_size)
       target_compile_definitions(bar INTERFACE BOOST_MPL_LIMIT_VECTOR_SIZE=$<TARGET_PROPERTY:boost_mpl_vector_size>)
       target_link_libraries(user foo bar)
      Because the TARGET_PROPERTY reads the boost_mpl_vector_size property
      from the HEAD of the dependency graph (the user target), and because
      that property appears in the COMPATIBLE_INTERFACE_NUMBER_MAX of
      the dependencies of the user target, the maximum value for it is
      chosen for the compile definition, ie, 40.
      There are also use-cases for choosing the minimum value of a number.
      In Qt, deprecated API can be disabled by version. Setting the
      definition QT_DISABLE_DEPRECATED_BEFORE=0 disables no deprecated
      API. Setting it to 0x501000 disables API which was deprecated before
      Qt 5.1 etc.
      If two dependencies require the use of API which was deprecated in
      different Qt versions, then COMPATIBLE_INTERFACE_NUMBER_MIN can be
      used to ensure that both can compile.
  9. 22 Oct, 2013 2 commits
  10. 21 Oct, 2013 1 commit
    • Rolf Eike Beer's avatar
      use size_t for GeneratorExpressionContent::ContentLength to fix some warnings · a80fe4b1
      Rolf Eike Beer authored
      CMake/Source/cmGeneratorExpressionParser.cxx: In member function ‘void cmGeneratorExpressionParser::ParseGeneratorExpression(std::vector<cmGeneratorExpressionEvaluator*>&)’:
      CMake/Source/cmGeneratorExpressionParser.cxx:116:55: warning: conversion to ‘unsigned int’ from ‘long int’ may alter its value [-Wconversion]
      CMake/Source/cmGeneratorExpressionParser.cxx:240:39: warning: conversion to ‘int’ from ‘long int’ may alter its value [-Wconversion]
  11. 28 Aug, 2013 1 commit
  12. 27 Aug, 2013 1 commit
    • Stephen Kelly's avatar
      Genex: Fix evaluation of MAP_IMPORTED_CONFIG_<CONFIG> · 15d98a42
      Stephen Kelly authored
      Commit 10a069b5 (Genex: Fix $<CONFIG> with IMPORTED targets and
      multiple locations., 2013-07-15) changed the logic here to include
      handling of the MAP_IMPORTED_CONFIG_<CONFIG> target property, but
      it was buggy in several ways.
      Uppercase the configs in all cases, and compare the mapped configs
      with the parameter to the CONFIG genex, instead of with the key of
      the mapping.
  13. 02 Aug, 2013 1 commit
    • Stephen Kelly's avatar
      Add the ALIAS target concept for libraries and executables. · 370bf554
      Stephen Kelly authored
      * The ALIAS name must match a validity regex.
      * Executables and libraries may be aliased.
      * An ALIAS acts immutable. It can not be used as the lhs
        of target_link_libraries or other commands.
      * An ALIAS can be used with add_custom_command, add_custom_target,
        and add_test in the same way regular targets can.
      * The target of an ALIAS can be retrieved with the ALIASED_TARGET
        target property.
      * An ALIAS does not appear in the generated buildsystem. It
        is kept separate from cmMakefile::Targets for that reason.
      * A target may have multiple aliases.
      * An ALIAS target may not itself have an alias.
      * An IMPORTED target may not have an alias.
      * An ALIAS may not be exported or imported.
  14. 26 Jul, 2013 1 commit
  15. 24 Jul, 2013 2 commits
  16. 16 Jul, 2013 1 commit
  17. 11 Jul, 2013 1 commit
  18. 07 Jul, 2013 2 commits
  19. 28 Jun, 2013 1 commit
  20. 24 Jun, 2013 3 commits
  21. 12 Jun, 2013 1 commit
  22. 11 Jun, 2013 1 commit
  23. 10 Jun, 2013 1 commit
  24. 05 Jun, 2013 1 commit
    • Stephen Kelly's avatar
      Genex: Fix the HEAD target used for evaluated expressions · 5b222354
      Stephen Kelly authored and Brad King's avatar Brad King committed
      If the expression $<TARGET_PROPERTY:prop> appears in the content
      of a target property, the target that prop is read from is
      the 'head target' of the expression. In contexts such as evaluating
      the content of a target property during generation, such
      as INCLUDE_DIRECTORIES, the 'head target' is the one on which the
      initial request was made.
      If evaluating a generator expression which is not a target property
      content, the target must be explicitly specified. Such contexts
      include add_custom_command and file(GENERATE). The content might
      then look like
      However, as there is no HeadTarget set, any generator expressions
      evaluated as part of reading prop from tgt which do not specify
      the tgt directly report an error.
      Modify the logic of the TARGET_PROPERTY generator expression so
      that in such contexts, the 'head target' is set to the appropriate
      target which was first encountered.
  25. 02 Jun, 2013 2 commits
  26. 30 May, 2013 3 commits
    • Stephen Kelly's avatar
      GenexEval: Fix evaluation of INCLUDE_DIRECTORIES target property. · 3aa9ce44
      Stephen Kelly authored
      This property should come from the content of the property itself,
      plus the INTERFACE_INCLUDE_DIRECTORIES of the link *implementation*.
      In contrast, when the INTERFACE_INCLUDE_DIRECTORIES is evaluated for
      a target, the INTERFACE_INCLUDE_DIRECTORIES of the link *interface*
      is used.
      Similar logic applies for the COMPILE_DEFINITIONS target properties.
      If the propertyName is already an INTERFACE_ variant of the property,
      ie, the expression is similar to
      then the INTERFACE_INCLUDE_DIRECTORIES of the link *interface* of foo
      is used.
      However, if the propertyName is not an INTERFACE_ variant, and the
      interfacePropertyName is, ie, the expression is similar to:
      then the INTERFACE_INCLUDE_DIRECTORIES of the link *implementation*
      of foo is used.
    • Stephen Kelly's avatar
      GenexEval: Extract a getLinkedTargetsContent from TargetPropertyNode. · 0b39fefe
      Stephen Kelly authored
      This will be used to process transitive components of properties
      which depend on linked targets. Currently only the link interface
      of the target can be used as the source of the linked targets, but
      in the next commit it will be possible to use the link implementation
      as the source of link targets.
      This commit does not change the semantics of the code.
    • Stephen Kelly's avatar
  27. 24 May, 2013 1 commit
  28. 17 May, 2013 1 commit
  29. 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.