1. 14 Apr, 2014 1 commit
  2. 03 Apr, 2014 1 commit
  3. 02 Apr, 2014 2 commits
    • Stephen Kelly's avatar
      cmTarget: Allow transitive evaluation of SOURCES property. · 3676fb49
      Stephen Kelly authored
      Extend the cmGeneratorExpressionDAGChecker with an interface
      returning the name of the top target.  Use that to determine
      when there is a DAG violation, as required by the RunCMake.Languages
      tests.
      3676fb49
    • Stephen Kelly's avatar
      cmTarget: Make the source files depend on the config. · e6971df6
      Stephen Kelly authored
      Disallow the use of config-specific source files with
      the Visual Studio and Xcode generators. They don't have
      any way to represent the condition currently.
      
      Use the same common-config API in cmQtAutoGenerators. While
      it accepts config-specific files, it doesn't have to support
      multiple configurations yet.
      
      Loop over the configs in cmTargetTraceDependencies
      and cmGlobalGenerator::WriteSummary and consume all source
      files.
      
      Loop over the configs in cmComputeTargetDepends and compute the
      object library dependencies for each config.
      e6971df6
  4. 08 Mar, 2014 1 commit
  5. 06 Mar, 2014 1 commit
    • Brad King's avatar
      Utilities/Release: Fix nightly build upload · 25fb430e
      Brad King authored
      Since commit 71b14dcb (Utilities/Release: Do not upload doc staging
      tarball, 2014-02-26) the prefix upload_release.cmake computes does not
      match any files when used with -DVERSION=master as has been done for the
      nightly binary builds.  Since the version is not actually 'master'
      anyway, change the nightly binary upload logic to explicitly pass the
      destination directory.  Do not pass any VERSION so the default is taken
      and matches the binaries.
      25fb430e
  6. 03 Mar, 2014 9 commits
    • Brad King's avatar
      Tests: Optionally configure tests exclusively, with an external CMake · 9608ef6f
      Brad King authored
      Add an undocumented CMake_TEST_EXTERNAL_CMAKE option to name an external
      CMake 'bin' directory.  Skip all main CMake binary builds and instead
      configure the Tests directory to run using the external CMake provided.
      This will provide a means to exercise the CMake test suite generating
      for target platforms and compilers with which the CMake source does not
      build.  That will allow us to raise the level of C++ features required
      of a compiler to build our source while retaining tests for generating
      projects with older compiler tools.
      9608ef6f
    • Brad King's avatar
      Tests: Drop CMAKE_TEST_GENERATOR(|_TOOLSET) variables · 9f5bd180
      Brad King authored
      s/CMAKE_TEST_GENERATOR/CMAKE_GENERATOR/g
      9f5bd180
    • Brad King's avatar
      Tests: Drop CMAKE_TEST_MAKEPROGRAM variable · 76477267
      Brad King authored
      Remaining uses of the variable simply test its value so use
      CMAKE_MAKE_PROGRAM directly instead.
      76477267
    • Brad King's avatar
      Tests: Rename CMAKE_TEST_MAKEPROGRAM uses for explicit make program · a8a9fb7e
      Brad King authored
      Rename uses of the variable for specifying the make program used to
      build test projects to CMake_TEST_EXPLICIT_MAKE_PROGRAM.
      a8a9fb7e
    • Brad King's avatar
      Tests: Rename CMAKE_TEST_MAKEPROGRAM uses for nested test projects · 40475573
      Brad King authored
      In the ExportImport, Fortran, and MacRuntimePath tests the
      CMAKE_TEST_MAKEPROGRAM variable is used to pass an explicit request for
      a CMAKE_MAKE_PROGRAM value to be used when building the inner projects.
      Rename these use cases to CMake_TEST_NESTED_MAKE_PROGRAM.
      40475573
    • Brad King's avatar
      Tests: Rename CMAKE_TEST_DEVENV -> CMake_TEST_DEVENV · f99734b2
      Brad King authored
      Follow the convention of naming variables related to the CMake build
      itself as "CMake_" rather than "CMAKE_".  While at it, consolidate the
      code computing CMake_TEST_DEVENV to be more localized.
      f99734b2
    • Brad King's avatar
      Tests: Drop CMAKE_TEST_MSVC and test MSVC directly · 3c01ee5a
      Brad King authored
      Now that we no longer support running tests using a different generator
      we can trust the MSVC platform indicator directly.
      3c01ee5a
    • Brad King's avatar
      Tests: Drop CMAKE_TEST_GENERATOR and CMAKE_TEST_MAKEPROGRAM options · daf0a5fe
      Brad King authored
      Drop the option to test with a different generator and make program than
      was used to build.  This was used only to test support for the Open
      Watcom compiler which at one time could not build CMake.  Instead we
      will allow CMake to be configured to skip building binaries and just run
      the test suite using an external CMake (in a future change).
      
      For now leave the two option variables hard-coded to the old option
      defaults until code can be updated to stop using them.
      daf0a5fe
    • Brad King's avatar
      Tests: Drop kwsys test · e5096312
      Brad King authored
      KWSys now has its own dashboard and test clients that run on all the
      machines where we test CMake.  We no longer need a test inside CMake to
      test KWSys independently.
      e5096312
  7. 26 Feb, 2014 1 commit
  8. 09 Feb, 2014 1 commit
  9. 01 Feb, 2014 1 commit
  10. 29 Jan, 2014 1 commit
  11. 14 Jan, 2014 1 commit
  12. 08 Jan, 2014 1 commit
  13. 04 Jan, 2014 1 commit
  14. 23 Dec, 2013 1 commit
  15. 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
  16. 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
  17. 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
  18. 18 Nov, 2013 14 commits