Slashdot Mirror


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.

7 of 46 comments (clear)

  1. Re:Reason for pulling Xcode by stingerman101 · · Score: 4, Informative

    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"

  2. Re:Reason for pulling Xcode by capmilk · · Score: 4, Informative

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

  3. Where's the news? by Sklivvz · · Score: 5, Funny

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

  4. Re:Reason for pulling Xcode by mj_1903 · · Score: 5, Informative
    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.

  5. More updates... by djupedal · · Score: 4, Informative

    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. "

  6. Buy Apple Stock Because by LinuxMacWin · · Score: 5, Interesting

    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.

  7. Re:More information? by Moses+Lawn · · Score: 4, Insightful

    ...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?

    --

    What if life is just a side effect of some other process and God has no idea we exist?