-The binaries of EdkShellBinPkg are generated with EDK-Shell 1.04 release and build with Edk Compatibility & BaseTools Package\r
-(r4631)\r
-\r
-The following steps are 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 the directory in EdkCompatibilityPkg , e.g. c:\EdkII\EdkCompatibilityPkg\Shell\r
-4. Workaround an issue in EdkCompatibilityPkg\Shell\ver\Ver.inf to spit:\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 (r4630) does not support this syntax in EDK inf.\r
-\r
-5. Under workspace directory, exectute:\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
-6. Copy the binaries from Build directory to this package. Typically the EFI binary\r
- of EdkCompatibility\Shell\$(INF_BASENAME).inf is generaged at:\r
- Build\EdkShellPkg\DEBUG_WINDDK3790x1830\$(ARCH)\EdkCompatibility\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
-\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
+The binaries of EdkShellBinPkg are generated with Efi-Shell-Dev-Snapshot-20091214.zip (plus a security hot-fix see EdkShellbinPkg\SecurityPatch.diff) and build with Edk Compatibility & BaseTools Package\r
+(r9623)\r
+\r
+The following steps can help to re-generate these binaries for customization:\r
+1. Check out EdkCompatibilityPkg (r9623) to $(WORKSPACE)\EdkCompatibilityPkg (svn https://edk2.tianocore.org/svn/edk2/trunk/edk2/EdkCompatibilityPkg).\r
+2. Check out EdkShellPkg(r9623) to $(WORKSPACE)\EdkShellPkg (svn https://edk2.tianocore.org/svn/edk2/trunk/edk2/EdkShellPkg).\r
+3a.Check out Edk Shell project source (r36) to $(WORKSPACE) (svn https://efi-shell.tianocore.org/svn/efi-shell/trunk/Shell). It is read-only and current revison (r36) is identical to Efi-Shell-Dev-Snapshot-20091214.zip. \r
+3b.Apply the security hot fix in EdkShellBinPkg\SecurityPatch.diff to patch in Shell\shellenv\exec.c\r
+4. Update to the newest BaseTools package. (r9623 or later)\r
+5. Under workspace directory (i.e. c:\EdkII), \r
+ To generate Minimum Shell, execute: "build -a IA32 -a X64 -a IPF -p EdkShellPkg\EdkShellPkg.dsc -m EdkShellPkg\Shell\Shell.inf" \r
+ To generate Full Shell, execute: "build -a IA32 -a X64 -a IPF -p EdkShellPkg\EdkShellPkg.dsc -m EdkShellPkg\Shell\ShellFull.inf" \r
+6. In EdkShellBinPkg\Bin, we only provides the binary files of those applications which haven't been contained in Minmum Shell but in Full Shell.\r
+ To generate them, execute: "build -a IA32 -a X64 -a IPF -p EdkShellPkg\EdkShellPkg.dsc -m EdkShellPkg\Xxx\Xxx.inf". Xxx means the corresponding module name.
\ No newline at end of file