In article <[EMAIL PROTECTED]>, "Baxter" <[EMAIL PROTECTED]>
wrote:
> Ah, yes - I see "PalmOS_Headers_Debug". I assume I just clear the field?
> (and then add the headers I need in my source files.)
You could. But the precompiled header can be the difference between 5
minute compiles and 20 se
Ah, yes - I see "PalmOS_Headers_Debug". I assume I just clear the field?
(and then add the headers I need in my source files.)
--
-
Free software - Baxter Codeworks www.baxcode.com
-
At 06:59 PM 11/23/2004, you wrote:
I ended up doing something like you suggest. I couldn't get Ben's
suggestion(s) to work, then I noticed that my .cpp files weren't even
including the PalmOS.h -- so I've probably got something pathological going
on.
No, your project is likely using a precompiled
At 06:27 PM 11/23/2004, you wrote:
In article <[EMAIL PROTECTED]>, Ben Combee <[EMAIL PROTECTED]>
wrote:
> Note: if you're using a precompiled header, that will override the
> fresh include of PalmOS.h, so you'd be best to make your own static
> library that does this access built without precompil
I ended up doing something like you suggest. I couldn't get Ben's
suggestion(s) to work, then I noticed that my .cpp files weren't even
including the PalmOS.h -- so I've probably got something pathological going
on.
My issue is that this code was developed on the Macintosh, while I'm
developing u
In article <[EMAIL PROTECTED]>, Ben Combee <[EMAIL PROTECTED]>
wrote:
> Note: if you're using a precompiled header, that will override the
> fresh include of PalmOS.h, so you'd be best to make your own static
> library that does this access built without precompiled headers, and
> link that in
Ben Combee wrote:
> At 05:18 PM 11/23/2004, you wrote:
>
>> My other options are quite unpleasant: 1) back up to an older SDK, 2)
>> modify the BuildDefaults.h file in the SDK.
>
>
> You can also make your own glue code -- just #define the appropriate
> macro to allow access to the structures
At 05:18 PM 11/23/2004, you wrote:
My other options are quite unpleasant: 1) back up to an older SDK, 2)
modify the BuildDefaults.h file in the SDK.
You can also make your own glue code -- just #define the appropriate macro
to allow access to the structures you need before you #include
In this
I inherited some legacy Palm code that I'm trying to compile with the latest
CW compiler and SDK 5.
I get the error: "illegal use of incomplete struct/union/class 'struct
FormBitmapTag'."
This is because with SDK 4.0 and up access to struct internals is blocked.
The problem I have is that the do
