An easier way to do it is to simply do this at the top of your source (no need to hack the SDK headers): #define PILOT_PRECOMPILED_HEADERS_OFF #include <Pilot.h> That is, put the #define before #including <Pilot.h> BTW, what problems were you having that this helped resolve? I'm curious... Rgds, Jun-Kiat Lam Metrowerks Technical Support ----- Original Message ----- From: "Scott Lopez" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, December 05, 1999 9:01 AM Subject: Re: CW6 Constructor eats my CPU > I experienced significant difficulties with R6 on NT. I decided to try > something a little unusual. I created a Palm VII Support directory in the > codewarrior release 5 directory and copied the palm vii directory over. > You will also have to put the following lines at the top of your source > files that use "Pilot.h" > > #ifndef PILOT_PRECOMPILED_HEADERS_OFF > #define PILOT_PRECOMPILED_HEADERS_OFF > #endif > > I have achieved much greater stability in development and have been able to > access all features of the Palm VII libraries and include files. You can > do the same with the 3.1 files also. > > When you do this go to your target settings and change the project > directory to point to Palm VII or whatever library you want to use. Also, > if you are using codewarrior lite make sure you copy the runtime directory > over from the "Palm OS 3.0 Support" directory. > > For all of it's problems I only see a new user interface on the R6 version. > > Hope this helps. > > Denis Faivre wrote: > > > On my machine, each time I start Constructor, CPU usage sticks to 100%. > > I have CW6 running on a Celeron 300A with Windows 95 OSR2. > > > > Did anyone else notice that? > > > > -- Denis Faivre - [EMAIL PROTECTED] > > -- Ablivio - http://www.ablivio.com > >
