\r
Pre-requisites:\r
* Build environment capable of build the edk2 MdeModulePkg.\r
-* A properly configured ASL compiler\r
- * Intel ASL compiler: Available from http://www.acpica.org\r
- or\r
- * Microsoft ASL compiler: Available from http://www.acpi.info\r
+* A properly configured ASL compiler:\r
+ - Intel ASL compiler: Available from http://www.acpica.org\r
+ - Microsoft ASL compiler: Available from http://www.acpi.info\r
\r
Update Conf/target.txt ACTIVE_PLATFORM for OVMF:\r
PEI arch DXE arch UEFI interfaces\r
depend on how your build is configured. You can expect to find\r
these binary outputs:\r
* OVMF.FD\r
- * Please note! This filename has changed. Older releases used OVMF.Fv.\r
-* CirrusLogic5446.rom\r
+ - Please note! This filename has changed. Older releases used OVMF.Fv.\r
+* OvmfVideo.rom\r
\r
More information on building OVMF can be found at:\r
\r
\r
* QEMU 0.9.1 or later is required.\r
* Either copy, rename or symlink OVMF.FD => bios.bin\r
-* Either copy, rename or symlink CirrusLogic5446.rom => vgabios-cirrus.bin\r
* Be sure to use qemu-system-x86_64, if you are using and X64 firmware.\r
(qemu-system-x86_64 works for the IA32 firmware as well, of course.)\r
* Use the QEMU -L parameter to specify the directory where the bios.bin\r
- and vgabios-cirrus.bin files are located.\r
+ file is located.\r
* Optionally you can use the QEMU -serial command to capture the\r
OVMF debug messages. For example: -serial file:serial.log\r
* The EFI shell is built into OVMF builds at this time, so it should\r
\r
=== Build Scripts ===\r
\r
-On environments with the bash shell you can use OvmfPkg/build32.sh and\r
-OvmfPkg/build64.sh to simplify building and running OVMF.\r
+On systems with the bash shell you can use OvmfPkg/build.sh to simplify\r
+building and running OVMF.\r
\r
So, for example, to build + run OVMF X64:\r
-$ OvmfPkg/build64.sh\r
-$ OvmfPkg/build64.sh qemu\r
+$ OvmfPkg/build.sh -a X64\r
+$ OvmfPkg/build.sh -a X64 qemu\r
\r
And to run a 64-bit UEFI bootable ISO image:\r
-$ OvmfPkg/build64.sh qemu -cdrom /path/to/disk-image.iso\r
+$ OvmfPkg/build.sh -a X64 qemu -cdrom /path/to/disk-image.iso\r
+\r
+To build a 32-bit OVMF without debug serial messages using GCC 4.5:\r
+$ OvmfPkg/build.sh -a IA32 -b RELEASE -t GCC45\r
\r
=== Network Support ===\r
\r
-net nic,model=e1000,addr=3 -net nic,model=e1000,addr=4\r
-net user,restrict=yes -net user,dhcpstart=10.0.2.10\r
\r
+=== UNIXGCC Debug ===\r
+\r
+If you build with the UNIXGCC toolchain, then debugging will be disabled\r
+due to larger image sizes being produced by the UNIXGCC toolchain. The\r
+first choice recommendation is to use GCC44 or newer instead.\r
+\r
+If you must use UNIXGCC, then you can override the build options for\r
+particular libraries and modules in the .dsc to re-enable debugging\r
+selectively. For example:\r
+ [Components]\r
+ OvmfPkg/Library/PlatformBdsLib/PlatformBdsLib.inf {\r
+ <BuildOptions>\r
+ GCC:*_*_*_CC_FLAGS = -UMDEPKG_NDEBUG\r
+ }\r
+ IntelFrameworkModulePkg/Universal/BdsDxe/BdsDxe.inf {\r
+ <BuildOptions>\r
+ GCC:*_*_*_CC_FLAGS = -UMDEPKG_NDEBUG\r
+ }\r
+\r