1. 10 Dec, 2015 1 commit
  2. 24 Oct, 2015 2 commits
  3. 19 Oct, 2015 3 commits
  4. 18 Oct, 2015 1 commit
  5. 14 Oct, 2015 2 commits
  6. 12 Oct, 2015 3 commits
  7. 08 Oct, 2015 2 commits
  8. 05 Aug, 2015 6 commits
  9. 30 Jul, 2015 3 commits
  10. 07 Jun, 2015 1 commit
  11. 03 May, 2015 1 commit
  12. 20 Apr, 2015 1 commit
  13. 11 Feb, 2015 3 commits
    • Brad King's avatar
      install: Allow generator expressions in TARGETS DESTINATION (#14317) · f30022eb
      Brad King authored
      This will allow per-config destinations for targets in EXPORT sets.
      Using multiple install(TARGETS) with separate CONFIGURATIONS is
      rejected as a target appearing more than once in an export set.
      Now instead one can write
       install(TARGETS foo EXPORT exp DESTINATION lib/$<CONFIG>)
      to get a single logical membership of the target in the export set
      while still having a per-config destination.
    • Brad King's avatar
      cmInstallGenerator: Pass destination explicitly to AddInstallRule · 7607c3d1
      Brad King authored
      This will allow specific invocations to transform the destination
      before AddInstallRule uses it.
    • Brad King's avatar
      cmInstallGenerator: Refactor computation of absolute install dest · 290ca8e2
      Brad King authored
      Replace the GetInstallDestination method, which looked up the
      Destination ivar, with a new ConvertToAbsoluteDestination method that
      takes the nominal destination as an argument.  Update call sites
      accordingly.  This will allow some clients to transform the install
      destination before calling the method.
  14. 18 Jan, 2015 1 commit
  15. 11 Jan, 2015 1 commit
  16. 12 Dec, 2014 1 commit
  17. 10 Oct, 2014 1 commit
    • Clinton Stimpson's avatar
      OSX: Warn when attempting to change runtime paths on OS X 10.5 · 50e261dd
      Clinton Stimpson authored
      Even though 10.5 supports @rpath, the support is not complete
      enough for CMake.  For instance, install_name_tool doesn't support
      adding and removing rpaths.
      Also modifying BundleUtilities test to remove an undesirable cmake
      generated runtime path.  The intent was to build with the install
      rpath as is done with the other cases in this test.
  18. 10 Jul, 2014 1 commit
  19. 24 Jun, 2014 1 commit
    • Brad King's avatar
      install: Thread message level setting through internal API · ec7cf7ea
      Brad King authored
      Create a cmInstallGenerator::MessageLevel enumeration for future use in
      specifying install message verbosity.  Thread values of the type through
      constructors and save the value as a member of cmInstallGenerator.
      Use only a "MessageDefault" value for now.
  20. 08 Mar, 2014 2 commits
    • Ben Boeckel's avatar
    • Ben Boeckel's avatar
      strings: Remove cmStdString references · 270eb96d
      Ben Boeckel authored
      Casts from std::string -> cmStdString were high on the list of things
      taking up time. Avoid such implicit casts across function calls by just
      using std::string everywhere.
      The comment that the symbol name is too long is no longer relevant since
      modern debuggers alias the templates anyways and the size is a
      non-issue since the underlying methods are generated since it's
  21. 03 Feb, 2014 1 commit
    • Clinton Stimpson's avatar
      OS X: Make sure RPATHs are unique to avoid possible corruption. · 028a5285
      Clinton Stimpson authored
      When using link_directories() and including CMAKE_CFG_INTDIR,
      one can end up with duplicate RPATHs in the binary which
      install_name_tool cannot fix without corrupting the binary.
      Also, the cmake_install.cmake file has been fixed to correctly
      handle these generator specific variables.
  22. 11 Dec, 2013 1 commit
  23. 07 Oct, 2013 1 commit
    • Stephen Kelly's avatar
      Add the INTERFACE_LIBRARY target type. · fe732264
      Stephen Kelly authored
      This target type only contains INTERFACE_* properties, so it can be
      used as a structural node. The target-specific commands enforce
      that they may only be used with the INTERFACE keyword when used
      with INTERFACE_LIBRARY targets. The old-style target properties
      matching LINK_INTERFACE_LIBRARIES_<CONFIG> are always ignored for
      this target type.
      The name of the INTERFACE_LIBRARY must match a validity generator
      expression. The validity is similar to that of an ALIAS target,
      but with the additional restriction that it may not contain
      double colons. Double colons will carry the meaning of IMPORTED
      or ALIAS targets in CMake 2.8.13.
      An ALIAS target may be created for an INTERFACE library.
      At this point it can not be exported and does not appear in the
      buildsystem and project files are not created for them. That may
      be added as a feature in a later commit.
      The generators need some changes to handle the INTERFACE_LIBRARY
      targets returned by cmComputeLinkInterface::GetItems. The Ninja
      generator does not use that API, so it doesn't require changes
      related to that.