[mirror_edk2.git] / ShellBinPkg / ReadMe.txt

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