_VERSION_MINOR 9)
-set(CMake_VERSION_PATCH 20170830)
+set(CMake_VERSION_PATCH 20170831)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/
> Can I link to CUDA libraries with GCC while not using FindCUDA
Yes you can if you have enabled the CUDA language. You will need to
use find_package and can use the CMAKE_CUDA_IMPLICIT_LINK_DIRECTORIES
as the location(s) to search.
> Instead of modifying what FindCUDA does, which would break
On 08/29/2017 05:28 PM, Robert Dailey wrote:
> One other thing: Is there a way to make find_package() default to
> CONFIG mode? Right now it seems to search MODULE first, then CONFIG.
> But right now the only way to enable config is to explicitly use the
> CONFIG option or make sure CMake can't
Hi,
we have encountered this issue as well, in our case when using thrust on the
host side. We currently solve this by still using FindCUDA, even when using
CMake 3.8/3.9, but only using the CUDA_*_LIBRARY and CUDA_TOOLKIT_INCLUDE
variables and nothing else.
Instead of modifying what FindCUDA
