Buildbot: fix for missing CUDA compute after recent changes
Issue was caused by how CUDA devices availability done in Cycles. Basically, if there's no WITH_CUDA_BINARIES buildtime, nvcc becomes mandatory dependency. Since kernels are building in separate target now, this logic broke a bit. Perhaps condition in util_cuda shall be changed to be a bit smarter, but for now just work-around by enabling CUDA binaries when building Cycles. Made it empty arch list to be sure no kernels will try to re-compile after cudakernels target is done.
This commit is contained in:
@@ -110,7 +110,8 @@ BF_JACK_LIB_STATIC = '${BF_ZLIB}/lib/libjack.a'
|
||||
|
||||
# Cycles
|
||||
WITH_BF_CYCLES = True
|
||||
WITH_BF_CYCLES_CUDA_BINARIES = False
|
||||
WITH_BF_CYCLES_CUDA_BINARIES = True
|
||||
BF_CYCLES_CUDA_BINARIES_ARCH = []
|
||||
|
||||
WITH_BF_OIIO = True
|
||||
WITH_BF_STATICOIIO = True
|
||||
|
@@ -110,7 +110,8 @@ BF_JACK_LIB_STATIC = '${BF_ZLIB}/lib/libjack.a'
|
||||
|
||||
# Cycles
|
||||
WITH_BF_CYCLES = True
|
||||
WITH_BF_CYCLES_CUDA_BINARIES = False
|
||||
WITH_BF_CYCLES_CUDA_BINARIES = True
|
||||
BF_CYCLES_CUDA_BINARIES_ARCH = []
|
||||
|
||||
WITH_BF_OIIO = True
|
||||
WITH_BF_STATICOIIO = True
|
||||
|
Reference in New Issue
Block a user