Well, one thing that I am using but is totally old and unsupported is
multilink: http://www.djw.org/product/palm/multilink/
I had some problems getting it built with the latest cygwin (the
released binaries didn't seem to work), but I did eventually figure it
out. Basically, it ignores all your sectioning and resections your app
for you at link time.
These are the lines from my makefile that create the PRC:
# Replaces the link step
m68k-palmos-multilink -stdlib -fid $(JMP_FID) $(LDFLAGS) $(OBJS)
mv -f *.grc $(WORK_DIR)
build-prc -o $(TARGET) -n "$(APPLICATION)" -c $(CRID) $(DEFFILE)
$(WORK_DIR)/*.grc $(WORK_DIR)/$(ROFILE)
And I don't have to do any section crap at all, which is what
m68k-palmos-ld should do for you. Also, if you are using C++, like me,
and your code generates any C++ exception handling symbols, multilink
totally freaks out, so I had to disable that. The problem for me was
that it would generate that stuff no matter what flags i specified if
I had any pure virtual functions. Bleah. So much for good
object-oriented design.
-DG
Hi David,
THANK you - so much - for chiming in so quickly with your thoughts and
suggestions. That 'Multilink' approach appears to have real merit.
The code I inherited is all standard C - so there's no exception
situation to worry about.
After taking a look at the makefile(s) situation - I am a little
confused about exactly what gets replaced in which file - For instance
'JMP_FID' does not seem to be currently defined anywhere - but I went
to the djw.org site and will try to incorporate the materials as best I
can.
Again - your response is greatly appreciated. I'll post the results
when I get a couple of paces ahead of where things currently are.
Best Wishes,
Lance Drake
--
For information on using the PalmSource Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/support/forums/
