Image Update Files

The component to package mapping file, .cpm.csv, defines the relationship between components and packages. The .cpm.csv file maps the component tags and files to packages. The .cpm.csv file is identical to the .csv files used in the multi-XIP build system.

Component to package mapping files specify in which package a module, file, or registry key belongs to.

The .cpm.csv file is also one of the inputs used by the Manifest Build Tool to generate the build side manifest, .bsm.xml, file. For more information, see Package Generation Process.

The following three files are merged:

• Microsoft modules are mapped by the /Public/%_TGTPROJ%/Oak/Files/%_TGTPROJ%.cpm.csv file
• OEM modules are mapped by the Oem.cpm.csv file, which is located in one or more of the following directories: /Platform/%_TGTPLAT%/Files/Cebase, /Platform/%_TGTPLAT%/Files/Smartfon, and /Platform/%_TGTPLAT%/Files/Wpc.
• /Public/Common/Oak/Files/Metadata.cpm.csv file

//这里是说wm会把上面三个.cp.csv文件merge成Cexipmodl.cpm.csv 因此如果我们在bsp中定义像

GWES.exe 在public下已经定义过的 makimg时候就会被提示重复定义。还有 buildpkg是不会重新进行merge的。

The final output file is Cexipmodl.cpm.csv merged.

You can define the .cpm.csv file using any one of the following syntax:

• Explicit file mapping

  <File name>,<Package name>

  Example: BubbleBreaker.exe,Games

  Use explicit mappings sparingly because this cannot be used to map registry entries.

• Component-based mapping

  <CE_MODULES_X>,<Package name>

  Example: APPS_MODULES_BUBBLEBREAKER,Games

  This mapping is based on the closest surrounding CESYSGEN tag. This type of mapping works for registry entries and .bib files.

  The optional <BOOTHIVE> modifier forces all registry keys into Boot.hv. This replaces the <DEFAULTREG> option from the Multi-XIP cpm.csv files.

• XIPREGION tags

  XIPREGION tags behave the same way as CESYSGEN tags. You need to surround the group of .bib or .reg file entries that you wish to map with ";@XIPREGION IF XXX" and ";@XIPREGION ENDIF XXX". You can replace XXX with any name you want, there is no strict naming convention.

  Project.bib, Project.reg, and sometimes Platform.bib do not get CEFiltered so you cannot use CESYSGEN tags. In this case, use XIPREGION tags instead.

In the Wpc.cpm.csv file, CE_MODULES_RAMFMD should ALWAYS be set to IGNORE. There should be no IMG flag dependencies in the base files. If OEMs want to include CE_MODULES_RAMFMD in their device, OEMs should add the line CE_MODULES_RAMFMD,OEMDRIVERS to the Oem.cpm.csv file.