1. 07 May, 2014 1 commit
  2. 09 Feb, 2014 1 commit
  3. 01 Feb, 2014 1 commit
  4. 29 Jan, 2014 1 commit
  5. 14 Jan, 2014 1 commit
  6. 08 Jan, 2014 1 commit
  7. 04 Jan, 2014 1 commit
  8. 23 Dec, 2013 1 commit
  9. 10 Dec, 2013 1 commit
    • Stephen Kelly's avatar
      Remove INTERFACE build targets. · 97fae68b
      Stephen Kelly authored
      Commit b04f3b9a (Create make rules for INTERFACE_LIBRARY
      targets., 2013-08-21) extended the makefile generator to create
      build targets for INTERFACE_LIBRARY targets. No other generators
      were extended with this feature.
      
      This conflicts with the feature of whitelisting of target properties
      read from INTERFACE_LIBRARY targets. The INTERFACE_* properties
      of the INTERFACE_LIBRARY may legitimately contain TARGET_PROPERTY
      generator expressions for reading properties from the 'head target'.
      The 'head target' would be the INTERFACE_LIBRARY itself when creating
      the build rules for it, which means that non-whitelisted properties
      would be read.
      97fae68b
  10. 27 Nov, 2013 1 commit
    • Stephen Kelly's avatar
      QtAutoUic: Add INTERFACE_AUTOUIC_OPTIONS target property. · 98093c45
      Stephen Kelly authored
      Transitively consume the property from linked dependents.
      
      Implement configuration-specific support by following the pattern
      set out for compile definitions and includes in cmQtAutoGenerators.
      
      Implement support for origin-tracking with CMAKE_DEBUG_TARGET_PROPERTIES.
      
      This is motivated by the needs of KDE, which provides a separate
      translation system based on gettext instead of the Qt linguist
      translation system. The Qt uic tool provides command line options
      for configuring the method used to translate text, and to add an
      include directive to the generated file to provide the method.
      
       http://thread.gmane.org/gmane.comp.kde.devel.frameworks/7930/focus=7992
      
      Implement the interface to provide the uic options as a usage-requirement
      on the KI18n target, as designed for KDE.
      98093c45
  11. 21 Nov, 2013 1 commit
    • Stephen Kelly's avatar
      Introduce CMAKE_STAGING_PREFIX variable. · 7521da28
      Stephen Kelly authored
      This variable can be useful in cross-compiling contexts where the
      sysroot is read-only or where the sysroot should otherwise remain
      pristine.
      
      If the new CMAKE_STAGING_PREFIX variable is set, it is used instead
      of CMAKE_INSTALL_PREFIX when generating the installation rules in
      cmake_install.cmake.
      
      This way, the CMAKE_INSTALL_PREFIX variable
      always refers to the installation prefix on the target device, regardless
      of whether host==target.
      
      If any -rpath paths passed to the linker contain the CMAKE_STAGING_PREFIX,
      the matching path fragments are replaced with the CMAKE_INSTALL_PREFIX.
      Matching paths in the -rpath-link are not transformed.
      
      The cross-prefix usr-move workaround is assumed not to require extension
      regarding CMAKE_STAGING_PREFIX. The staging area is a single prefix, so
      there is no scope for cross-prefix symlinks. The CMAKE_INSTALL_PREFIX
      is still used to determine the workaround path, and that variable
      remains the relevant one even if CMAKE_STAGING_PREFIX is used. If the
      generated export files are deployed to the target, the workaround
      will still be in place, and still be employed if required.
      7521da28
  12. 18 Nov, 2013 14 commits
  13. 13 Nov, 2013 1 commit
  14. 12 Nov, 2013 1 commit
    • Brad King's avatar
      Copyright.txt: Add test to check year range · 2bbf6bd7
      Brad King authored
      Add a CMake.Copyright test that, when the CMake version number knows the
      year (as it does in development versions), checks that Copyright.txt has
      been updated with the current version year.
      2bbf6bd7
  15. 01 Nov, 2013 1 commit
  16. 31 Oct, 2013 1 commit
  17. 26 Oct, 2013 1 commit
    • Pedro Navarro's avatar
      ctest_update: Add support for Perforce p4 client · 970c8234
      Pedro Navarro authored and Brad King's avatar Brad King committed
      Teach the ctest_update implementation to use the p4 command-line
      client to perform updates and extract the list of changes.
      
      Add a CTest.UpdateP4 test like those that exist already for the other
      version control tools.  Make the test available when p4 and the p4d
      server are found.  During the test launch p4d in the background to
      serve a repository from the test directory.  Then direct the client
      toward this server for the duration of the test.
      970c8234
  18. 25 Oct, 2013 1 commit
  19. 24 Oct, 2013 2 commits
  20. 21 Oct, 2013 2 commits
    • Nils Gladitz's avatar
      7a665ae7
    • Stephen Kelly's avatar
      Create make rules for INTERFACE_LIBRARY targets. · b04f3b9a
      Stephen Kelly authored and Brad King's avatar Brad King committed
      The result is that the depends of the target are created.
      
      So,
      
       add_library(somelib foo.cpp)
       add_library(anotherlib EXCLUDE_FROM_ALL foo.cpp)
       add_library(extra EXCLUDE_FROM_ALL foo.cpp)
       target_link_libraries(anotherlib extra)
      
       add_library(iface INTERFACE)
       target_link_libraries(iface INTERFACE anotherlib)
      
      Executing 'make iface' will result in the anotherlib and extra targets
      being made.
      
      Adding a regular executable to the INTERFACE of an INTERFACE_LIBRARY
      will not result in the executable being built with 'make iface' because
      of the logic in cmComputeTargetDepends::AddTargetDepend.
      
      So far, this is implemented only for the Makefile generator. Other
      generators will follow if this feature is possible for them.
      
      Make INTERFACE_LIBRARY targets part of the all target by default.
      Test this by building the all target and making the expected library
      EXCLUDE_FROM_ALL.
      b04f3b9a
  21. 18 Oct, 2013 1 commit
  22. 15 Oct, 2013 2 commits
    • Brad King's avatar
      Drop CMAKE_STRICT mode · 277bd1db
      Brad King authored
      With our modern development workflow it is less likely a property will
      be added to C++ code without documentation.  This mode only existed to
      support the DocTest which had very limited coverage of the properties
      anyway.
      277bd1db
    • Stephen Kelly's avatar
      Require CMake 2.8.4 or greater to build CMake · 920ffbf5
      Stephen Kelly authored and Brad King's avatar Brad King committed
      This allows the use of the $<TARGET_FILE:...> generator expression as a
      replacement for the use of the LOCATION target property.  The use of the
      LOCATION target property is now deprecated for in-build targets.
      
      Also drop other checks for older CMake versions:
      
      * Simplify cmake_set_target_folder macro.
      * Use find_package(LibArchive) unconditionally.
      * Simplify condition for running testVisualStudioSlnParser test.
      * Convert two macros to functions.
      * Unconditionally run the CTestTestRerunFailed test.
      920ffbf5
  23. 08 Oct, 2013 2 commits