X-Git-Url: https://git.proxmox.com/?a=blobdiff_plain;f=OvmfPkg%2FREADME;h=51041a0551ec696b2cf17cb4b341370b827878d6;hb=492e34a59041a04f92958139fee6ee4110a8cbe4;hp=c37bfb6316f0cb82e48d7c0ac5c8f9f88533e2ba;hpb=aed8e2ec4e92350341e4e34697471b52fa4eb4c1;p=mirror_edk2.git

diff --git a/OvmfPkg/README b/OvmfPkg/README
index c37bfb6316..51041a0551 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,8 +49,8 @@ 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.
-* CirrusLogic5446.rom
+  - Please note!  This filename has changed.  Older releases used OVMF.Fv.
+* OvmfVideo.rom
 
 More information on building OVMF can be found at:
 
@@ -61,11 +60,10 @@ http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=How_to_build_OVM
 
 * QEMU 0.9.1 or later is required.
 * Either copy, rename or symlink OVMF.FD => bios.bin
-* Either copy, rename or symlink CirrusLogic5446.rom => vgabios-cirrus.bin
 * Be sure to use qemu-system-x86_64, if you are using and X64 firmware.
   (qemu-system-x86_64 works for the IA32 firmware as well, of course.)
 * Use the QEMU -L parameter to specify the directory where the bios.bin
-  and vgabios-cirrus.bin files are located.
+  file is located.
 * Optionally you can use the QEMU -serial command to capture the
   OVMF debug messages.  For example: -serial file:serial.log
 * The EFI shell is built into OVMF builds at this time, so it should
@@ -76,15 +74,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 ===
 
@@ -114,3 +115,22 @@ To add network drivers to OVMF:
     -net nic,model=e1000,addr=3 -net nic,model=e1000,addr=4
     -net user,restrict=yes -net user,dhcpstart=10.0.2.10
 
+=== UNIXGCC Debug ===
+
+If you build with the UNIXGCC toolchain, then debugging will be disabled
+due to larger image sizes being produced by the UNIXGCC toolchain. The
+first choice recommendation is to use GCC44 or newer instead.
+
+If you must use UNIXGCC, then you can override the build options for
+particular libraries and modules in the .dsc to re-enable debugging
+selectively. For example:
+  [Components]
+  OvmfPkg/Library/PlatformBdsLib/PlatformBdsLib.inf {
+    <BuildOptions>
+      GCC:*_*_*_CC_FLAGS             = -UMDEPKG_NDEBUG
+  }
+  IntelFrameworkModulePkg/Universal/BdsDxe/BdsDxe.inf {
+    <BuildOptions>
+      GCC:*_*_*_CC_FLAGS             = -UMDEPKG_NDEBUG
+  }
+