alexis.girault at kitware.com
Tue Jan 3 16:23:29 EST 2017
I've been confronted to this kind of XCode/SDK version issues, and even
though I did not dig up much, I found this post which encouraged using the
SDK of the same version that the deployment target, so I went with it and
it worked well for me: http://stackoverflow.com/a/15092753
I listed which SDKs ships with each XCode as well as official download
links in this google doc:
There is also some link to a couple scripts I have been using to fixup my
xcode with the previous SDKs, the latest being XCodeLegacy:
On Tue, Jan 3, 2017 at 3:19 PM, Marcus D. Hanwell <
marcus.hanwell at kitware.com> wrote:
> On Tue, Jan 3, 2017 at 3:00 PM, Sean McBride <sean at rogue-research.com>
> > On Tue, 3 Jan 2017 14:50:50 -0500, Marcus D. Hanwell said:
> >>So that the binaries we ship work with older versions of the OS, or
> >>that is my understanding and why we have continued to do this.
> > Ah, no, that's a common misconception. There is a different setting
> called "deployment target" that decides the oldest version of the OS that
> binaries will run on. It's called "CMAKE_OSX_DEPLOYMENT_TARGET" in cmake.
> So it's perfectly OK to use Xcode 8 with its 10.12 SDK but with deployment
> target set to say 10.9. Then your binary will work on >= 10.9. It's a
> much better choice than hacking your Xcode.
> We should take a look at that then, I was still under the impression
> we needed to hack our XCode. I will leave it in place for now, and see
> what happens.
> Powered by www.kitware.com
> Visit other Kitware open-source projects at http://www.kitware.com/
> Search the list archives at: http://markmail.org/search/?q=vtk-developers
> Follow this link to subscribe/unsubscribe:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the vtk-developers