Updates will be applied on October 27th between 12pm - 12:45pm EDT (UTC-0400). Gitlab may be slow during the maintenance window.

  1. 11 Oct, 2013 1 commit
  2. 13 Sep, 2013 1 commit
    • Brad King's avatar
      FindCUDA: Always list custom command outputs in their targets · ef27fa67
      Brad King authored
      CMake's intended interface for linking to explicit object files (marked
      with EXTERNAL_OBJECT) is that only those listed as target sources should
      be linked.  Drop FindCUDA's attempt to hide the .obj files from VS IDE
      project files, which depends on VS-version-specific behavior of linking
      custom command outputs that happen to be named "*.obj".  CMake puts
      external object files in a dedicated source group anyway.
      ef27fa67
  3. 22 Jul, 2013 1 commit
  4. 18 Apr, 2013 2 commits
  5. 14 Mar, 2013 1 commit
  6. 12 Mar, 2013 3 commits
    • James Bigler's avatar
      FindCUDA: Added cupti library. · c939b494
      James Bigler authored
      In addition to adding the cupti library, find_local_library_first has
      been renamed to cuda_find_local_library_first with a backward
      compatibility macro to find_local_library_first.  Also added
      cuda_find_local_library_first_with_path_ext to handle different paths.
      c939b494
    • James Bigler's avatar
      FindCUDA: Add support for separable compilation · 6a19150b
      James Bigler authored
      This adds a new variable, CUDA_SEPARABLE_COMPILATION, and two new
      functions, CUDA_COMPUTE_SEPARABLE_COMPILATION_OBJECT_FILE_NAME and
      CUDA_LINK_SEPARABLE_COMPILATION_OBJECTS.
      
      When CUDA_SEPARABLE_COMPILATION is specified then CUDA runtime objects
      will be compiled with the separable compilation flag.  These object
      files are collected in a target named variable that can be used in
      CUDA_COMPUTE_SEPARABLE_COMPILATION_OBJECT_FILE_NAME and
      CUDA_LINK_SEPARABLE_COMPILATION_OBJECTS.
      6a19150b
    • James Bigler's avatar
      FindCUDA: Remove linkage against CUDA driver library (#13084) · 3497bc2c
      James Bigler authored
      The CUDA runtime library (libcudart) doesn't depend on the driver API
      library (libcuda) and shouldn't be used to link CUDA run time codes.
      3497bc2c
  7. 20 Aug, 2012 2 commits
    • James Bigler's avatar
      Added CUDA_SOURCE_PROPERTY_FORMAT. Allows setting per file format (OBJ or PTX) · 787287cc
      James Bigler authored
      Added CUDA_SOURCE_PROPERTY_FORMAT that allows users to set the format (OBJ or PTX) on a
      per file basis.
      787287cc
    • James Bigler's avatar
      FindCUDA: Added CUDA_HOST_COMPILER variable. · db207e40
      James Bigler authored
      Added a new CUDA variable for specifying the CUDA_HOST_COMPILER.  This will allow users to
      be able to specify which host compiler to use for invoking NVCC with.  By default it will
      use the compiler used for host compilation.  This is convenient for when you want to
      specify a different compiler than the default compiler.  You end up using the same
      compiler for both the NVCC compilation and the host compilation instead of using the
      default compiler in the path for NVCC.
      db207e40
  8. 14 Aug, 2012 1 commit
    • Rolf Eike Beer's avatar
      use the find_* functions ENV parameter · b04650e1
      Rolf Eike Beer authored
      Instead of directly passing $ENV{SOMEVAR} to a find_* call pass in ENV SOMEVAR.
      This will make sure the paths will get correctly handled through different
      platforms, especially on Windows.
      
      Also fixes one place where paths with windows delimiters (\) were hardcoded to
      use forward slashes.
      b04650e1
  9. 13 Aug, 2012 2 commits
    • Kitware Robot's avatar
      Remove CMake-language block-end command arguments · 9db31162
      Kitware Robot authored
      Ancient versions of CMake required else(), endif(), and similar block
      termination commands to have arguments matching the command starting the
      block.  This is no longer the preferred style.
      
      Run the following shell code:
      
      for c in else endif endforeach endfunction endmacro endwhile; do
          echo 's/\b'"$c"'\(\s*\)(.\+)/'"$c"'\1()/'
      done >convert.sed &&
      git ls-files -z -- bootstrap '*.cmake' '*.cmake.in' '*CMakeLists.txt' |
      egrep -z -v '^(Utilities/cm|Source/kwsys/)' |
      egrep -z -v 'Tests/CMakeTests/While-Endwhile-' |
      xargs -0 sed -i -f convert.sed &&
      rm convert.sed
      9db31162
    • Kitware Robot's avatar
      Convert CMake-language commands to lower case · 77543bde
      Kitware Robot authored
      Ancient CMake versions required upper-case commands.  Later command
      names became case-insensitive.  Now the preferred style is lower-case.
      
      Run the following shell code:
      
      cmake --help-command-list |
      grep -v "cmake version" |
      while read c; do
          echo 's/\b'"$(echo $c | tr '[:lower:]' '[:upper:]')"'\(\s*\)(/'"$c"'\1(/g'
      done >convert.sed &&
      git ls-files -z -- bootstrap '*.cmake' '*.cmake.in' '*CMakeLists.txt' |
      egrep -z -v '^(Utilities/cm|Source/kwsys/)' |
      xargs -0 sed -i -f convert.sed &&
      rm convert.sed
      77543bde
  10. 19 Jun, 2012 2 commits
  11. 18 Feb, 2012 1 commit
  12. 20 Dec, 2011 1 commit
  13. 05 Dec, 2011 5 commits
  14. 20 Jan, 2011 1 commit
    • Brad King's avatar
      Modules: Include builtin FindPackageHandleStandardArgs directly · c4275592
      Brad King authored
      The FindPackageHandleStandardArgs module was originally created outside
      of CMake.  It was added for CMake 2.6.0 by commit e118a627 (add a macro
      FIND_PACKAGE_HANDLE_STANDARD_ARGS..., 2007-07-18).  However, it also
      proliferated into a number of other projects that at the time required
      only CMake 2.4 and thus could not depend on CMake to provide the module.
      CMake's own find modules started using the module in commit b5f656e0
      (use the new FIND_PACKAGE_HANDLE_STANDARD_ARGS in some of the FindXXX
      modules..., 2007-07-18).
      
      Then commit d358cf5c (add 2nd, more powerful mode to
      find_package_handle_standard_args, 2010-07-29) added a new feature to
      the interface of the module that was fully optional and backward
      compatible with all existing users of the module.  Later commit 5f183caa
      (FindZLIB: use the FPHSA version mode, 2010-08-04) and others shortly
      thereafter started using the new interface in CMake's own find modules.
      This change was also backward compatible because it was only an
      implementation detail within each module.
      
      Unforutnately these changes introduced a problem for projects that still
      have an old copy of FindPackageHandleStandardArgs in CMAKE_MODULE_PATH.
      When any such project uses one of CMake's builtin find modules the line
      
        include(FindPackageHandleStandardArgs)
      
      loads the copy from the project which does not have the new interface!
      Then the including find module tries to use the new interface with the
      old module and fails.
      
      Whether this breakage can be considered a backward incompatible change
      in CMake is debatable.  The situation is analagous to copying a standard
      library header from one version of a compiler into a project and then
      observing problems when the next version of the compiler reports errors
      in its other headers that depend on its new version of the original
      header.  Nevertheless it is a change to CMake that causes problems for
      projects that worked with previous versions.
      
      This problem was discovered during the 2.8.3 release candidate cycle.
      It is an instance of a more general problem with projects that provide
      their own versions of CMake modules when other CMake modules depend on
      them.  At the time we resolved this instance of the problem with commit
      b0118402 (Use absolute path to FindPackageHandleStandardArgs.cmake
      everywhere, 2010-09-28) for the 2.8.3 release.
      
      In order to address the more general problem we introduced policy
      CMP0017 in commit db44848f (Prefer files from CMAKE_ROOT when including
      from CMAKE_ROOT, 2010-11-17).  That change was followed by commit
      ce28737c (Remove usage of CMAKE_CURRENT_LIST_DIR now that we have
      CMP0017, 2010-12-20) which reverted the original workaround in favor of
      using the policy.  However, existing project releases do not set the
      policy behavior to NEW and therefore still exhibit the problem.
      
      We introduced in commit a364daf1 (Allow users to specify defaults for
      unset policies, 2011-01-03) an option for users to build existing
      projects by adding -DCMAKE_POLICY_DEFAULT_CMP0017=NEW to the command
      line.  Unfortunately this solution still does not allow such projects to
      build out of the box, and there is no good way to suggest the use of the
      new option.
      
      The only remaining solution to keep existing projects that exhibit this
      problem building is to restore the change originally made in commit
      b0118402 (Use absolute path to FindPackageHandleStandardArgs.cmake
      everywhere, 2010-09-28).  This also avoids policy CMP0017 warnings for
      this particular instance of the problem the policy addresses.
      c4275592
  15. 04 Jan, 2011 1 commit
  16. 04 Oct, 2010 2 commits
    • James Bigler's avatar
      Allow -g3 for CUDA v3.0+. · 6916f8db
      James Bigler authored
      In versions of the CUDA toolkit previous to version 3.0 the use of -g3 would cause
      compilation errors.  This was fixed in version 3.0.
      6916f8db
    • James Bigler's avatar
      Fix for bug 0011263. · 1df8516c
      James Bigler authored
      Added CUSDKCOMPUTE_ROOT to the list of paths when looking for CUDA_SDK_ROOT_DIR.
      1df8516c
  17. 28 Sep, 2010 1 commit
  18. 10 Sep, 2010 1 commit
    • James Bigler's avatar
      Added CUDA 3.2 directory changes. Disable emulation mode for CUDA 3.1+. · 4f0636e9
      James Bigler authored
      CUDA 3.2 on Windows systems changed the layout of the library paths.  This adds the extra
      directories needed to locate the new files.
      
      I also explicitly disable emulation mode for CUDA 3.1+.  This feature was deprecated in
      3.0 and ultimately removed in 3.1.  The script errors out if CUDA_BUILD_EMULATION is
      turned on.  I didn't want to ignore emulation mode (even with a warning - which most
      people may not even see) and have users confused as to why it wasn't working.
      4f0636e9
  19. 07 Aug, 2010 1 commit
  20. 13 Jul, 2010 1 commit
  21. 21 Jun, 2010 1 commit
    • James Bigler's avatar
      Add support for the emulation version of the cudart library. · bb6acb86
      James Bigler authored
      In version 3.0 of the CUDA toolkit when building code for emulation, you need to link
      against a new version of the cuda run time library called cudartemu.  This CL adds a check
      for the new library and uses it when present and in emulation mode.  Note that this
      library is not present in previous or subsequent versions of the CUDA toolkit.
      bb6acb86
  22. 15 Jun, 2010 1 commit
  23. 12 May, 2010 1 commit
    • James Bigler's avatar
      Fixed: CUDA_VERSION_MAJOR/MINOR now computed after first run. · 0d30e3fe
      James Bigler authored
      CUDA_VERSION_MAJOR and CUDA_VERSION_MINOR were only computed when CUDA_VERSION was first
      computed.  Subsequent runs of FindCUDA would not have CUDA_VERSION_MAJOR/MINOR set.  We
      now extract the major and minor versions from the CUDA_VERSION cache variable every run.
      0d30e3fe
  24. 11 Feb, 2010 1 commit
  25. 28 Jan, 2010 3 commits
  26. 08 Jan, 2010 2 commits