Xcode 3.2.6 and Mountain Lion

问题:

I use Xcode 3.2.6 sometimes instead of Xcode 4 because I find some advantages doing that. I had an old installation of Xcode 3.2.6 on Snow Leopard and updated to Lion and Xcode works as before. No problems at all. Now I intend to update to Mountain Lion. Now I have read about people having problems with Xcode 3.2.6 on Mountain Lion, especially Interface Builder. Does anybody here have experiences? May I continue running Xcode 3.2.6 on Mountain Lion?

回答1:

Lars: Haven't done extensive testing yet but after upgrading to 10.8 Xcode 3.2.6 itself runs and seems to build just fine, including a PowerPC target. Interface Builder just bounces in the Dock when I try to launch it. This thread on the dev forums Can XCode 3.2.6 & Interface Builder be made to run... implies it could be issues with Xcode 3's iOS platform plugins.

Macmade: If you must support OS X 10.5 and below and PowerPC, which I have to, then Xcode 4 alone isn't an option. Keeping a copy of Xcode 3 around has been an ideal solution for those projects, especially as it will generally happily live in it's own folder hierarchy.

Believe me I'd love to avoid the hassles of supporting old OS versions but in the end what the client wants is what matters.

回答2:

Xcode 3.2.6 seems to run just fine on Mountain Lion, though I haven't played with it extensively yet. And once I deleted the two iOS related .platforms folders in /Developer/Platforms (leaving only MacOSX.platform) Interface Builder works for me (and without the issues in the devforum thread).

I say its worth it to try and find out. I too need to support users that are using 10.6 support (I've only just dropped 10.4 support, and the next release will be dropping 10.5 support). I would have been up on Xcode 4 if they didn't drop 10.5 support when it first came out, and I would be on Xcode 4.3 if it worked until ML or Xcode 4.4 if it supported 10.6. But Apple made different decisions.

I hope this helps.

回答3:

Xcode 3.2.6 seems to work, but I noticed some issues, like inability for apps compiled with it to access Keychains.

The most safe solution is to run Snow Leopard under Virtual Box. It's a bit slow to install, but it's manageable.

回答4:

I've been using Xcode 3 on Mountain Lion for two months now without problems. Even the custom IBPlugin that the old project uses still loads and works.

The most essential thing to do is NOT to install iOS SDK, as its plugins break Interface Builder.

I've summarized all known issues into installation instructions:

• How to install Xcode 3 on Mountain Lion

回答5:

Metrowerks CodeWarrior was a nice IDE, back in the classic OS days...

Seriously, you should move to Xcode 4.

Of course, you are used to Xcode 3.x, and moving to a recent version may take you some time, may change some of your habits. But it's just the way it works.

Maybe you can use Xcode 3 on Mountain Lion. But just why?

Compiler versions are just old, you won't have access to the latest frameworks, SDKs, language features... Should I say more?

I don't think that developing an app on a modern system with a legacy IDE/compiler suite, just because you prefer it, is a nice way of developing stuff...

So just invest some time learning Xcode 4... It will definitively save you a lot of time developing/debugging...