]>
Commit | Line | Data |
---|---|---|
1 | The binaries of EdkShellBinPkg are generated with EDK-Shell 1.05 release and build with Edk Compatibility & BaseTools Package\r | |
2 | (r5782)\r | |
3 | \r | |
4 | The following steps can help to re-generate these binaries for customization:\r | |
5 | 1. Check out EdkCompatibilityPkg (r5782) to $(WORKSPACE)\EdkCompatibilityPkg (svn https://edk2.tianocore.org/svn/edk2/trunk/edk2/EdkCompatibilityPkg).\r | |
6 | 2. Check out EdkShellPkg(r5782) to $(WORKSPACE)\EdkShellPkg (svn https://edk2.tianocore.org/svn/edk2/trunk/edk2/EdkShellPkg).\r | |
7 | This package has an SVN extern directory from EDK Shell project. It is read-only and current revison (r30) is identical to EDK shell 1.05 release. \r | |
8 | 3. Update to the newest BaseTools package. (r5782 or later)\r | |
9 | 4. Apply a hot fix ShellHotFix.patch under EdkShellPkg directory.\r | |
10 | Add a Shell Hot Fix patch to solve RFC3066 language compatibility issue and "CHAR8" compatibility issue in DmpStore, Edit command and shell script execution.\r | |
11 | This patch will be integrated into the later official release.\r | |
12 | 5. Under workspace directory (i.e. c:\EdkII), execute: build -a IA32 -a X64 -a IPF -p EdkShellPkg\EdkShellPkg.dsc\r | |
13 | 6. Copy the binaries from Build directory to this package. Typically the EFI binary\r | |
14 | of EdkShellPkg\Shell\$(INF_BASENAME).inf is generated at:\r | |
15 | Build\EdkShellPkg\DEBUG_MYTOOLS\$(ARCH)\EdkShellPkg\Shell\$(INF_BASENAME)\OUTPUT\$(BASENAME).efi\r | |
16 | For example:\r | |
17 | The x64 EFI image of EdkShellPkg\Shell\ver\ver.inf is generated at:\r | |
18 | Build\EdkShellPkg\DEBUG_MYTOOLS\X64\EdkShellPkg\Shell\ver\Ver\OUTPUT\ver.efi\r | |
19 | \r | |
20 | Note: Other\Maintained\Application\Shell\Shell.inf corresponds to Minimum shell binaries.\r | |
21 | Other\Maintained\Application\Shell\ShellFull.inf corresponds to Full Shell binaries. |