From: "Jason Freund" <[EMAIL PROTECTED]> > I have a relatively big project that hasn't had any > problems until yesterday I wanted to add: > #include <68k/Hs.h> > ...and a few other HS headers from the HandSpring5 > SDK to one of the files. But when I tried to compile > with CW8 (Windows) I get: > > "Error: the file '68k/Hs.h' cannot be opened" > Heh. I spent half of yesterday swearing at exactly this problem when trying to make a small modification to a large project that hasn't been opened in twelve months. And of course I was short of time and didn't need some vague error message.
I suspect that it's a bug in the way header files are managed by CW that hasn't shown up in testing because they always do things properly. What I mean by 'properly' is that I found that headers that were missing the usual #ifndef / #def / #endif lines to prevent double-loading were causing the problems. Initially it also seemed to be related to loading the Palm OS headers (I could make the problem go away in one instance be removing a #include <form.h>). I also found that a new header had a semicolon missing from the prototype (dumb-ass programmer) but I can't remember if this was triggering the "can't open" error or a different error after I fixed that. Sorry to be vague - just trying to provide enough info for you to track down your problem. The interesting thing I found was that when adding the header file to the project (I do this for reference when editing code) two entries would appear in the project hierarchy. One for 'header.h' and one for 'header.h#include'. I could delete the second one but then couldn't turn on the dot that includes the file in that project. It was also file-specific, in that I could remove all object code and recompile the project and the header would load happily for some C files and fail for others. The fact that I also had a different problem that caused the vague "A file could not be added to one or more targets" error meant that I'm surprised the CW team couldn't hear me swearing all the way from NZ. That one was also painful - a project with existing rcp files wouldn't accept another rcp file because there wasn't a file mapping for that suffix. A error message to that effect would have saved me a frustrating half hour. Chris Tutty -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
