1. 17 Feb, 2016 6 commits
  2. 12 Feb, 2016 4 commits
  3. 11 Feb, 2016 2 commits
  4. 10 Feb, 2016 1 commit
  5. 09 Feb, 2016 4 commits
  6. 08 Feb, 2016 14 commits
  7. 05 Feb, 2016 4 commits
    • Brad King's avatar
      ExternalProject: Be compatible with projects setting CMAKE_CFG_INTDIR · 1b9d15c1
      Brad King authored
      Since commit v3.5.0-rc1~32^2~1 (ExternalProject: Simplify `cmake
      --build` configuration passing, 2016-01-19) we use the `$<CONFIG>`
      generator expression to generate the `cmake --build . --config <config>`
      value for the default BUILD_COMMAND instead of the CMAKE_CFG_INTDIR
      placeholder value provided by multi-config generators.  However, some
      projects have been abusing the old implementation detail by setting
      CMAKE_CFG_INTDIR themselves to get a specific configuration.  Those
      projects should be updated to set their own BUILD_COMMAND to get
      non-default behavior.  Meanwhile we can be compatible with their
      existing releases by detecting when CMAKE_CFG_INTDIR is not a
      generator-provided placeholder and using its value instead.
      1b9d15c1
    • Brad King's avatar
      install(EXPORT): Fix crash on target in another directory · 47460f3e
      Brad King authored
      Refactoring merged by commit v3.5.0-rc1~299 (Merge topic
      'use-generator-target', 2015-10-20) in and around
      commit v3.5.0-rc1~299^2~13 (cmExportSet: Store a cmGeneratorTarget,
      2015-10-17) changed export sets to delay looking up actual targets and
      stores only their names.  However, in InstallCommand::HandleExportMode
      we need to lookup targets immediately to check them for
      EXPORT_LINK_INTERFACE_LIBRARIES.  The check was accidentally made local
      to the current directory, so if an export set contains a target from
      another directory the lookup fails and CMake crashes.  Fix the check to
      look up the target name globally, and tolerate when no target is found
      just in case.
      Reported-by: Kelly (KT) Thompson's avatarKelly Thompson <kgt@lanl.gov>
      47460f3e
    • Brad King's avatar
      Tests: Use newer policy settings in RunCMake.install test · e86383e1
      Brad King authored
      In particular, avoid CMP0042 warnings on OS X.
      e86383e1
    • Brad King's avatar
      Fix dependency scanning configuration in subdirectories · c5eb21b6
      Brad King authored
      Refactoring in commit v3.5.0-rc1~347^2~2 (Set the current dirs on the
      snapshot before creating the cmMakefile) accidentally changed the
      source and binary directories configured in `cmake -E cmake_depends`
      for use during dependency scanning.  This can cause the wrong directory
      information to be loaded.  It also breaks Fortran module dependency
      scanning for modules provided by targets in subdirectories that do
      not have Fortran_MODULE_DIRECTORY set.
      
      Fix the dependency scanning directory configuration and add a test to
      cover the Fortran module case in which the breakage was observed.
      Reported-by: Kelly (KT) Thompson's avatarKelly Thompson <kgt@lanl.gov>
      c5eb21b6
  8. 02 Feb, 2016 5 commits