Apple Updates Xcode, Final Cut Pro

iumacboy writes "Hot on the heels of yesterdays Panther 10.3.2 update and today's QuickTime 6.5 and iTunes 4.2 updates, Apple has released Xcode 1.1, Apple's free suite of developer tools for Mac OS X. 'The Xcode 1.1 Update provides overall stability and performance enhancements to Xcode IDE, as well as improvements to debugging, workflow, the Xcode build system, and CodeSense. It is recommended that all Xcode users install this update.' Available via Software Update." Well, earlier today it was available via Software Update; it has since disappeared. However, if you are a Final Cut Pro user, you can get FCP 4.1.1 and LiveType 1.1.1 while you wait for Xcode 1.1 to return. Also, iTunes 4.2 has now appeared in Software Update, too.

Comments

More information?

[Permission Denied]

It would be really nice if the headline actually linked to Apple's knowlege base article on this update. I can't find it and I can't even get the README file since it's not in Software Update.

What I want to know is how much of the backend stuff they've changed. For instance, if they've upgraded gcc. It doesn't really affect me if the front end breaks, but I have a largish project which I'm right now preparing for release and I need to decide whether to build now or to run the update and go through another testing cycle. My intuition tells me to build now and update later, but I don't know if they've fixed any massive compiler bugs.

Re:More information?

[nether]

Let me state it succinctly: You are a fool.

Why would you risk your release schedule for some possible panacea, which in all likely hood break your build in a nature that is completely unknown?

I would hope that you listen to your intuition and continue with your plan, build in additional testing for the next release.

Re:More information?

[Moses Lawn]

...I have a largish project which I'm right now preparing for release and I need to decide whether to build now or to run the update and go through another testing cycle. My intuition tells me to build now and update later, but I don't know if they've fixed any massive compiler bugs.


No no no NO! You *never* upgrade in the middle of a project, *especially* if you're in the final phases. Unless there is a known bug or limitation that is causing a drop-dead problem, you leave everything exactly as it is, so you have a known, stable build. You don't get new libraies, you don't add that cool new feature, you don't install the latest service pack on the (internal) build machine. You certainly don't upgrade the compiler or IDE.

The alternative is, in the best case, to have to start the testing cycle over from the beginning. In the worst case, the upgrade will break something badly, and in a situation where you cannot roll back to the original state (as I assume an OSX update is, but I may be mistaken), you'll be screwed.

I don't know if this is a personal project or a work-related thing, but if it's for work, first your boss will kick your ass, then QA will hand it back to you, in pieces.

Follow your intuition here. If there were any big compiler bugs, testing would have already found them, right?

Re:Maybe not fine

[mj_1903]

This I am sure is highly unrelated. He did install Quicktime at the same time, which if corrupted could have caused kernel panics. There is no reason for any XCode software to be loaded at launch with the affect of causing a kernel panic.

Saying this, I will restart my machine now and see if it panics on launch as I have quicktime and xcode installed.