I used PilRc Designer to convert my rsrc file to an rcp file, replaced same
in a copy of my old project that I've converted to V9. It worked fine with
the Mac68 and PalmRez linkers, but, like a good boy, I'm trying to keep up
with the times and use the PalmOs linker. So, I made the conversion,
replaced the resource file in my project with the .rcp, changed linkers in
the settigns panel, hit the Make button and got ....
Warning : OS Error The parameter is incorrect.
(87)
Project: VitalSignsR9.mcp, Target: VitalSigns, Source File: VitalSignsr9.rcp
Error : Unable to call the command line tool. Check your PATH environment
variable.
Project: VitalSignsR9.mcp, Target: VitalSigns, Source File: VitalSignsr9.rcp
Error : Compile failed
Project: VitalSignsR9.mcp, Target: VitalSigns, Source File: VitalSignsr9.rcp
I downloaded the V9.1 patch and tried again with same effect. I'm on a
Win2kPro box with CW V9.1. Did I miss a step? I did look at my PATh
variable and it didn't mention any folders relating to CW - although I'd
expect the CW install to take care of that, if it was necessary. What SHOULD
my path variable include? (if that is indeed the way to get the pilrc
compiler to launch..)
Thanks, Randyp
<Begin Whine>
you know, I can piss away enough unbillable hours in bugs of my own making
without spending DAYS converting projects/project settings everytime you
folks deliver a new release. I feel I can say this 'cuz I've got CD's on my
desk from the first release (which never compiled ANYTHING successfully, as
it was convinced it was still running on a MAC) to the present V9, excepting
V7 & 8, which I skipped because I had a shippable product compiled with Rel6
and didn't dare fiddle with it by changing my tools. Instilling that kind of
fear in your users CAN'T be good marketing strategy. I only bought V9
because my clients are wanting to move to V5 and high res Sony's and such.
</Whine End>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
