Overnight my computer auto updated to OSX 10.10.5 (from 10.10.4) and to
Xcode 7.0. even though auto updates were turned off.
OSX 10.10.5 and xcode 7.0 introduce a new SDK version of 10.11 which
src/blender/CMakeLists.txt is not aware of.
Fortunately uname -r reports the system as 14.5 now.
This is problematic (not your patch, that its checking for exact OSX
versions in the first place).
This means you can't build older Blender versions on a new system,
which is needed for bisecting.
At least not easily, without manually editing the CMakeLists.txt file each step.
Did anyone look
I think this aggressive updating policy on Apple's part could be a real
problem for us.
uname -r on OS X 10.10.5 does give 14.5
and xcode 7 is released. I do not really get the "The patch moves
requirenment for a new CMake from 14.0 to 14.5" comment though
Martijn
On Mon, Sep 21, 2015 at 11:28
On Mon, Sep 21, 2015 at 6:46 PM, Sergey Sharybin wrote:
> Levon, is the OSX and new XCode officially released or they're still on the
> beta state?
>
> In any case, the patch lacks two things:
>
> - SCons needs support of new XCode as well
> - The patch moves requirenment
Levon, is the OSX and new XCode officially released or they're still on the
beta state?
In any case, the patch lacks two things:
- SCons needs support of new XCode as well
- The patch moves requirenment for a new CMake from 14.0 to 14.5
Campbell, don't think we really looked into making XCode