• 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
Targets, configurations, etc
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Targets, configurations, etc


  • Subject: Targets, configurations, etc
  • From: Steve Mills <email@hidden>
  • Date: Thu, 8 Sep 2005 14:23:46 -0500

I'm starting our conversion from CW to Xcode. Now that Xcode has Build Configurations, it helps a bunch. The old way was, well, gross. However, I'm still confused about something. If you edit the Project Settings, the Build Configurations are obvious. But when I edit the Active Target, it also has the same Configuration popup. If I make changes here with the Configuration set to Debug, for instance, the target's settings then override the project's Debug configuration settings. Correct? Why would I want to do this? As far as I understand the order of settings, I should only need to make changes to the Project's configurations, then delete an overridden settings in the target. Correct?

Barring understanding the above, here's a somewhat different question. The project I'll be converting later has 5 targets in the CW project: Pro Debug, Pro Release, Pro Beta, Desktop Debug, and Desktop Release. Pro and Release are 2 different versions of our app, with Desktop having less features than Pro.

All our projects are based on our own application framework (not to be confused with a .framework). This framework includes a .rsrc file, a localizable .rsrc file, and a .strings file. Each project can also contain its own .rsrc and .strings files, however, some project resources or strings might override the framework's resources or strings. CW handles this by not copying resources in later files that have already been copied from earlier files. So we always make sure the project's .rsrc file comes first in the link order, then the framework's .rsrc file. When we switched to building a bundled app, I had to use a PostLink.sh script to use the ResMerger tool to merge the localizable .rsrc files into the correct place in the package. Then earlier this month I switched to using .strings files and had to write my own app to merge these. This is also executed by the PostLink.sh script.

Additionally, the Desktop targets contain extra .rsrc and .strings files that override the project's normal resources and strings.

Having explained all that, I'd like suggestions for how I should set up an Xcode project for this. Because Desktop needs additional files, I'm guessing I'll need to use more than 1 target. Having read the documentation for Build Phases, I didn't noticed anything that would cause a .rsrc file to be copied only in some cases.

Steve Mills
Drummer, Mac geek
http://sjmills5.home.mchsi.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: Targets, configurations, etc
      • From: Fritz Anderson <email@hidden>
  • Prev by Date: Re: XCode Rules!
  • Next by Date: compile error while switching from gcc 3.3 to 4.0
  • Previous by thread: Re: Class Diagram colors - bug or blindness?
  • Next by thread: Re: Targets, configurations, etc
  • Index(es):
    • Date
    • Thread