> I've successfully installed Prc-tools-0.5.1b3 on my Linux box
Great!
> and was able to make John Marshall's 'Trashy Little Program'
> (TLP) - which demonstates howto to compile a multisegmented
> palm app, with Palm SDK 3.1.
If you downloaded the TLP more than a couple of hours ago, you should
download it again. I've just updated it to use the new .def file stuff
in the build-prc in 0.5.1b3, and it's a much better sample now. (The
hacks the earlier one used don't work for a real application.)
> (Any chance of getting a Tarball?). [of the SDK]
The build guys have been told to make it a tarball next time, or we'll
hit them over the heads with a stuffed penguin. :-)
> Created a 'header.gcc' file consisting of:
>
> PalmOptErrorCheckLevel.h Dynamic/PalmOptErrorCheckLevel.h
> LibTraps.h Libraries/LibTraps.h
Good stuff. The 3.5 SDK has a `header.gcc' file with these files in it
and a few others, but I guess the version up on the Provider Pavillion
is from before I added it.
> /usr/local/palmdev/sdk/include/Core/System/ErrorBase.h:236:
> warning: possibly bad __callseq__ `trap #15; dc.w sysTrapErrSetJump'
[...]
> multiapp.o(.text+0x2c):multiapp.c: undefined reference to `sysTrapWinDrawChars'
[...]
> As you can see I receive 'undefined reference' errors for all the Palm
> SDK functions I attempt to call. Does this have something to do
> with the ISSUE 1 - 'callseq' problems?
It certainly does! The warning was intended to alert you to this problem
before the link stage, because I had the idea (not sure why now) that under
some circumstances the linker would silently accept the bad references and
then your program would crash mysteriously at runtime. Or maybe I just
wanted to have a useful error message.
Well, I won't bore everybody with the details (email me if you're curious).
To cut a long story short, the answer is:
Congratulations on being the first guinea pig!
Prc-tools-0.5.1b3 and the 3.5 SDK do coexist happily, and in fact they're
working together nicely on my machine here at Palm. Unfortunately, you
have an earlier version of the 3.5 SDK, one from before I made a quite big
change to the sysTrap enumeration for GCC's benefit.
I'm not sure when the next updated SDK is going up on the Provider
Pavillion. Until then, you can make these warnings and errors go away
by hacking in /usr/local/palmdev/sdk-3.5/include/PalmTypes.h:
at about line 208, change
#if __GNUC__ > 2 || (__GNUC__ == 2 && __GNUC_MINOR__ >= 95)
to
#if 0
so that you'll pick up the `systrap' trap call instead of the `callseq'
one. Having done this, you should be able to use all the normal systraps
just fine.
John
