-The binaries of EdkShellBinPkg are generated with EDK-Shell 1.04 release and build with Edk Compatibility & BaseTools Package\r
-(r4631)\r
+The binaries of EdkShellBinPkg are generated with EDK-Shell 1.05 release and build with Edk Compatibility & BaseTools Package\r
+(r5782)\r
\r
The following steps can help to re-generate these binaries for customization:\r
-1. Check out EdkCompatibilityPkg (r4631) to a directory EdkCompatibilityPkg in workspace (svn https://edk2.tianocore.org/svn/edk2/trunk/edk2/EdkCompatibilityPkg). \r
-2. Update to the newest BaseTools package.\r
-2. Download EfiShell 1.04.zip from EDK Shell official release https://efi-shell.tianocore.org/servlets/ProjectDocumentList?folderID=52&expandFolder=52&folderID=45\r
-3. Unzip it to be a sub-directory in EdkCompatibilityPkg , i.e. c:\EdkII\EdkCompatibilityPkg\Shell\r
-4. Work around an issue in EdkCompatibilityPkg\Shell\ver\Ver.inf to split:\r
- [sources.ia32|x64]\r
- ia32\ver32.c\r
-\r
- to be:\r
- [sources.ia32]\r
- ia32\ver32.c\r
-\r
- [sources.x64]\r
- ia32\ver32.c\r
-\r
- since current build tools (r4631) do not support this syntax in EDK INF format.\r
-\r
-5. Under workspace directory (i.e. c:\EdkII), execute:\r
- build -a IA32 -a X64 -a IPF -p EdkShellBinPkg\GenBin\EdkShellPkg.dsc -t WINDDK3790x1830\r
- The use of WINDDK instead of MYTOOLS is due to the fact that EDK shell source 1.04 is not\r
- VS2005 clean.\r
-\r
+1. Check out EdkCompatibilityPkg (r5782) to $(WORKSPACE)\EdkCompatibilityPkg (svn https://edk2.tianocore.org/svn/edk2/trunk/edk2/EdkCompatibilityPkg).\r
+2. Check out EdkShellPkg(r5782) to $(WORKSPACE)\EdkShellPkg (svn https://efi-shell.tianocore.org/servlets/ProjectDocumentList?folderID=52&expandFolder=52&folderID=45).\r
+ 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
+3. Update to the newest BaseTools package. (r5782 or later)\r
+4. Apply a hot fix ShellHotFix.patch under EdkShellPkg directory.\r
+ 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
+ This patch will be integrated into the later official release.\r
+5. Under workspace directory (i.e. c:\EdkII), execute: build -a IA32 -a X64 -a IPF -p EdkShellPkg\EdkShellPkg.dsc\r
6. Copy the binaries from Build directory to this package. Typically the EFI binary\r
- of EdkCompatibility\Shell\$(INF_BASENAME).inf is generated at:\r
- Build\EdkShellPkg\DEBUG_WINDDK3790x1830\$(ARCH)\EdkCompatibility\Shell\$(INF_BASENAME)\OUTPUT\$(BASENAME).efi\r
+ of EdkShellPkg\Shell\$(INF_BASENAME).inf is generated at:\r
+ Build\EdkShellPkg\DEBUG_MYTOOLS\$(ARCH)\EdkShellPkg\Shell\$(INF_BASENAME)\OUTPUT\$(BASENAME).efi\r
For example:\r
- The x64 EFI image of EdkCompatibility\Shell\ver\ver.inf is generated at:\r
- Build\EdkShellPkg\DEBUG_WINDDK3790x1830\X64\EdkCompatibilityPkg\Shell\ver\Ver\OUTPUT\ver.efi\r
+ The x64 EFI image of EdkShellPkg\Shell\ver\ver.inf is generated at:\r
+ Build\EdkShellPkg\DEBUG_MYTOOLS\X64\EdkShellPkg\Shell\ver\Ver\OUTPUT\ver.efi\r
\r
Note: Other\Maintained\Application\Shell\Shell.inf corresponds to Minimum shell binaries.\r
Other\Maintained\Application\Shell\ShellFull.inf corresponds to Full Shell binaries.
\ No newline at end of file