Lance Drake wrote:
As I am very new to the Palm development world, it's no surprise that I'm not familiar with all of the nuances which may be a part of successfully creating a project build environment.
In particular, the project which I have been handed was originally being built with version 9 of the CodeWarrior Palm OS development package - owned and retained by the previous developer. Unfortunately, this package is not currently for sale by Metrowerks. I found a v6 package on eBay - purchased it, then realized it requires an existing CW install with 68K compilers, etc - which I do not have.
So, I moved over to the PalmOS development area, went thru the agony of putting 'default: break;' at the bottom of every switch statement in the source, and slugged thru several other anomalies not supported by the gcc compiler versus CW. Finally I got to the point where it was supposed to link and saw the "Showing the first 100 of 617 link errors "relocation truncated to file: DISP 16 funcname" report.
After reading the 'Sections.h" file in the project, it was not clear whether I had to not only add the 'EXTRA_SECTION_ONE' macro after the declaration and definition but also in every instance where the call was invoked from within the code. To wit, Sections.h indicates, "...the annotation has to be visible at the function definition and everywhere the function is used." Oh please... say it ain't so.
Nothing I do seems to reduce the number of errors. Can anyone point me to a specific laundry-list of steps I can invoke to get this multiple-segment-mess straightened out?
Thanks VERY much,
Lance Drake
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
--
For information on using the PalmSource Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/support/forums/
