]>
Commit | Line | Data |
---|---|---|
072d6116 | 1 | ============================================================================\r |
2 | OVERVIEW\r | |
3 | ============================================================================\r | |
a8cc4795 HT |
4 | The binaries of ShellBinPkg are generated with ShellPkg project and built with\r |
5 | BaseTools Package. The binaries are built with no debug information by building\r | |
6 | with "RELEASE" target. The EDKII revision 11595 was used for both.\r | |
072d6116 | 7 | \r |
8 | The following steps can help to re-generate these binaries for customization:\r | |
9 | 1. Check out EDK II to $(WORKSPACE) \r | |
a8cc4795 | 10 | (svn https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2).\r |
072d6116 | 11 | 2. Under $(WORKSPACE) directory (i.e. c:\EdkII),\r |
3c73ec6c | 12 | To generate Shell, execute: \r |
13 | "build -a IA32 -a X64 -p ShellPkg\ShellPkg.dsc -b RELEASE".\r | |
072d6116 | 14 | \r |
072d6116 | 15 | ============================================================================\r |
16 | HOW TO INCORPORATE THIS SHELL INTO NT32\r | |
17 | ============================================================================\r | |
18 | The instructions below are included as a sample and template on how a \r | |
19 | developer may integrate this code into an existing platform:\r | |
072d6116 | 20 | \r |
21 | 1. Update system PCDs to support this new module\r | |
22 | Update the PCD as follows using the Shell's PCD:\r | |
3c73ec6c | 23 | gEfiIntelFrameworkModulePkgTokenSpaceGuid.PcdShellFile|{ 0x83, 0xA5, \r |
24 | 0x04, 0x7C, 0x3E, 0x9E, 0x1C, 0x4F, 0xAD, 0x65, 0xE0, 0x52, 0x68, 0xD0, \r | |
25 | 0xB4, 0xD1 }\r | |
072d6116 | 26 | \r |
27 | 2. Remove the old shell from the NT32 Firmware list\r | |
28 | Remove the FILE APPLICATION section for the old shell.\r | |
29 | \r | |
30 | 3. Add this shell to the NT32 firmware list\r | |
31 | Add the Shell.INF to the end of the list of DXE modules.\r | |
32 | \r | |
33 | 4. Build NT32\r | |
34 | \r | |
35 | ============================================================================\r | |
36 | KNOWN LIMITATIONS\r | |
37 | ============================================================================\r | |
38 | 1. RM can delete current working directory via other map name.\r | |
39 | 2. DrvCfg is not functional.\r | |
40 | 3. ifConfig permanent settings are under investigation (may not function correctly)\r | |
41 | 4. Shell documentation is in development and forthcoming.\r | |
42 | \r | |
43 | ============================================================================\r |