Produce all the PciIo & Dpath protocol for all the pci devices under the current...
[mirror_edk2.git] / EdkShellBinPkg / ReadMe.txt
970e4d2b 1The binaries of EdkShellBinPkg are generated with EDK-Shell 1.04 release and build with Edk Compatibility & BaseTools Package\r
abe7b4c6 3\r
4The following steps are can help to re-generate these binaries for customization:\r
970e4d2b 51. Check out EdkCompatibilityPkg (r4631) to a directory EdkCompatibilityPkg in workspace (svn \r
62. Update to the newest BaseTools package.\r
72. Download EfiShell from EDK Shell official release\r
83. Unzip it to the directory in EdkCompatibilityPkg , e.g. c:\EdkII\EdkCompatibilityPkg\Shell\r
94. Workaround an issue in EdkCompatibilityPkg\Shell\ver\Ver.inf to spit:\r
10 [sources.ia32|x64]\r
11 ia32\ver32.c\r
13 to be:\r
14 [sources.ia32]\r
15 ia32\ver32.c\r
17 [sources.x64]\r
18 ia32\ver32.c\r
20 since current build tools (r4630) does not support this syntax in EDK inf.\r
225. Under workspace directory, exectute:\r
23 build -a IA32 -a X64 -a IPF -p EdkShellBinPkg\GenBin\EdkShellPkg.dsc -t WINDDK3790x1830\r
24 The use of WINDDK instead of MYTOOLS is due to the fact that EDK shell source 1.04 is not\r
25 VS2005 clean.\r
276. Copy the binaries from Build directory to this package. Typically the EFI binary\r
28 of EdkCompatibility\Shell\$(INF_BASENAME).inf is generaged at:\r
29 Build\EdkShellPkg\DEBUG_WINDDK3790x1830\$(ARCH)\EdkCompatibility\Shell\$(INF_BASENAME)\OUTPUT\$(BASENAME).efi\r
30 for example:\r
31 The x64 EFI image of EdkCompatibility\Shell\ver\ver.inf is generated at:\r
32 Build\EdkShellPkg\DEBUG_WINDDK3790x1830\X64\EdkCompatibilityPkg\Shell\ver\Ver\OUTPUT\ver.efi\r
abe7b4c6 33\r
34Note: Other\Maintained\Application\Shell\Shell.inf corresponds to Minimum shell binaries.\r
35 Other\Maintained\Application\Shell\ShellFull.inf corresponds to Full Shell binaries.