Minimizing executable memory usage

"Byron Guernsey" <byron-s/[email protected]> Thu, 18 Aug 2005 11:30:02 -0400
Newsgroups gmane.comp.windows.ce.freeware
Message-ID <001f01c5a409$b3c0b8e0$0a00a8c0@antigravity>
Does anyone have some tips or pointers to information on keeping the running 
executable size small on WinCE/PocketPC executables?  Any tips on 
identifying where the memory usage is occurring?

I'm using the evc4 toolset for compiling and I suspect that there are ways 
reduce the executable bloat by avoiding certain API's or linkages.  I've had 
a lot more experience with Linux and Windows C/C++ programming, so I'm not 
familiar with all the size caveats of the CE libraries.

I have an executable that has a running footprint of about 8 megabytes.  The 
code compiles into either a CE binary or a Windows win32 executable with 
Visual Studio C++ 6, so I've profiled the memory usage with BoundsChecker 
and I'm certainly not seeing dynamic allocations made by the code that come 
anywhere close to that 8 meg.  So my assumption is that I'm getting code 
bloat based on my design or based on linkages.  I just don't know how I 
approach reducing that.

Any tips would be greatly appreciated.  I have had a hard time finding 
information on the web about optimizing code for small executable size. 
This code is intended to be ported to the SmartPhone Edition of CE 
eventually and things get a bit tighter in terms of available memory there.

Thanks,
Byron




------------------------ Yahoo! Groups Sponsor --------------------~--> 
<font face=arial size=-1><a href="http://us.ard.yahoo.com/SIG=12hbsgprf/M=362131.6882499.7825260.1510227/D=groups/S=1707281942:TM/Y=YAHOO/EXP=1124386236/A=2889191/R=0/SIG=10r90krvo/*http://www.thebeehive.org
">Get Bzzzy! (real tools to help you find a job) Welcome to the Sweet Life - brought to you by One Economy</a>.</font>
--------------------------------------------------------------------~->