Hmm, it always seemed to work up until now. Anyway, I’ve never seen any explicit instructions as to how to build 2.8. There are only instructions for master on that page. I’ll try the suggestions I haven’t tried yet.
So… do I do the git checkout blender2.8 right after cloning master? Or do I pull the submodules or make update first? I’m just trying to find the right order of things. Can’t find any instructions on building 2.8, which is why I was guessing. Thx.
I did my setup just like Chuck (or at least just like the wiki instructions with the addition of the -b blender2.8 on the initial checkout), and I get those same messages from make update, but it has never seemed to cause a problem. My OpenSubdiv appears to work (at least I think it’s OpenSubdiv).
The one other issue I had originally was that “make full” did not build CUDA support at least to the degree that my video card did not show up in the CUDA device Preference. Since then I’ve been doing “make release” which has always built everything and I’ve never seen a discrepancy between my build and the nightly builds (doesn’t mean there aren’t any).
The other thing is that the Blender build on my MacBook Pro runs in about 1/10th the time as my Windows build. Some of this is probably because I don’t even try to build the CUDA stuff on my Mac at the moment. I’m actually trying to port some of this stuff to Metal (one of my many goals). If nothing else, I’ve found some brilliant GPU code inside of Blender/Cycles.
So I got make full working properly on Windows. However, it still doesn’t see my 2 Nvidia GPUs. I do see that it is picking up CUDA 10.0 even though I have CUDA 9.1 on the machine as well. I suppose I’ll have to change something about my Path to build Blender. But I don’t want to break my Vulkan and CUDA 10.0 code. So I’ll have to figure out how to wrap up the Blender build. Was hoping to spend as little time as possible fighting with Windows. And make release works as well on Windows.
And make release results in my GPUs being found even though it warned me that it was using CUDA 10.0.
My windows make release only takes a couple minutes unless it decides it needs to rebuild all the CUDA kernels, in which case that takes an additional 20 minutes or so. Normally it’s a very reasonable build time.
And Windows builds were broken last night and this morning due to an internal compiler error caused by a change yesterday, so you might have gotten caught up in that as well.