> From: Scott Dreslinski [mailto:[EMAIL PROTECTED]] > been asked by a customer to support Portugese. [...] > I also assume i will make another target for Portugese, > and then build that target.
(Here's my $.02 based on a nonzero amount of experience...) I recommend *not* using separate targets. That can get unwieldy as you add more and more languages. Instead use targets to isolate language-independent build options. In particular you probably want a Debug target and a Release target, each with appropriate settings for compiler optimization, A6 frames, MacsBug symbols, and so on. Then to configure language, use the Access Path and Source Tree functionality of CodeWarrior. Put your different language resources into separate directories. Create a Source Tree that points to the currently desired language. Use that Source Tree in an Access Path in the project. To vary language, make your Source Tree the kind based on an environment variable or Windows registry key, which you can then modify outside CodeWarrior to effect a change in the final access path the IDE uses. This can be neatly managed in a build script or batch file. (I don't know the Mac equivalent.) Or to get really fancy, you can automate the IDE via its COM interfaces to manipulate access paths under more direct control. I wrote a VBScript program for this, which launches the IDE and tweaks one of the access paths to point to any specified language directory, and optionally does a build. The documented COM interfaces work well and are easy to use from VBScript, and (I assume) any other COM-enabled tool. -slj- -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
