• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
glitch upgrading from Xcode 2.0 to 2.4
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

glitch upgrading from Xcode 2.0 to 2.4


  • Subject: glitch upgrading from Xcode 2.0 to 2.4
  • From: email@hidden
  • Date: Sat, 23 Sep 2006 17:56:16 -0400

Today I upgraded from Xcode 2.0 to 2.4. It was not a trouble-free upgrade, I'm sorry to say.

My application is a 'terminal' app - it makes no use of any OS resources other than memory allocation. This is so I can easily transport the code between MacOS, Windoze, and Linux. Thus, I expected no problem when moving this relatively undemanding app to 2.4.

After doing the installation and booting Xcode 2.4, I started getting random "Internal Error" messages indicating that some object was expecting a nonzero field, but was finding a zero field. When I tried to build and run my app (ignoring the periodic non-fatal Xcode 2.4 internal error messages for the moment), the build completed successfully but it didn't boot into a "pseudo-terminal". Instead, I got the familiar "Internal Error" message.

After poking around and figuring out a tiny part of what Apple has actually done in moving from 2.0 to 2.4 (thanks for
the poor-quality release notes!), I found that build products for the development phase now go in their own subfolder called 'Development'. However, in the initial Xcode 2.4 project (built by Xcode from the 2.0 project), there was a folder WITH NO NAME that corresponded to the new /build/Development subfolder that was automatically created by Xcode 2.4. So, I renamed the unnamed folder to Development, and was able to build and run within a pseudo-terminal successfully. I also don't get any more "Internal Error" messages. I suspect that the initially unnamed 'Development' folder was causing the Xcode 2.4 internal errors.


I'm surprised that such a simple problem could have escaped Apple's regression testing (assuming that
they did any :-) Thank goodness that everything else seems to be working normally now (my app's own regression tests all passed
successfully, and I've done one new build cycle without any anomalies).


Good Luck!

________________________________________________________________________
Check out the new AOL. Most comprehensive set of free safety and security tools, free access to millions of high-quality videos from across the web, free AOL Mail and more.


_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: glitch upgrading from Xcode 2.0 to 2.4
      • From: Mailing list subscriptions <email@hidden>
    • Re: glitch upgrading from Xcode 2.0 to 2.4
      • From: Chris Espinosa <email@hidden>
  • Prev by Date: Re: Attach to Process to debug Framework
  • Next by Date: Re: glitch upgrading from Xcode 2.0 to 2.4
  • Previous by thread: Re: Run Script build phase and osacompile
  • Next by thread: Re: glitch upgrading from Xcode 2.0 to 2.4
  • Index(es):
    • Date
    • Thread