sravan/system76-edk2
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

add required 'profiles.txt' file to the binary releases.

Browse Source 
add 'minimal' version of the shell (without any profiles).
update to current ShellPkg tip version.


git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@11667 6f19259b-4bc3-4df7-8a09-765794883524
This commit is contained in:
jcarsey
2011-05-16 22:20:11 +00:00
parent 82571fb5d1
commit 2f4f828a23
10 changed files with 53 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
ShellBinPkg/ReadMe.txt
View File

@@ -1,16 +1,19 @@
============================================================================
OVERVIEW
============================================================================
The binaries of ShellBinPkg are generated with ShellPkg project and built with
BaseTools Package. The binaries are built with no debug information by building
with "RELEASE" target. The EDKII revision 11595 was used for both.
The binaries of ShellBinPkg are generated with ShellPkg project and built with
BaseTools Package (r11666). The binaries are built with no debug information
by building with "RELEASE" target.
The following steps can help to re-generate these binaries for customization:
1. Check out EDK II to $(WORKSPACE)
(svn https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2).
(svn https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2).
2. Under $(WORKSPACE) directory (i.e. c:\EdkII),
To generate Shell, execute:
"build -a IA32 -a X64 -p ShellPkg\ShellPkg.dsc -b RELEASE".
To generate Shell, execute:
"build -a IA32 -a X64 -p ShellPkg\ShellPkg.dsc -b RELEASE"
To generate Minimal Shell, execute:
"build -a IA32 -a X64 -p ShellPkg\ShellPkg.dsc -b RELEASE -D NO_SHELL_PROFILES"
============================================================================
HOW TO INCORPORATE THIS SHELL INTO NT32
@@ -36,7 +39,7 @@ developer may integrate this code into an existing platform:
KNOWN LIMITATIONS
============================================================================
1. RM can delete current working directory via other map name.
2. DrvCfg is not functional.
2. DrvCfg does not overlap boot manager functionality.
3. ifConfig permanent settings are under investigation (may not function correctly)
4. Shell documentation is in development and forthcoming.