OK Ben.  Thank you for the information.  That white paper came in handy;
although, I do have another question as a result of reading it.

I turned on the "PC-Relative Constant Data" switch in the settings panel and
made certain that all of my globals that I was concerned about were declared
as const and I even got rid of the pointers inside of these const structs
just as the white paper informed.  Well, the number on the data side went
down to 0, so I thought it had worked.  Well, upon rebuilding the project, I
get the following warnings (which sound serious):

"Segment 'Data Segment 2' is greater than 64K, it will generate an invalid
PRC file."
AND
"PalmRez Warning: Output resource size is greater than ~64K size limit:
'code 3'"

Like I mentioned in the previous email, I split my project into 5 segments.
"Data Segment 2" used have 29K of data and 0K of code.  Now, after the
PC-Relative Constant Data switch, both the code and data are listed as 0K.
The funny thing is that it is not complaining about Data Segment 1, which is
basically the same as Data Segment 2 - it just has fewer files.

Oh well.  Thank you again for your time.

Regards,

Daniel Suleski :->
TD, Mysticware Inc.
www.mysticware.com


"Ben Combee" <[EMAIL PROTECTED]> wrote in message
news:100848@;palm-dev-forum...
>
> At 20:47 2002-11-12 -0500, you wrote:
> >Hi everyone.
> >
> >I am trying to build a project that is giving me the following errors
when I
> >try to run it...
> >
> >"Link Error: __RuntimeModule__: Near data segment is bigger than 64K."
> >
> >The other error messages have to do with some of my functions not being
> >within range of a function it is calling.  I have handled those types of
> >errors before by simply moving the questionable files closer to each
other.
> >Anyway...
>
> This is a data segment error, not a code segment error.  This is caused by
> having too many global or static variables, having too many C++ virtual
> tables, having too many exception tables, or something like
> that.  Rearranging your code won't fix this, but taking a look at what
> files produce a lot of data (look in the data column), doing a disassemble
> on them, and seeing if you can reduce that size will.
>
> See my whitepaper at http://www.metrowerks.com/pdf/Expanded_Mode.pdf for
> some more information on one way to solve this, if your problems are due
to
> extensive C++ use.
>
> --
> Ben Combee <[EMAIL PROTECTED]>
> CodeWarrior for Palm OS technical lead
> Palm OS programming help @ www.palmoswerks.com
>
>
>



-- 
For information on using the Palm Developer Forums, or to unsubscribe, please see 
http://www.palmos.com/dev/support/forums/

Reply via email to