Hmm. OK, perhaps I should clarify. I understood the original question to
mean how to set specific DEBUG targets, which could be done using #ifdefs,
but in CodeWarrior is normally done using Debug targets. You could use
#ifdefs and prefix files in order to determine which specific portion of the
code would be debugged though. That is you #ifdef your code, and then set
the flag in the prefix file (Project settings->C/C++ Language) depending on
which target you want to debug.

Sorry if I caused any confusion.

Jun-Kiat Lam
Metrowerks Technical Support

----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, August 20, 1999 5:02 PM
Subject: Re: #ifdef debug (or similar)


> Chris,
>
>     I agree this works great and that was sort of my point; however,
> Jun-Kiat said "In CodeWarrior, you would use Targets instead of #ifdefs."
> and I did not understand how a new target negates the need for a #ifdef.
>
> Ron
>
>
> >that's what i do.  it works great.  i'm not really sure what else you'd
be
> >looking for.
> ..
> >
> >do you mean you want to exclude specific file from one or more targets?
> >select the file in the project window, then hit Alt-Enter (or click the
> >Project Inspector toolbar button or choose Window->Project Inspector).
> >make
> >sure the Targets tab is selected, and then check/uncheck the desired
> >targets.
> ..
> > Interesting, I use multiple targets but I still need #ifdef's so the
code
> > can be include/excluded by the target.  The extra target just
> > allows me to define or not define to include/non include the code.
> >
> > Am I missing a better way ?
> > How can a target alter the code without #ifdef's ?
> ..
> > In CodeWarrior, you would use Targets instead of #ifdefs. In the Project
> > window, select Targets, select Create Targets, Clone an existing Target
> and
> > then build this new target with debug information and libraries. This
new
> > target will become the debug version of the target you cloned.
> ..
> > Rgds,
> > Jun-Kiat Lam
> > Metrowerks Technical Support
>
>
>

Reply via email to