• 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
Giving up on build styles
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Giving up on build styles


  • Subject: Giving up on build styles
  • From: David Catmull <email@hidden>
  • Date: Mon, 18 Apr 2005 11:16:37 -0700

I've been working on converting our CodeWarrior application and library projects to XCode, and have finally come to the conclusion that we have to use targets instead of build styles. It was a reluctant decision because we're just doing debug/final builds, and that's what build styles are supposed to be for, but build styles don't work the way we need them to.

Below are the main problems I ran into. Has anyone else run into these issues? Did you come to the same conclusion?

* XCode doesn't deal well with build styles changing the name of the product. I used the Executable Prefix setting to produce libXXX and libDebugXXX versions of all our libraries, and XCode got confused by this: it only showed one item in the Products group, and the name would change between debug and regular now and then.

* When building a project that the current target depends on, the current project's build style is used rather than the subproject's. For me this was bad because, in my application project, I was using the Other Linker Flags field in my build styles to specify whether to link to the debug or final versions of the libraries, and having that applied to the library projects caused errors. You don't want a library project trying to link to the library it's supposed to produce. I thought of working around this using a shell script build phase to manually specify the build style, but that's a hack that shouldn't be necessary.

* Build styles can't exclude source/resource files. This was the final straw. We have extra stuff for running unit tests and displaying the results. The UI resource files involved should not be in the final build, and we don't want to waste cycles compiling test code for a final build even if it will get dead-stripped out.

--
David Catmull
email@hidden
http://www.uncommonplace.com/

_______________________________________________
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: Giving up on build styles
      • From: "Timothy J.Wood" <email@hidden>
    • Re: Giving up on build styles
      • From: Andreas Grosam <email@hidden>
    • Re: Giving up on build styles
      • From: Ricky Sharp <email@hidden>
  • Prev by Date: Set java package location
  • Next by Date: Re: Giving up on build styles
  • Previous by thread: Set java package location
  • Next by thread: Re: Giving up on build styles
  • Index(es):
    • Date
    • Thread