![windows ce 6.0 os image windows ce 6.0 os image](https://www.msembedded.biz/fileadmin/_migrated/RTE/RTEmagicC_SILICA-Microsoft-Windows-CE60-scheme.jpg)
I am presenting the snapshot of the WEC 7 dependencies for you to have a look. And many dependencies did not crop up with the WCE 6.0 image that I built. The Standard Shell seemed to have the most dependencies. I had included the ActiveSync for my connectivity and debugging and Standard Shell for the base GUI and Desktop. There were 2 main components that were having a number of dependencies
![windows ce 6.0 os image windows ce 6.0 os image](https://slidetodoc.com/presentation_image_h/a6e2690e9c53715133a48d6ed6bab025/image-7.jpg)
#WINDOWS CE 6.0 OS IMAGE WINDOWS#
So checked the dependencies of individual components one by one for both Windows CE 6.0 and WEC 7.0 Yet… the size was never got that big for WinCE 6.0. Well that’s what we used to face with Windows CE 6.0 as well. DependenciesĪs you all know Windows CE has a lot of inter-related dependencies and components keep piling up as dependencies add up as a chain. How could the same set of features create a 300% increase? I started to explore and found a few things which I am sharing in this blog. Wow that was some 300% more of binary size… The “Release” Image size was around 25MB. Then I moved on to my WEC 7 development platform and built an exact replica of the features with WEC7 BSP for Alioth. A cool GUI based build in 8.5 MB without any effort to optimize it.Hmmm.Sounds good. I booted up the OS and checked to find everything working as expected. The “Release” Image size was around 8.5MB. I created an OSDesign with selected components (not exactly minimum) for a GUI based build, in my Alioth platform in CE 6.0. I was really seeing something drastically different in the image size when I compared the Windows CE 6.0 image of the Alioth platform and the Windows Embedded Compact 7.0 of Alioth. As I started to look into the differences, the first thing that struck me was the image size.