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

Reason for pulling Xcode

[Anonymous Coward]

Does anyone happen to have any information about the withdrawal of Xcode 1.1? I'm interested in this because I'm going to finally upgrade to Panther + Xcode today.

Re:Reason for pulling Xcode

[stingerman101]

From Apple's xCode Discussion thread:

"Due to a server-side glitch, we had to pull the update. We are working on the problem and I'll post when it is available again.

Scott"

Re:Reason for pulling Xcode

[capmilk]

You forgot to quote the most important part:
"For those that have already installed the 1.1 update, you are fine."

Re:Reason for pulling Xcode

[mj_1903]

I wouldn't say that. I have seen some issues with this build already, and its less than 3 hrs old on my machine. Quick observations:
- Under some circumstances builds will fail (unsure of the circumstances) and you cannot shutdown the build in anyway or restart it. The only way to fix the issue is to force quite Xcode.
- Some of my projects had weird linking errors and complained about: "Dependency Analysis". Rebuilding the project fixed this annoyance.

After those events though (the former was repeatable), I would have to say its a nice update. Code Sense is much much much faster than before. The interface has been tweaked in my deparments, for the better IMHO and build times has stayed the same which is always welcome (although I would love it to be faster).

As Apple said, there is no reason to worry about your Xcode installations, we are just going to have Xcode 1.1.1 as soon as Apple get back on the 5th of Jan.

Re:Reason for pulling Xcode

[redJag]

Yes, they pulled it because it was showing up on every machine, rather than just ones that had XCode installed. Nothing wrong with the update, though, so no worries!

Re:Reason for pulling Xcode

[javaxman]

The glitch was that it was showing up in Software Update even on machines which didn't have the developer tools installed.

For those machines, it would continue to show up even if the package was installed.

So there's a problem with the installer, not the code. I'm sure it'll be fixed soon if it isn't already fixed.

Re:Reason for pulling Xcode

[Rosyna]

"For those that have already installed the 1.1 update, you are fine."

For those that are confused by the above statement:

If you have already downloaded Xcode 1.1, the version on ADC of if it comes back to Software Update is no different so you do not need to download it again.

In general happy speak "you are fine" means "don't waste time downloading again"

Re:Reason for pulling Xcode

[Geoffreyerffoeg]

I think we slashdotted Software Update.

Where's the news?

[Sklivvz]

I use Windows XP and get way more updates than Mac users, so I win!!!

Re:Where's the news?

[Anonymous Coward]

(Score:-1, The Awful Truth about Macintoshes)

Shall we add to that the $129 annual fee to continue to use any updated application?

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?

[bsartist]

For instance, if they've upgraded gcc.

I didn't see anything in the release notes that specifically said anything about a new GCC. Here's what I get with "gcc --version":

gcc (GCC) 3.3 20030304 (Apple Computer, Inc. build 1495)

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?

More updates...

[djupedal]

Apple released DVD Studio Pro 2.0.3 and Compressor 1.1.

"The DVD Studio Pro update includes changes from DVD Studio Pro 2.0.1-2.0.3, adds support for Cropped D-1 and 1/2 D-1 MPEG-2 video resolutions, changes the behavior of the dual-layer break point for DVD-9 projects, and more.

The Compressor update "dramatically improves" MPEG-2 encoding performance, optimizes presets, and enhances the reliablity of the Submit button. "

Maybe not fine

[hargettp]

Today's MacIntouch is reporting that some users are encountering kernel panics and have had to reinstall Panther after installing Xcode 1.1. Probably pulled for very good reasons.

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.

Re:Maybe not fine

[mj_1903]

Restarted with no issue. I doubt Apple would have pulled it for one person panic'ing. If everyone did, yes, they would have (aka 10.2.6).

Re:Maybe not fine

[squiggleslash]

Seems unlikely that XCode would cause Kernel panics. I don't believe there's any aspect of XCode that actually runs at a level that would cause such a thing.

Re:Maybe not fine

[Anonymous Coward]

Widespread Panic

Re:Maybe not fine

[Rosyna]

Neither QT or xcode lode anything into kernel space, it is unlikely (if possible at all) they'd cause a kernel panic.

Re:Maybe not fine

[prockcore]

He did install Quicktime at the same time, which if corrupted could have caused kernel panics.

You gotta love software design that makes your kernel crash if the movie playback library has problems. Kind of like making a web browser part of the OS.

