In article <[EMAIL PROTECTED]>, Ben Combee <[EMAIL PROTECTED]> wrote:
> 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? No, there isn't. If I could have multiple .rcp files in my project I'd be completely happy. > Using the RESETAUTOID keyword added in PilRC 2.9p10-CW2, its quite doable > to have multiple RCP files. Ah, but I can't use PilRC 2.9p10-CW2 with Palm 8, can I? I can't use Palm 9 because it doesn't exist for the Mac. I need to continue working anyway and part of that is finding my own way out of Constructor and into multiple .rcp files. Also, the RESETAUTOID keyword doesn't seem to be present in the main tree yet. > 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. I really dislike the idea of using fake targets in this way. It feels like a clunky work-around. Easier to fix the problem at its source. I looked at the archives; when #include .rcp was proposed, nobody could think of a reason why only supporting the .rcp extension was a limitation. Here's a good one. :) -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
