Hmm, ok. One thing that you can try to do is to do a Preprocess and look at the
preprocessor output. Perhaps from there you can see where it is being
defined/redefined and get an idea of what your source is pulling in.
-- jkl
----- Original Message -----
From: "Horace Ho" <[EMAIL PROTECTED]>
Newsgroups: palm-dev-forum
To: "Palm Developer Forum" <[EMAIL PROTECTED]>
Sent: Wednesday, March 28, 2001 2:15 PM
Subject: Re: #defines in "Prefix file" ofproject settings ignored
> Sorry that I cannot send my project source. One point to add, the target
> with
> a .h file define in Prefix file is cloned from a target without the .h file.
> So there
> are two targets, the new target with .h file defined in Prefix file field,
> the old
> target with the Prefix file field empty.
>
> It is really strange. As there is a macro definition conflict (which means
> the
> compiler can 'see' the #define in .h file). And the code segment inside
> #ifdef /
> #endif will take effect if the #define line is moved from the .h Prefix file
> to the
> source .c file itself!
>
> Thanks
> horace
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
