In article <87294@palm-dev-forum>, [EMAIL PROTECTED] says... > Perhaps there's something weird with pre-compiled headers going on, and > you have to rebuild them. Perhaps you're #including <PalmOS.h> from a > prefix file, before your definition of ALLOW_ACCESS_TO_<foo> gets a > chance to have an effect. But I'm just grasping at straws :-), you > should wait for someone more knowledgeable about CW to answer this part. > > Ben, I thought there was something about this on palmoswerks, but > couldn't find it. The closest seemed to be > > http://www.palmoswerks.com/stories/storyReader$12 > > which talks about rebuilding precompiled headers.
I've not posted on this topic, but it seems to be a good one, so I'll write up an article tonight. In V8, new projects are created out of the wizard using one of the prebuild precompiled header files we ship in the box. These headers are built with the strictest options, using the BuildHeaders.mcp project. Since the IDE's browser system doesn't read symbols out of precompiled headers, we rely on a link to this BuildHeaders project to import the symbols into the IDE for coloring and hyperlink purposes. You can see this setting in the C/C++ Compiler panel -- usually, it will be something like "Palm_OS_Headers_Strict" or "Palm_OS_Headers_Strict_Debug". To disable this header, just blank out the prefix file setting. I'd suggest actually building your code that does direct structure access into a static library using your custom settings, and then linking that into the main project that builds the app strictly. You also could just make your own precompiled header that allows the proper settings -- looking at BuildHeaders.mcp is a good idea to see how precompiled header files are produced. -- Ben Combee <[EMAIL PROTECTED]> CodeWarrior for Palm OS technical lead Get help at http://palmoswerks.com/ -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
