"Danko Radic" <[EMAIL PROTECTED]> wrote in message
news:65597@palm-dev-forum...
>
> I have tried to compile my 3.1 projects under CW R7 to see if it's
easy to
> migrate. PalmOS 3.1 support was placed into CW directory, paths were
set
> within the project etc, but it didn't want to compile reporting
something
> like "Illegal header files" refering to some header files from 3.1
SDK...
>
> Is it possible to make CW 7 to accept 3.1 SDK and compile projects?
>
> I know that most of you would think like why not converting my project
to
> use 3.5 headers.. It's ok with some small projects, but this
particular
> one is some 30 000 lines long and working.. Sorry, but have no nerves
to
> step into such kind of job. I didn't really like that 'source
scorching'
> policy introduced with 3.5 SDK, but now it's beside point anyway...
I am guessing that you're having problems due to precompiled header
files. The 3.1 SDK used precompiled headers to speed up compilation,
but the scheme used was a bit brittle.
It took about fifteen minutes for me to get the 3.0 MineSweeper example
compiling with CW Palm 8. The 3.1 SDK, as downloaded, doesn't put
everything quite right for Windows-based development.
The first thing you need to fix is the PalmOSHeaders.mcp project. This
builds four precompiled header files, but the current CWPalm compilers
don't like the path syntax used on Windows. If you open each PCH file,
you'll see a line like
#pragma precompile_target ":Obj:Pilot.h.mch"
Remove the ":Obj:" prefix from all of these lines, and you'll be able to
build this project. You will notice that in the 3.5 SDK, they created a
Windows and a Macintosh version of this file.
After you do that, you should be able to build a 3.1 project. You may
have to much with your access paths some more, but that should be pretty
easy.
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
