Proposal:
Add a second file extension that PilRC will recognize as a Palm resource file.
Background information:
I use the VSS plugin with CodeWarrior. Because of this, I like to have all of my files (including headers) in the project file. This way I can quickly tell if a file is checked in or not even if it is not usually compiled.
Beginning a few versions ago, pilrc (and the plugin) supported #include of other .rcp files. However, the file *must* have an extension of .rcp to be parsed as pilrc source.
The problem is that if I add these sub rcp files to my project, the Pilrc plugin will try to compile them as well.
Is there a compelling reason to compile these as part of your master RCP file instead of compiling them as separate RCP files and merging all the resources from the different RCP files at link time?
Using the RESETAUTOID keyword added in PilRC 2.9p10-CW2, its quite doable to have multiple RCP files.
The other option for you is to have those RCP files be a member of a "Do not compile" target in your project and remove the target dots from them in your real targets. That will maintain them as project files while not including them in the build.
--
Ben Combee <[EMAIL PROTECTED]>
CodeWarrior for Palm OS technical lead
Palm OS programming help @ www.palmoswerks.com
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
