• 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
Re: porting code from project builder to xcode
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: porting code from project builder to xcode


  • Subject: Re: porting code from project builder to xcode
  • From: Timothy Standing <email@hidden>
  • Date: Fri, 14 Nov 2003 10:36:39 -0800

I have just finished porting the SoftRAID 3 project from PB to Xcode 1.0. It took me 4 days to complete and I am still not certain that everything is being built correctly.

These are the issues which caused me problems:

- My projects all used precompiled prefixed headers. Xcode does not correctly recompile the precompiled headers if one of the headers changes. Solution: turn off precompiled headers in all projects.

- When I imported a Cocoa PB project into Xcode, the help files, images and Nib files all were left out of the project. Solution: manually add these back to their respective projects.

- Building a Development version of a project enables ZeroLink by default. This means that the full symbol build (i.e. Development build) I need for debugging the kext using the two machine gdb setup will not run on a second machine. Solution: turn off zerolink in all projects in the Development build style.

- All of the scripts I use for building different versions of the SoftRAID (i.e.: debug, release, end-user demo) had to be rewritten to run in bash. Solution: go to http://www.gnu.org/manual/bash-2.05a/ to read up on how bash works. This took me a day as I had no prior experience with bash.

- The Xcode UI does not update correctly if you use the inspector to change the name or location of a file (e.g. .UI graphic image file) in your project directory. Solution: close and reopen your project after changing or adding each individual file to your project.

- The debugger will occasionally refuse to single step or continue past a breakpoint in a Cocoa project. Solution: quit Xcode and relaunch it. Relaunching just the executable you are debugging does not clear this problem.

- xcodebuild (the command one invokes for performing builds from a script) ignores the build style of a project. It alway performs a full build of the deployment build style. Therefore, when I try and build a development build (full symbol version) of the SoftRAID kext using my build script, I can't debug it using gdb. Solution: build a development version manually using the Xcode IDE and then manually copy it into the SoftRAID application. (This gets old fast.)

I hope this prevents others from having to spend as much time as I have tracking down problems with Xcode 1.0. My recommendation for anyone with a large project is to stick with ProjectBuilder until the next version of Xcode gets released. I don't feel that this version of Xcode is ready for production quality development. (Just my opinion.)
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: porting code from project builder to xcode
      • From: Markus Hitter <email@hidden>
  • Prev by Date: Re: std::string crash with optimisations
  • Next by Date: Re: (no subject)
  • Previous by thread: re: porting code from project builder to xcode
  • Next by thread: Re: porting code from project builder to xcode
  • Index(es):
    • Date
    • Thread