Older Xcode on El Capitan?

SHNXX

macrumors 68000
Original poster
Oct 2, 2013
1,817
610
I haven't updated my app to the Swift 2 because I'm afraid the debugging will delay things too much with the current development process.
As such, I'm using Xcode 6.4 right now which uses old version of Swift.

The El Capitan is due to be released soon, and I was wondering if older Xcode versions will still run on the El Capitan.
I read different opinions about it, and some suggested some fixes, but I'm not sure if it has changed for the GM or not.

Any ideas?
 

chown33

Moderator
Staff member
Aug 9, 2009
8,373
4,362
Pumpkindale
Don't change OSes in the middle of an important project.

Don't change IDEs in the middle of an important project.

Don't change anything unless you're fully capable of reverting to what you had before.

In short, don't change anything you can't immediately walk away from.

If you simply must get your hands on El Cap and play with it, then make a separate discardable partition or drive, install it there, and keep it completely separate from the important project. That is, don't edit or compile anything on El Cap, unless it's purely an experiment, and you're willing to discard the whole experiment if it doesn't pan out.
 

grandM

macrumors 65816
Oct 14, 2013
1,100
56
I haven't updated my app to the Swift 2 because I'm afraid the debugging will delay things too much with the current development process.
As such, I'm using Xcode 6.4 right now which uses old version of Swift.

The El Capitan is due to be released soon, and I was wondering if older Xcode versions will still run on the El Capitan.
I read different opinions about it, and some suggested some fixes, but I'm not sure if it has changed for the GM or not.

Any ideas?
Make sure you create a snapshot before import and keep a copy of your old Xcode version around.
 

bjet767

macrumors 6502a
Oct 2, 2010
961
307
Good advice. I recently updated a project (which had grown rather big) to Xcode 7 and finding the minor changes to make it compile/link was a real pain in the you know what. I finally did, but there was zero info from Apple about what needed to be done and the compiler/linker errors were only a little help.
 

developer13245

macrumors 6502a
Nov 15, 2012
534
699
Yup. We started a project a year ago and chose to stay with objective C because we knew Swift was/is a work in progress.
iOS 9 came out in the middle of the project end game, but the transition to iOS 9 and Xcode 7 was minor work. We started testing on 9 betas right after WWDC, and found MAJOR bugs. Luckily, Apple fixed all but one, and we had a workaround ready for the one bug that still is present, even on 9.1. This is how you play in Apple's court.