InDesign CS/CS2 Mac - making a target-specific macro

Question

Hello.
This is more a CodeWarrior question than an InDesign question, but because the difficulty is caused by the SDK, I am asking the question here. If anyone objects to the question, I recommend not responding.
I want to do this in one of my projects (greatly simplified code to illustrate concept only):
void MyCall(PMString AString)
#ifdef PRE_RELEASE_VERSION
CAlert::InformationAlert(AString);
#endif
I want to set up my project so that if I am running a prerelease version of my plugin, PRE_RELEASE_VERSION is automatically defined by a compiler flag.
In Visual Studio this is simplicity, itself. The flag is something like /DPRE_RELEASE_VERSION. I can include it in the Preprocessor definitions field in the Properties pane. In XCode, a similar feature is present. But I have spent the last two hours studying CW8 and CW9 for a similar ability, and the closest I can come is to modify the SDKPluginPrefix.h file, which is the file automatically placed by Dolly in the Prefix File field of the C++ Language pane in the CW Target Settings Panels.
The problem is that we are not allowed to modify the SDK, as part of the rules we agree to when we download the SDK. Now, I suspect that if I did modify the SDKPluginPrefix.h file to include an additional #define statement, I doubt that Adobe would come hunting me down, nevertheless, I would rather honor that agreement.
Another possibility is some elaborate scheme of header files included in only one target, etc, but I would rather seek simplicity, if at all possible.
Is there
b any other way
to set up a macro in CW for a single target only?
TIA!
John

Answer 1

if you are using CW8, click on the target settings on the Project Window. Under the Language Settings > C/C++ Language, enter your own "Prefix File" name. In this of your own prefix file, #include "SDKPluginPrefix.h" and enter whatever you feel like defining.
In CW 9, click on the target settings, too but look for C/C++ Preprocessor. do your #define there.
Since these are per target settings, you will need to do the same for all the targets.
HTH.
pete