On Wed, Jun 08, 2005 at 03:19:46PM -0500, Logan Shaw wrote: > Mark Tigges wrote: > >So, as I've learned more about PODS, and prc-tools I have become quite > >dismayed. We have a visualization library for detail in context > >viewing of GIS data. We have successfully deployed this on 300+MHz > >ARM machines in the past, running various PocketPC incarnations. It > >seems to me that in order to get this working on 5.4 I need to do the > >following: > > > > 1. Compile our C++ library using pacc -pno > > > > 2. Write a C interface for at least (limited functionality) 100 > > functions (about 700 for full functionality) which does the > > following: > > > > a. take the function arguments and compile them into a data > > block. > > > > b. use the PceNativeCall to call the appropriate PNO function > > with that data block as argument. > > > > 3. Write a m68k app with this PNO linked as a resource. > > I think there's another way. You can put 99% of the application inside > the PNO. The stuff that goes outside it is the basic initialization > stuff that handles launch codes and so on. The event loop can go > inside the PNO itself. >
[snip] Logan, first, thanks big time for the detailed reply. This had occured to me before. It's nice to learn about the requirement to split the pno up in the prc stage, not something that I had considered. This method would require very little PNO m68k glue. But, the bottom line is it _still_ IMO would be stupid work. The compatibility layer to the library functions wouldn't be hard to do. Just as you mentioned, tricky to find mistakes. But it's like a throw away stop gap measure until PalmOS 6 devices are ready. From what I read, all 6 apps will be fully native ARM. I might be incorrect in that belief, but the Palmsource site sure seems to insinuate that. The whole m68k/PACE/PNO thing seems to be a giant kludge. I can understand PACE so that legacy apps from previous PalmOS generations still work, but forcing ALL new programs to be m68k too? Strange to me. Thanks again, Mark. -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
