Dunno. I find this trick so useful, that I've been quite content for years with the tradeoff of using CW to compile, and then using nmake to post-link the resources via Pilrc (sending the .rcp file first through the C++ preprocessor, which by the way handles #include as well).
Back in '98 before Pilrc was able to emit the resources directly into the .prc, I wrote an RCPalm.exe to post-link the .bin files generated by Pilrc into the .prc file generated by CW. (I can only guess the reason I wrote a separate tool was because I didn't know Pilrc's source code was available; what was I thinking?? :-O Otherwise Pilrc would have had that capability much sooner ;-). "Steven Fisher" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > In article <[EMAIL PROTECTED]>, > "Chris Antos" <[EMAIL PROTECTED]> wrote: > > > Here's a trick I use. I pass my .rcp files through a C++ preprocessor > > first, which handles conditional directives, strips comments, allows me to > > use C style macros, etc. And I don't have to deal with any quirks in how > > Pilrc parses stuff. > > I wonder if there's a way to pull that off with Codewarrior. It seems it > should be possible to add a hack to that effect to the PilRC plugin, now > that I think of it... > > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
