1. 09 Jun, 2014 3 commits
  2. 05 Jun, 2014 2 commits
  3. 03 Jun, 2014 6 commits
  4. 02 Jun, 2014 3 commits
  5. 27 May, 2014 5 commits
  6. 22 May, 2014 1 commit
  7. 20 May, 2014 3 commits
  8. 19 May, 2014 4 commits
    • Brad King's avatar
    • Brad King's avatar
    • James Bigler's avatar
      FindCUDA: Use CUDA_NVCC_FLAGS* for separable compilation · 6ad14c71
      James Bigler authored and Brad King's avatar Brad King committed
      Previously when linking the intermediate link file for separable compilation
      the CUDA_NVCC_FLAGS* were not used.  This caused tremendous confusion when
      using this feature, and I consider it to be a bug.  This change should fix
    • Brad King's avatar
      CMP0022: Fix link language propagation in NEW behavior · 40b9cd0f
      Brad King authored
      The languages used in compiling STATIC libraries need to be propagated
      to dependents regardless of the settings of INTERFACE_LINK_LIBRARIES or
      CMP0022.  They are independent of the libraries in the link interface.
      Prior to commit v2.8.12~192^2~2 (Introduce the INTERFACE_LINK_LIBRARIES
      property, 2013-06-04) the cmTarget::ComputeLinkInterface code path for
      "explicitLibraries" could never be taken for STATIC libraries, so the
      logic to propagate languages existed only in the non-explicitLibraries
      code path.  After that commit, INTERFACE_LINK_LIBRARIES could be set for
      STATIC libraries to cause the "explicitLibraries" code path to be taken.
      The commit also left the old non-explicitLibraries code path conditional
      on CMP0022 not being set to NEW.  Thus link language propagation was
      left missing from two cases by that commit.
      The explicitLibraries code path was fixed to propagate languages by
      commit v2.8.12~149^2~1 (cmTarget: Fix iface libraries and languages for
      static libraries, 2013-07-26).  However, the non-explicitLibraries case
      was never taught to propagate languages when CMP0022 is set to NEW.  Fix
      that now.  Factor the logic to propagate link languages out of the link
      interface libraries conditions so that it always occurs.  Update
      Tests/Fortran to set CMP0022 to NEW to test this case (because the test
      passes only if link language propagation works).
  9. 13 May, 2014 3 commits
  10. 09 May, 2014 5 commits
    • Brad King's avatar
      Merge branch 'ninja-intel-linux' into release · 9996b984
      Brad King authored
    • Brad King's avatar
      Ninja: Fix deptype for Intel compiler on Linux · 54535f47
      Brad King authored
      Since commit v3.0.0-rc1~305^2 (Ninja: deptype msvc for Intel's compiler
      on Windows, 2013-11-25) we used "deps = msvc" for the Intel compiler.
      This is correct only on Windows.  On Linux we still want "deps = gcc".
      Fix the logic to use "deps = msvc" when the compiler id or the "simulate
      id" is "MSVC".  This will preserve the behavior on Intel for Windows and
      fix the behavior on Intel for Linux.  In the future this should be
      converted to a platform information module variable.
    • Brad King's avatar
    • Brad King's avatar
      cmTarget: Evaluate CMP0026 in calling context · 23409f50
      Brad King authored
      This policy should be checked at the call site that tries to access the
      LOCATION property, not the directory scope containing the target.
      Thread the caller context through cmTarget::GetProperty to use for
      checking the policy setting and emitting a diagnostic with proper
      Extend the RunCMake.CMP0026 test with a cross-directory case.
    • Brad King's avatar
      cmTarget: Drop unused GetProperty signature · 2e75bf67
      Brad King authored
      No callers use the second "scope" argument.  Drop this signature and
      hard-code the default parameter value internally.
  11. 07 May, 2014 5 commits