1============================================================================
2                                 OVERVIEW
3============================================================================
4The binaries of ShellBinPkg are generated with ShellPkg project and built with
5BaseTools Package (git version: d2fc7711136a13ea3ea8e00de6d9651507b8ed50). The
6binaries are built with no debug information by building with "RELEASE" target.
7
8To generate Full Shell, execute:
9  "build -a IA32 -a X64 -p ShellPkg\ShellPkg.dsc -b RELEASE"
10To generate Minimal Shell, execute:
11  "build -a IA32 -a X64 -p ShellPkg\ShellPkg.dsc -b RELEASE -D NO_SHELL_PROFILES"
12
13============================================================================
14                    HOW TO INCORPORATE THIS SHELL INTO NT32
15============================================================================
16The instructions below are included as a sample and template on how a
17developer may integrate this code into an existing platform:
18
191. Update system PCDs to support this new module
20   Update the PCD as follows using the Shell's PCD:
21   gEfiIntelFrameworkModulePkgTokenSpaceGuid.PcdShellFile|{ 0x83, 0xA5,
22    0x04, 0x7C, 0x3E, 0x9E, 0x1C, 0x4F, 0xAD, 0x65, 0xE0, 0x52, 0x68, 0xD0,
23    0xB4, 0xD1 }
24
252. Remove the old shell from the NT32 Firmware list
26   Remove the FILE APPLICATION section for the old shell.
27
283. Add this shell to the NT32 firmware list
29   Add the Shell.INF to the end of the list of DXE modules.
30
314. Build NT32
32
33============================================================================
34                          KNOWN LIMITATIONS
35============================================================================
361. RM can delete current working directory via other map name.
372. DrvCfg does not overlap boot manager functionality.
383. Shell documentation is in development and forthcoming.
39
40============================================================================
41