Buy Apple Stock Because

[LinuxMacWin]

Something's up. Per websites, not much speculation about the coming MacWorld. The noise re MacWorld is much lower than years past. Apple has released / patched / upgraded so many product lines in the past quarter. Looks like MacWorld will not have much to demonstrate. Unless Steve wants to talk about the year that was rather than the year to come.

Or is there something going on. Watching Apple for a long time, I am suspicious.

Sorry if it is offtopic re Xcode etc., but I think my comments covers what is going on in general than this specific thread.

Re:Buy Apple Stock Because

[aftk2]

Actually, I would disagree (although you are correct that rumor sites haven't really been speculating too much). The reason I would disagree is that Jobs is actually giving the Keynote speech this year. At this past Macworld (the name of which was changed to something else, I believe) he didn't.

It is true that Apple wanted to break the linkage between product announcements and Macworlds, if only for more flexibility. But if Jobs is giving the keynote, I would imagine that at least something marginally interesting is going to come out.

[cringe] God, I'm such a fanboy. [/cringe]

Re:Buy Apple Stock Because

[speechpoet]

Not quite. Steve Jobs has given the keynote at January's Macworld San Francisco for donkey's years. The one held every July,Macworld New York (sorry... it's 'Creative Pro'! no, wait, it's 'Macworld Creative Pro'! no, wait, it's 'MacWorld Essentials LE'!), is the one that Steve has been blowing off.

distccd

[Slur]

Actually, when you enable distributed compile it causes distccd to load at startup. That means, in case you didn't know, that you don't need to keep XCode running on machines that you use for remote compiling.

Re:distccd

[mj_1903]

I have distributed compiles enabled, but there is no reason that should cause a kernel panic.

The Beauty of Slashdot ...

[mach_5]

Is I no longer have to manually check software update. I just read the slashdot headlines.

XCode 1.1 available from connect.apple.com

[davester666]

It's the same version that was available yesterday [or so Apple claims]. You can either download an updater or a complete installer.

There's also a separate "Xcode 1.1 Assembly Rule" download for assembly language programming [which everyone on /. uses, of course].

Re:XCode 1.1 available from connect.apple.com

[davester666]

Ugh. After seeing a message on the xcode-users mailing list, I downloaded the full installer of xcode [previously, I had applied the updater]. It turns out that if you really want your developer tools updated, you need to download the full XCode 1.1 installer. For example, InterfaceBuilder only gets updated to v2.4.1 [from v2.4] using the full installer.

This seems pretty stupid. I can't imagine any developer wanting just parts of the developer tools updated...and it's not clear which parts the XCode Updater updates [just XCode?].

Final Cut Pro update and PCI Macs

[HTH NE1]

And like always, since they've updated the version of Final Cut Pro, non-AGP Mac users will need to edit the application's Info.plist file again, changing "AGP" to "PCI". Instructions here.

This little hack has let me delay buying a new G5 until I have gathered sufficient funds.

battery

[y0bhgu0d]

there was also a "Battery Update"

don't remember the details, but i downloaded and installed it. Panther, iBook

Re:battery

[prockcore]

Yeah, a co-worker's 2 year old iBook's battery life went from 1 hour to 1:30..

man laptop batteries are pathetic.

You lie!

[Anonymous Coward]

Everyone knows that apple produces perfect software! It must be your hardware!!!

<joke>

2003-12-19 Security Update was posted today.

[ITR81]

Fixes: AFP Server, ASN.1 Decoding for PKI, cd9660.util, Directory Services, fetchmail, fs_usage, rsync. and System Initialization. Xcode 1.1 was put back on the Update Server today after a server glitch yesterday caused it to be pulled. Quicktime 6 MPEG-2 Component is also updated today as well. This was fix an issue where the component expired on the 15th of Dec.

Re:tsarkon reports on Sir Haxalot, /. whore.

[Anonymous Coward]

"Home is where the Hard is". Hahahaha! That's classic.

sicko.

Funny man

[FredFnord]

Well, if you think about needing to absolutely ensure that an audio stream gets a certain number of processor cycles and never gets swapped out no matter what, and the video stream can't have its priority downgraded after hogging the processor for a while (which is what normally happens to a process in the MacOS X multitasking model when it hogs too many resources) and all sorts of other fun stuff... ...then yes, actually, you DO have to love it. Because it works better that way.

-fred