On Wed, Sep 21, 2016 at 3:15 PM, Adam Dershowitz <de...@alum.mit.edu> wrote:
> That comment does not make it at all clear what those of us who updated to
> Xcode 8 (but not beta!) but are still on OS X 10.11 are supposed to do.
> I have posted a ticket about building cmake that seems to be because it is
> trying to use 10.12 SDK, but it is not clear how to work around that.
> Perhaps the answer is to downgrade to Xcode 7, and stay away from 8? (It is
> a big download!)
> Or, it might be that just the 10.11 command line tools is enough?
If you install Xcode 8 on 10.11, you need to make sure that
'xcode-select -p' reports /Applications/Xcode.app/Contents/Developer
so that you are actually using the Xcode 8 compilers. The Command Line
Tools installed by Software Update or 'xcode-select --install' on
10.11 will be those from Xcode 7.3.1 and will provide the 10.11 SDK
installed in /.
>> On Sep 21, 2016, at 2:44 PM, Lawrence Velázquez <lar...@macports.org> wrote:
>> Jack Howarth has noted on IRC that that Apple will not be releasing
>> a Command Line Tools package for Xcode 8 on El Capitan [*].
>> There is no Command Line Tools (OS X 10.11) for Xcode
>> 8 package. Xcode 8 contains SDKs that are incompatible
>> with earlier toolchains. Developers who want to make use
>> of the Xcode 8 SDKs from the command line must choose
>> the SDK with xcode-select. Developers on OS X El Capitan
>> who have installed versions of the Command Line Tools
>> (OS X 10.11) for Xcode 8 Beta should install Command
>> Line Tools (OS X 10.11) for Xcode 7.3.1. (28234439)
>> Do we need to adjust our installation instructions to account for this?
>> The consequences of mixing the Xcode 7 CLT with Xcode 8 are not clear to
>> me; maybe it's not a problem at all.
>> macports-dev mailing list
> macports-dev mailing list
macports-dev mailing list