I realize PRCMerge is probably complaining about the code resources in the XRD file that were
created when I extracted the resources from my previous .PRC file using GenerateXRD.
This sounds like a job for hand-editing your XRD file. It should be simple to remove the 'code' sections from it.
The build does produce a new .PRC which runs OK until it tries to run a function that
belongs to an extra section, crashing with the messages...
RALLoadModule 18153472 - HostControl.dll : Already loaded, usecount now = 4 RALLinkClient UI.dll --> HostControl.dll run68k.c, Line:4425, Unhandled instr
So I thought you might be able to shed some light on two questions:
-Does PRCMerge leave out my new sections from the new .PRC and use the old code from the XRD instead,
resulting in incorrect address resolutions?
It may do this. It depends of the order of the command line which one will be used.
-Is there a setting in PODS to tell Make that this is a multi-section build other than the existence
of Sections.h and Sections.def? (The make file appears to perform the correct inclusion of my extra
sections).
All of the section work is done using sections.def and the section __attributes__ in your code. Once the prc-tools linker has run, there's nothing special needed to support them.
-- Ben Combee, DTS technical lead, PalmSource, Inc. Read "Combee on Palm OS" at http://palmos.combee.net/
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
