I believe the closest equivalent to settinga CUDA_TOOLKIT_ROOT_DIR when
using enable_language(CUDA) is to set either the environment variable
CUDACXX or the CMake cache entry CMAKE_CUDA_COMPILER to point to the
location of the nvcc compiler.
However I think there are still some "features" of FindC
"we should not try to combine enable_language(CUDA) with
find_package(CUDA). They do not work together, either use one or another."
Absolutely, my goal is to move to the new built-in language support. I'm
having trouble doing that because I can't find any documentation on it. For
instance, what is
Hi,
That was my confusion as well: to my understanding, we should not try to
combine enable_language(CUDA) with find_package(CUDA). They do not work
together, either use one or another.
Kind regards,
- Dmitry.
пт, 29 мар. 2019 г. в 19:58, Dustyn Blasig :
> Hi All,
>
> I can't find any documenta
Hi All,
I can't find any documentation on the new-ish "native" CUDA support. I need
to know all the variables that we can use, and (for instance) whether
checking the CUDA version is now supported. When searching online, I'm
always directed to the old FindCUDA pages which don't seem to match what
This is an oversight rather than an unsupported feature. Can you
report this as an issue on https://gitlab.kitware.com/cmake/cmake
On Fri, Dec 8, 2017 at 3:56 AM, Hancox, James wrote:
> Hi,
>
>
>
> I’m working on porting an existing FindCUDA project over to using the new
> CMake built-in CUDA sup
Hi,
I'm working on porting an existing FindCUDA project over to using the new CMake
built-in CUDA support, with Visual Studio 15.4.1, CUDA 9.0.176, and CMake
3.10.0. I am currently trying to find a way to disable the -G compilation flag
for NVCC with Debug builds. (Due to the nature of our code
