summaryrefslogtreecommitdiffstats
path: root/OvmfPkg/README
diff options
context:
space:
mode:
authorjljusten <jljusten@6f19259b-4bc3-4df7-8a09-765794883524>2011-01-09 03:50:21 +0000
committerjljusten <jljusten@6f19259b-4bc3-4df7-8a09-765794883524>2011-01-09 03:50:21 +0000
commit66325870afafef6bf221fc3cc214f208b281652b (patch)
tree29aa34e32ce1b011d802b249f69e965d4980ecd4 /OvmfPkg/README
parentaf072124e4f2f004f2200d765a72efb7c97c9aec (diff)
downloadedk2-66325870afafef6bf221fc3cc214f208b281652b.tar.gz
edk2-66325870afafef6bf221fc3cc214f208b281652b.tar.bz2
edk2-66325870afafef6bf221fc3cc214f208b281652b.zip
OvmfPkg/build.sh: Add features and replace build32/64.sh
Add a single build.sh to replace build32.sh & build64.sh. The script watches for various parameters: -a: allows selecting IA32 or X64 (default) -b: allows selecting RELEASE or DEBUG (default) -t: allows selecting the toolchain When running qemu, the script doesn't always add -hda now. If the user provides a disk parameter (for example, -fda, -hda or -cdrom), then -hda will not be added to the qemu command line. git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@11238 6f19259b-4bc3-4df7-8a09-765794883524
Diffstat (limited to 'OvmfPkg/README')
-rw-r--r--OvmfPkg/README22
1 files changed, 12 insertions, 10 deletions
diff --git a/OvmfPkg/README b/OvmfPkg/README
index c37bfb6316..e4a4b1f5a1 100644
--- a/OvmfPkg/README
+++ b/OvmfPkg/README
@@ -28,10 +28,9 @@ Current capabilities:
Pre-requisites:
* Build environment capable of build the edk2 MdeModulePkg.
-* A properly configured ASL compiler
- * Intel ASL compiler: Available from http://www.acpica.org
- or
- * Microsoft ASL compiler: Available from http://www.acpi.info
+* A properly configured ASL compiler:
+ - Intel ASL compiler: Available from http://www.acpica.org
+ - Microsoft ASL compiler: Available from http://www.acpi.info
Update Conf/target.txt ACTIVE_PLATFORM for OVMF:
PEI arch DXE arch UEFI interfaces
@@ -50,7 +49,7 @@ under the $WORKSPACE/Build/*/*/FV directory. The actual path will
depend on how your build is configured. You can expect to find
these binary outputs:
* OVMF.FD
- * Please note! This filename has changed. Older releases used OVMF.Fv.
+ - Please note! This filename has changed. Older releases used OVMF.Fv.
* CirrusLogic5446.rom
More information on building OVMF can be found at:
@@ -76,15 +75,18 @@ http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=How_to_build_OVM
=== Build Scripts ===
-On environments with the bash shell you can use OvmfPkg/build32.sh and
-OvmfPkg/build64.sh to simplify building and running OVMF.
+On systems with the bash shell you can use OvmfPkg/build.sh to simplify
+building and running OVMF.
So, for example, to build + run OVMF X64:
-$ OvmfPkg/build64.sh
-$ OvmfPkg/build64.sh qemu
+$ OvmfPkg/build.sh -a X64
+$ OvmfPkg/build.sh -a X64 qemu
And to run a 64-bit UEFI bootable ISO image:
-$ OvmfPkg/build64.sh qemu -cdrom /path/to/disk-image.iso
+$ OvmfPkg/build.sh -a X64 qemu -cdrom /path/to/disk-image.iso
+
+To build a 32-bit OVMF without debug serial messages using GCC 4.5:
+$ OvmfPkg/build.sh -a IA32 -b RELEASE -t GCC45
=== Network Support ===