1. 15 Apr, 2015 1 commit
  2. 10 Apr, 2015 1 commit
  3. 09 Apr, 2015 2 commits
    • James Bigler's avatar
      FindCUDA: Add specific cuda_language_flag instead of using nvcc. · 1b0c77a3
      James Bigler authored
      I was previously appending to nvcc_flags inside the file loop.  This
      caused the flag to be appended multiple times which freaks out nvcc.
      Now the flag is specifically handled per file.
    • James Bigler's avatar
      FindCUDA: Allow setting CUDA_SOURCE_PROPERTY_FORMAT for non-.cu files. · 8313de2d
      James Bigler authored
      A previously undocumented feature allowed overriding the format
      specified to CUDA_WRAP_SRCS with a source file property called
      CUDA_SOURCE_PROPERTY_FORMAT.  I added documentation for this feature as
      well as added the ability to let nvcc compile any file regardless of
      type if this property was found.
      In addition, I also fixed a couple of bugs with the calls to
      _cuda_get_important_host_flags that weren't garding the arguments with
      "" to prevent empty values from causing errors.
  4. 08 Apr, 2015 1 commit
    • James Bigler's avatar
      FindCUDA: Handle c++11 host flag · 99abebde
      James Bigler authored
      If the host flags contain a c++11 flag (at least for gcc), then we can't
      automatically propagate to nvcc it using -Xcompiler.  This is because
      nvcc can't use any C++ only flags.  Instead we find this flag and add it
      to nvcc's flags (it has a special flag for dealing with c++11 code) and
      remove it from the host flags.
      Co-Author: Guillermo Marcus <gmarcus@nvidia.com>
  5. 07 Apr, 2015 1 commit
  6. 06 Apr, 2015 1 commit
    • Brad King's avatar
      Features: VS 2013 Update 3 supports initializer lists (#15494) · ecb1d5b4
      Brad King authored
      VS 2013 originally claimed to support initializer lists but a bug was
      found in which it generated bad code silently.  For this reason we
      previously considered support to not be present.  However, Update 3 adds
      a hard error on cases that previously generated bad code, so it is now
      safe to use initializer lists with VS 2013 Update 3 or greater.  At
      worst a compiler error will be issued in the cases that do not work, but
      that is no different from any other compiler-specific workaround a
      project code may need.
  7. 04 Apr, 2015 1 commit
  8. 03 Apr, 2015 1 commit
    • James Bigler's avatar
      FindCUDA: Use the static CUDA runtime library if available (#15482) · 7fea2b77
      James Bigler authored
      Beginning in CUDA 5.5 a static version of the cuda runtime library
      became available.  Since nvcc defaults to using this library over the
      shared version, FindCUDA will also default to using this version.  There
      are many advantages to using the static version (most importantly to
      avoid conflicts with multiple versions when building a CUDA based
      library).  Offer a CUDA_USE_STATIC_CUDA_RUNTIME option to control
      this behavior.
  9. 31 Mar, 2015 1 commit
    • Domen Vrankar's avatar
      CPackRPM: Add basic symlink support (#15209) · 681f3a2f
      Domen Vrankar authored
      RPM packages can contain symbolic links to relative paths - including
      support for multiple relocation paths through generation of post install
      relocation scripts.  Add basic support with limitations described in
  10. 30 Mar, 2015 1 commit
    • Felix Schwitzer's avatar
      UseSWIG: Do not use MAIN_DEPENDENCY on custom commands (#15480) · b372a99a
      Felix Schwitzer authored
      Add the dependency on the main swig input source file as a normal
      DEPENDS option.  We cannot use MAIN_DEPENDENCY because if there are
      multiple target languages then multiple custom commands would want to
      use the same MAIN_DEPENDENCY, but at most one custom command may specify
      a given source file as its MAIN_DEPENDENCY.  Exposed by a CMP0057
  11. 27 Mar, 2015 3 commits
  12. 26 Mar, 2015 3 commits
  13. 24 Mar, 2015 1 commit
    • Gregor Jasny's avatar
      OS X: Look for Xcode 5 platform-specific Frameworks · 52642b46
      Gregor Jasny authored
      The Xcode 5 platform specific framework locations differ from the Xcode
      6 ones.  Look first for the Xcode 6 ones, then for iOS Xcode 5 ones and
      last for the Xcode 5 OS X ones.
      For reference, the XCTest.framework is located as follows:
      Signed-off-by: Gregor Jasny's avatarGregor Jasny <gjasny@googlemail.com>
  14. 23 Mar, 2015 4 commits
  15. 20 Mar, 2015 4 commits
  16. 19 Mar, 2015 1 commit
    • Todd Gamblin's avatar
      BlueGene/Q Platform files · 13807bcb
      Todd Gamblin authored
      - based on the BlueGene/P platform files.
      - tested by Todd Gamblin (LLNL) and David DeMarle (Kitware)
  17. 18 Mar, 2015 1 commit
  18. 17 Mar, 2015 4 commits
  19. 09 Mar, 2015 2 commits
  20. 06 Mar, 2015 1 commit
  21. 03 Mar, 2015 2 commits
  22. 02 Mar, 2015 1 commit
  23. 28 Feb, 2015 1 commit
  24. 27 Feb, 2015 1 commit