public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Rebecca Cran <rebecca@bluestop.org>
To: edk2-devel@lists.01.org
Subject: Re: Newbie: Getting Ovmf built
Date: Sat, 24 Nov 2018 22:59:32 -0700	[thread overview]
Message-ID: <15314690.vxEf1mJfsr@photon.int.bluestop.org> (raw)
In-Reply-To: <e6fbddcd-af70-793f-459b-9a9a3e3f09b3@linux.intel.com>

On Friday, 23 November 2018 17:40:15 MST stephano wrote:

> We have a set of simple instructions for folks building on standard
> Linux distros. Please have a look at this page:
> 
> https://github.com/tianocore/tianocore.github.io/wiki/Common-instructions
> 
> Note: Be sure the TARGET_ARCH is set correctly. (E.g. TARGET_ARCH = x64)

If you just want to build OVMF, there's a simpler way. After cloning, and 
assuming you're running bash, just:

cd edk2
. ./edksetup.sh
./OvmfPkg/build.sh -a X64 -t GCC5 -b RELEASE

If the build succeeds you'll end up with Build/OvmfX64/RELEASE_GCC5/FV/OVMF.fd 
which is the 'BIOS' image to pass to Qemu, e.g.:

qemu-system-x86_64 -m 4g -drive if=pflash,format=raw,readonly,file=Build/
OvmfX64/RELEASE_GCC5/FV/OVMF.fd \
        -nodefaults \
        -drive format=raw,file=/hda.img -monitor stdio \
        -vga std -sdl -drive format=raw,file=Install.iso

-- 
Rebecca




  parent reply	other threads:[~2018-11-25  5:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-23 22:44 Newbie: Getting Ovmf built Peter Wiehe
2018-11-24  0:40 ` stephano
2018-11-24 17:23   ` Peter Wiehe
2018-11-24 17:57     ` stephano
2018-11-24 18:03       ` Peter Wiehe
2018-11-24 19:45         ` Andrew Fish
2018-11-24 19:46           ` Peter Wiehe
2018-11-24 20:44             ` Andrew Fish
2018-11-26 14:09     ` Gao, Liming
2018-11-25  5:59   ` Rebecca Cran [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-11-24 21:18 Peter Wiehe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=15314690.vxEf1mJfsr@photon.int.bluestop.org \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox