Jaba,

Does it ignore the target if you actually define a different target and
set the new access path inside the separate target and don't define the
english access path?  Since that sounds really confusing, even to me,
maybe I'll just ask this - have you tried defining a french target and
an english target and only defining the access path for the french
version of your config.h file in the french target and the access path
for the english config.h in the english target?

DeAnna

-----Original Message-----
From: Jaba Adams [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 21, 2001 2:06 PM
To: Palm Developer Forum
Subject: CW 6.5 per target #defines - how?


Hi there,

I'm running into a problem with a localization project.
I'd like to have one English and one French target that define different

preprocessor macros.
In this case, the English and French versions are separate apps, with 
different creator IDs, but shared code.

For example, in my startup code I'd like to do something like:

#ifdef TARGET_FR
        // Check for International Manager.
        // If not present, issue error and exit.
#endif

Idea #1: Set up preprocessor definitions in the project settings.
I can't figure out how to do this in CW 6.5. I've checked the manuals,
kb 
and list archive.

Idea #2: Include a config.h file, where I have two versions, each in a 
different access path.
Unfortunately CW 6.5 ignores the access path and always includes the 
English config.

My directory structure:

{Project}
        \config-en
                config.h
        \config-fr
                config.h

In the French target, I add the config-fr access path; in the English 
target, I add the config-en path. This doesn't work! I've also tried
this 
with separate projects, rather than separate targets.

I'd really like to keep one common code-base.

Thanks!

Jaba Adams
Shinyfish Software
http://www.shinyfish.com


-- 
For information on using the Palm Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/tech/support/forums/

--
For information on using the Palm Developer Forums, or to unsubscribe, please see 
http://www.palmos.com/dev/tech/support/forums/

Reply via email to