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