Quote:
Originally Posted by schettj
I'll give it a shot.
The question is, which size? The size on disk for any OEM is knowable. The size that OEM will take in rom is not, since the ROM itself is compressed pretty heavily during build. So, for example, my current rom selections take a bit more then 100MB on disk just before they are churned into a rom image, and then (after much crunching) they end up wedged into the 60MB or so for the rom. You could say that the size used in rom is 3/5ths of the disk size, but you'd be wrong more often then not.
|
that's actually the easy part of it
To do it right, you need incremental building...which fundamentally is a different architecture. In the short run, I'm making a solution that will approximate the in ROM size, but won't be exact...so if you try to fill every last little byte, it may take you a couple iterations, but you'll have a fair indication of when you're near the edge.