Just to clarify the CUDA and CMake situation. CMake 3.8 added the initial first class support of CUDA to CMake ( instead of using FindCUDA ). This work only supports the makefile and ninja generators, which means that the visual studio IDE generator is not supported. This doesn't mean that the Visual Studio compiler isn't supported, as you still could use ninja or makefile with the VS compiler.
CMake 3.9 added the support for the visual studio generator for CUDA. The approach that was used was to call out to the existing MSBuild CUDA extensions that NVIDIA provides. With 3.9 all generators are considered to be 'first class' in regards to CUDA. On Thu, Jul 27, 2017 at 9:28 PM, J. Caleb Wherry <calebwhe...@gmail.com> wrote: > Not sure I understand your question but Visual Studio support just lagged a > version for that feature. It is available in CMake 3.9: > > https://cmake.org/cmake/help/v3.9/release/3.9.html > > Or are you asking before this version how was CUDA supported? > > -Caleb > > On Thu, Jul 27, 2017 at 9:07 PM Brian Davis <bitmi...@gmail.com> wrote: >> >> >> Can someone explain to me the meaning of the statement at: >> >> https://cmake.org/cmake/help/latest/release/3.8.html?highlight=cuda >> >> >> Make learned to support CUDA as a first-class language that can be enabled >> via the project() and enable_language() commands. >> CUDA is currently supported by the Makefile Generators and the Ninja >> generator on Linux, macOS, and Windows. *Support for the Visual Studio IDE >> is under development but not included in this release.* >> The NVIDIA CUDA Toolkit compiler (nvcc) is supported. >> >> Specifically: >> >> *Support for the Visual Studio IDE is under development but not included >> in this release.* >> >> Is CUDA as a first class language not supported for seemingly second class >> citizens such as Visual Studio? >> -- >> >> Powered by www.kitware.com >> >> Please keep messages on-topic and check the CMake FAQ at: >> http://www.cmake.org/Wiki/CMake_FAQ >> >> Kitware offers various services to support the CMake community. For more >> information on each offering, please visit: >> >> CMake Support: http://cmake.org/cmake/help/support.html >> CMake Consulting: http://cmake.org/cmake/help/consulting.html >> CMake Training Courses: http://cmake.org/cmake/help/training.html >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Follow this link to subscribe/unsubscribe: >> http://public.kitware.com/mailman/listinfo/cmake > > -- > Sent from my iPhone 4s > > -- > > Powered by www.kitware.com > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Kitware offers various services to support the CMake community. For more > information on each offering, please visit: > > CMake Support: http://cmake.org/cmake/help/support.html > CMake Consulting: http://cmake.org/cmake/help/consulting.html > CMake Training Courses: http://cmake.org/cmake/help/training.html > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/cmake -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
