In Windows Embedded Compact 7 and earlier versions, the build of the runtime image is processed by various batch files and msbuild files. When it comes to customize the build process, the first idea that come to your mind is to modify those files in order to change their original behavior. But this implies that the new behaving will have an impact on all the OSdesign that you will build.
If you look in details on the build process, you will identify that alternative batch files can be launched prior and after make image build phases.
The bach file list is the following, defined in the order they will be executed :
- PreMakeImg.proj : project file launched prior to the make image step
- PreFmergeBib.bat : launched prior merging the bib files into ce.bib
- PostFmergeBib.bat : launched after ce.bib creation
- PreFmergeReg.bat : launched prior merging the reg files into reginit.ini
- PostFmergeReg.bat : launched after reginit.ini creation but before compression
- PreFmergeDb.bat : launched prior merging the db files into initdb.ini
- PostFmergeDb.bat : launched after initdb.ini creation
- PreFmergeObj.bat : launched prior merging the dat files into initobj.dat
- PostFmergeObj.bat : launched after initobj.dat creation
- PreRomImage.proj : project file launched prior to the rom image step
- PostRomImage.bat : launched after the nk.bin creation
- PostMakeImg.bat : launched after the make image step
You can now customize the build steps by developing your own batch files and storing them into the FILES folder of your BSP.
The customization can be a simple modification of the registry files by adding time stamp information inside the runtime image, or could be more complex like removing unused files from the bib file, like wav files and sample pictures added by default, with the goal of reducing the size of the NK.bin.
- Nicolas
No comments:
Post a Comment