EDK II Module Writer's Guide - Intel

3.7.5.7 Example Build HelloWorldBuild –p MdeModulePkg/MdeModulePkg.dsc –mMdeModulePkg/Application/HelloWorld/HelloWorld.inf –a IA32 –b DEBUG –tMYTOOLSHelloWorld.efi will be generated in DEBUG directory:$(WORKSAPCE)/Build/MdeModulePkg/DEBUG_MYTOOLS/IA32/MdeModulePkg/Application/HelloWorld/HelloWorld/DEBUG, OUTPUTIn the build DEBUG directory the following files are created: the EFI image,intermediate files, AutoGen.h/.c and Module.map file.AutoGen.h/.c files are generated for each module by the EDK II build tool based onthe required module information. They declare the dependent PCDs, Guid Values andinclude module entry point related function. Those AutoGen functions are referred inthe ModuleEntryPoint library instance. For each module, the entry point function fistcalls AutoGen code, then enters into module functions.Module.map is generated by a compiler tool to list all functions and their relativeaddresses in this module. They can be used to locate the module function address atrun time.3.7.6 Build EFI Option Rom imageAn EFI Option Rom image is a standard EFI image. It can be built by the build modulecommand mentioned in the above section. The only difference is that its INF includesthe related PCI option in [Defines] section. When PCI option is set in module INF, thismodule will be built to EFI and Option Rom image both. In build DEBUG directory,ModuleName.efi and ModuleName.rom will be generated.The following example contains all PCI options required to create EFI option romimage.43