Re: [Bf-committers] Buildbot cuda-hack

I have no idea. I hard-coded libiomp5 because that’s the one included in darwin libs and the default used by the also included clang-omp-3.5. Official clang 3.7 uses libgomp as default and 3.8 uses libomp. iomp5 is hard-coded on several places, it’s just not hard-coded on the lines I had to

Re: [Bf-committers] Buildbot cuda-hack

Hi, Is it possible to somehow automatically detect which OpenMP library to use without need to hard-code it per-compiler-version? Maybe using try_compile CMake trickery? On Sun, Aug 28, 2016 at 8:37 PM, Francesc Juhe wrote: > I run a few tests regarding clang and omp after

Re: [Bf-committers] Buildbot cuda-hack

I run a few tests regarding clang and omp after installing OSX 10.11 and Xcode 7.3.1. It seems that clang-omp-3.5 from libs can’t compile using OSX 10.11 SDK. So, I downloaded clang 3.7.0 and 3.8.0 darwin binaries from official page and both compile blender ok after a minor modification on

Re: [Bf-committers] Buildbot cuda-hack

But the cuda-hack commit was for CUDA 7.5 initially, I just ask about it now because I am creating a new build environment with el capitan and wanted to know more of what this “hack” did to better understand the build process and be prepared if I had the same issue. About the openmp, I have

Re: [Bf-committers] Buildbot cuda-hack

I'd say cuda8 is pointless for you right now, cause pascal gpu is not yet supported by the NV/OSX (Quadro-) drivers. You would definitely loose openmp capability unless you compile and use a vanilla clang 3.7 which supports it. Jens Am 26.08.2016 um 18:11 schrieb Francesc Juhe: > Hi, > >

[Bf-committers] Buildbot cuda-hack

Hi, Some time ago noticed this commit https://developer.blender.org/rB3a24e6320f31a790ea9d3c912a35db2186140b71 changing the nvcc compiler on builbot but I did not give it much though as I was having no issues compiling with cuda 7.5 and clang 3.5 from libs folder on OSX 10.9. But now with