From 2af7637f207c420af602f43e514b1b20e7cfc718 Mon Sep 17 00:00:00 2001 From: Sergey Sharybin Date: Thu, 14 Jan 2016 12:24:09 +0500 Subject: Cycles: Add option to directly link against CUDA libraries The main purpose of such linking is to make Blender compatible with NVidia's debuggers and profilers which are doing some LD_PRELOAD magic to intercept some function calls. Such magic conflicts with our CUDA wrangler magic and causes segmentation faults. The option is disabled by default, so there's no affect on any of artists. In order to make Blender linked directly against CUDA library use the WITH_CUDA_DYNLOAD CMake option (it's marked as advanced). --- intern/cycles/cmake/external_libs.cmake | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'intern/cycles/cmake') diff --git a/intern/cycles/cmake/external_libs.cmake b/intern/cycles/cmake/external_libs.cmake index 56ab8bed6e8..fc75efa7755 100644 --- a/intern/cycles/cmake/external_libs.cmake +++ b/intern/cycles/cmake/external_libs.cmake @@ -37,7 +37,7 @@ endif() ########################################################################### # CUDA -if(WITH_CYCLES_CUDA_BINARIES) +if(WITH_CYCLES_CUDA_BINARIES OR NOT WITH_CUDA_DUNLOAD) find_package(CUDA) # Try to auto locate CUDA toolkit if(CUDA_FOUND) message(STATUS "CUDA nvcc = ${CUDA_NVCC_EXECUTABLE}") -- cgit v1.2.3