Re: Xcode 7.0?

[Jeremy Huddleston Sequoia]

> On Sep 18, 2015, at 08:15, Dave Horsfall  wrote:
> 
> On Fri, 18 Sep 2015, Ryan Schmidt wrote:
> 
>> No need for you to test anything. As I said before, OS X 10.11 requires 
>> Xcode 7. But this thread was started by someone on OS X 10.10, and I 
>> explained in my previous post why Xcode 7 on OS X 10.10 might be 
>> problematic, in ways that Xcode 7 on OS X 10.11 would not be 
>> problematic.
> 
> So, would I be correct in concluding that Apple just pushed out a public 
> release of Xcode (viz: 7) that may not be compatible with the current 
> public release of OS/X (viz: 10.10)?

No.

The OS X 10.11 SDK is compatible with building OS X applications for OS X 
10.10.  Some people misunderstand how SDKs work.  You can use newer SDKs to 
build for older OS versions (for example, I use the latest OS X SDK to build 
XQuartz for Snow Leopard users still).  Headers are annotated with availability 
such the new symbols are weakly linked.  Take a look at Availability.h for more 
details on how that works.

The OS X 10.11 SDK does remove some long-deprecated header, but there shouldn't 
be any ports that are hit by that.  If there are, then it is a bug in the port 
which also affects users on OS X 10.11.

> I suppose, in a quantum sort of way, that that's taking security to the 
> limits :-)
> 
> Please note that I am *not* knocking the MacPorts bods; they do a great 
> job, in what I know is a difficult and thankless task.
> 
> -- 
> Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will suffer."
> I'll support shark-culling when they have been observed walking on dry land.
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users



smime.p7s
Description: S/MIME cryptographic signature
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Xcode 7.0?

[Ryan Schmidt]

On Sep 18, 2015, at 2:53 AM, Dave Horsfall wrote:

> Looks like my MacBook (10.10.5) just helped itself to Xcode 7.  Should I 
> be worried about any, err, issues?  I recall a note about that...

Because Xcode 7 only contains the OS X 10.11 SDK, you may have problems 
building some ports on OS X 10.10 that expect there to be a corresponding OS X 
10.10 SDK. These could be viewed as bugs in those ports, but I'm worried there 
may be many of them. I'm worried, for instance, about all ports that build 
using cmake.

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Xcode 7.0?

[Richard Cobbe]

On Fri, Sep 18, 2015 at 04:54:37AM -0500, Ryan Schmidt wrote:
>
> On Sep 18, 2015, at 2:53 AM, Dave Horsfall wrote:
>
> > Looks like my MacBook (10.10.5) just helped itself to Xcode 7.  Should I
> > be worried about any, err, issues?  I recall a note about that...
>
> Because Xcode 7 only contains the OS X 10.11 SDK, you may have problems 
> building some ports on OS X 10.10 that expect there to be a corresponding OS 
> X 10.10 SDK. These could be viewed as bugs in those ports, but I'm worried 
> there may be many of them. I'm worried, for instance, about all ports that 
> build using cmake.

This seems to suggest that those of us who are still running 10.10
shouldn't upgrade.  Is that correct?  (Somewhat surprising, since 10.11
won't be released for another couple of weeks.)

Thanks,

Richard
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Xcode 7.0?

[Ryan Schmidt]

On Sep 18, 2015, at 8:32 AM, Ben Greenfield wrote:

> I have been running a migrated macports on 10.11 since wwdc. I haven’t run 
> into a problem with any of my installs.
> 
> If you want me to check a port I can do it. I performing an OS update right 
> now and if that works out I would be happy to try things for people.

No need for you to test anything. As I said before, OS X 10.11 requires Xcode 
7. But this thread was started by someone on OS X 10.10, and I explained in my 
previous post why Xcode 7 on OS X 10.10 might be problematic, in ways that 
Xcode 7 on OS X 10.11 would not be problematic.

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Xcode 7.0?

[Ryan Schmidt]

On Sep 18, 2015, at 7:09 AM, Richard Cobbe wrote:

> On Fri, Sep 18, 2015 at 04:54:37AM -0500, Ryan Schmidt wrote:
>> 
>> On Sep 18, 2015, at 2:53 AM, Dave Horsfall wrote:
>> 
>>> Looks like my MacBook (10.10.5) just helped itself to Xcode 7.  Should I
>>> be worried about any, err, issues?  I recall a note about that...
>> 
>> Because Xcode 7 only contains the OS X 10.11 SDK, you may have problems 
>> building some ports on OS X 10.10 that expect there to be a corresponding OS 
>> X 10.10 SDK. These could be viewed as bugs in those ports, but I'm worried 
>> there may be many of them. I'm worried, for instance, about all ports that 
>> build using cmake.
> 
> This seems to suggest that those of us who are still running 10.10
> shouldn't upgrade.  Is that correct?  (Somewhat surprising, since 10.11
> won't be released for another couple of weeks.)

I have kept my 10.10 machine at Xcode 6.4 for now, and if you can do that too, 
you will probably have fewer problems as a result. But I might upgrade to Xcode 
7 just to see what problems arise and to see if I can fix them. Users of 10.11 
have to use Xcode 7 or later; earlier versions will cause problems there.



___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Xcode 7.0?

[Dave Horsfall]

On Fri, 18 Sep 2015, Ryan Schmidt wrote:

> No need for you to test anything. As I said before, OS X 10.11 requires 
> Xcode 7. But this thread was started by someone on OS X 10.10, and I 
> explained in my previous post why Xcode 7 on OS X 10.10 might be 
> problematic, in ways that Xcode 7 on OS X 10.11 would not be 
> problematic.

So, would I be correct in concluding that Apple just pushed out a public 
release of Xcode (viz: 7) that may not be compatible with the current 
public release of OS/X (viz: 10.10)?

I suppose, in a quantum sort of way, that that's taking security to the 
limits :-)

Please note that I am *not* knocking the MacPorts bods; they do a great 
job, in what I know is a difficult and thankless task.

-- 
Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will suffer."
 I'll support shark-culling when they have been observed walking on dry land.
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users