Dean
Thu May 08 08:12:48 PDT 2008
For starters, make sure you base your OS Design on a custom device, and only
pull in the components you need. Fonts come in when you have mingdi in your
build, and mingdi comes in when various other components are selected. The
best way to see these dependencies is to look in the batch files that
control dependencies (\PUBLIC\CEBASE\OAK\MISC, in this case winceos.bat).
For finer granularity, you can set the _DEPTREES environment variable to
only include the OS trees you're interested in. That will prevent the
dependency checking from looking at undesired trees at all, and eliminate
those bib files completely (doesn't work for common.bib, obviously).
The last step is to do a manual filtering step on the bib files before
makeimg. That is brute force, but if you need to you can. My guess is in
the vast majority of cases the first step is sufficient. Most folks start
with something like Enterprise Webpad and wonder why it is so large :)
--
Dean Ramsier - eMVP
BSQUARE Corporation
<peach.voser@gmx.ch> wrote in message
news:9e951729-c84a-4ed0-99dc-4d8fa25da069@l64g2000hse.googlegroups.com...
> Hi,
>
> I would like to get rid of many unneeded components for a headless
> device. However, I cannot uncheck many catalog items because the
> Platform Builder thinks it is needed. For example: how can I get rid
> of the Tahoma fonts? Is there any method for this or do I have to
> apply brute force such as modifying common.bib?
>
> Thank you,
> Peter