> Ben/Metrowerks guys, don't be so touchy, just my frustration late at
night.

My frustration late at night too. :)

> Anyway, what I had done, last night, was because the CW6 folder was
still on
> my machine I had pointed one of the access paths to "..\CW for Palm OS
> R6\Palm OS 3.1 Support"  which developed the "Error :illegal
precompiled
> header version. Pilot.h line 36    #include "Pilot.h.mch". error.
Thinking
> about it I removed these points and re-assigned the access path to
> "..\CodeWarrior for Palm OS Platform 7.0\Palm OS 3.5 Support" now of
course
> the error messages have changed, when I compile to 1.) "Error : the
file
> 'Us.Prefix.h' cannot be opened.." and 2.) Error : the file 'Pilot.h'
cannot
> be opened Main.c line 16 #include<Pilot.h>".

Moving from the 3.1 SDK to 3.5 or later SDKs is a big process.  You will
need to change all of your includes, but with the PalmCompatibility.h
header, you can put off changing most of your source code.

> Does this mean I will have to go thru all my applications that I built
under
> CW6 for Palm OS 3.1 and change the include statements to PalmOS.h and
etc.
> to now compile under CW7? Is there a section in the CW docs that
explains
> this 'coversion' process for OS 3.1 CW6 to CW7?

Here are two articles that can help, depending on what you want to do.

The first is http://www.palmoswerks.com/stories/storyReader$12 -- this
talks about how to install the 3.1 SDK on CW Palm 8.  It should work the
same way on version 7.  This isn't a supported configuration, however.

The second article is http://www.palmoswerks.com/stories/storyReader$17,
which talks about updating to the 3.5 or 4.0 SDK.  It has a link to
Palm's article on the subject, and some extra commentary by me.

PalmOSWerks is my own personal weblog site where I archive articles I've
written on different Palm OS programming subjects -- look around and see
if anything looks interesting.



-- 
For information on using the Palm Developer Forums, or to unsubscribe, please see 
http://www.palmos.com/dev/tech/support/forums/

Reply via email to