============================================================================\r
OVERVIEW\r
============================================================================\r
-The binaries of ShellBinPkg are generated with ShellPkg project and built with \r
-BaseTools Package (r13224). The binaries are built with no debug information \r
-by building with "RELEASE" target.\r
+The binaries of ShellBinPkg are generated with ShellPkg project and built with\r
+BaseTools Package (git version: d2fc7711136a13ea3ea8e00de6d9651507b8ed50). The\r
+binaries are built with no debug information by building with "RELEASE" target.\r
\r
-The following steps can help to re-generate these binaries for customization:\r
-1. Check out EDK II to $(WORKSPACE) \r
-(svn https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2).\r
-\r
-2. Under $(WORKSPACE) directory (i.e. c:\EdkII),\r
- To generate Shell, execute:\r
- "build -a IA32 -a X64 -p ShellPkg\ShellPkg.dsc -b RELEASE"\r
- To generate Minimal Shell, execute:\r
- "build -a IA32 -a X64 -p ShellPkg\ShellPkg.dsc -b RELEASE -D NO_SHELL_PROFILES"\r
+To generate Full Shell, execute:\r
+ "build -a IA32 -a X64 -p ShellPkg\ShellPkg.dsc -b RELEASE"\r
+To generate Minimal Shell, execute:\r
+ "build -a IA32 -a X64 -p ShellPkg\ShellPkg.dsc -b RELEASE -D NO_SHELL_PROFILES"\r
\r
============================================================================\r
HOW TO INCORPORATE THIS SHELL INTO NT32\r
1. RM can delete current working directory via other map name.\r
2. DrvCfg does not overlap boot manager functionality.\r
3. Shell documentation is in development and forthcoming.\r
-4. ARM binaries are based on revision 13646. It is expected the binaries to\r
-sync with the other architectures next time they are rebuilt.\r
\r
============================================================================\r