The .lib is there. It's not a linker problem since the compiler itself is
generating the system traps and not the library calls. (ie: I can load the
app on Palm OS > 2.0 and it works fine but dies under OS v1).
This project worked perfectly under R4, including multiple targets with
different floating point options. I don't understand why it won't work
under R5.
I really also want to understand why _DONT_USE_FP_TRAPS_ isn't defined at
all with this version of the compiler. Under the R4 compiler this was
defined to either 1 or 0 depending on what floating point code you were
using.
Thanks though!
Richard Wagner
> -----Original Message-----
> From: Michael Yam [mailto:[EMAIL PROTECTED]]
> Sent: Monday, March 15, 1999 9:08 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Codewarrior R5 & Floating Point Library
>
>
> Check out SampleCalc.c for an explanation. Using "PalmOS" generates
> floating point code for PalmOS 2.0 and later. Setting it to
> "Library" for
> PalmOS 1.0 compatibility requires "NewFloatMgr.lib" to be
> linked with the
> code.
>
> Michael Yam
> Y Technology, Inc.
> [EMAIL PROTECTED]
>
> -----Original Message-----
> From: Richard Wagner <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> Date: Monday, March 15, 1999 8:42 PM
> Subject: FW: Codewarrior R5 & Floating Point Library
>
>
>
> I recently converted to R5 (from R4) and I can't seem to get
> R5 to handle
> when
> I change the floating point from "PalmOS" to "Library". In
> fact regardless
> of
> what the setting is the constant "_DONT_USE_FP_TRAPS_" doesn't get set
> either
> way! That constant is still referred to in NewFloatMgr.h.
>
> Obviously I'm missing something that changed although I can't
> figure out why
> it
> doesn't work.
>
> Thanks
> Richard Wagner
>
>
>
