summaryrefslogtreecommitdiffstats
path: root/CryptoPkg/Library
diff options
context:
space:
mode:
authorMike Beaton <mjsbeaton@gmail.com>2023-09-06 10:37:16 +0100
committermergify[bot] <37929162+mergify[bot]@users.noreply.github.com>2023-09-06 11:09:24 +0000
commit4d196352f35ac516b477e568265b4e537b0283d8 (patch)
treeed831f5d16efa90f0d027b9955893f21331df08a /CryptoPkg/Library
parent9b3d4f28f03a6b709736c67884305e33c8f16c78 (diff)
downloadedk2-4d196352f35ac516b477e568265b4e537b0283d8.tar.gz
edk2-4d196352f35ac516b477e568265b4e537b0283d8.tar.bz2
edk2-4d196352f35ac516b477e568265b4e537b0283d8.zip
OvmfPkg: Revert "Update build.sh to allow building OVMF then running QEMU"
This reverts commit 173a7a7daaad560cd69e1000faca1d2b91774c46 Fixes https://bugzilla.tianocore.org/show_bug.cgi?id=4528 The build.sh qemu option starts the correct qemu executable for the selected architecture (build.sh -a option, or implicit) and uses the correct previously built OVMF image for the selected architecture and build target (build.sh -b option, or implicit). With this revert, the above step will fail if there is no matching previously built OVMF image. This is advantageous over rebuilding each time the build.sh qemu option is used (as in the reverted commit), because it provides a quick way to run a just-built OVMF image in place, while: a) Starting immediately (saving the time required for a rebuild on each usage, if the VM is started multiple times) b) Preserving the NVRAM contents between multiple runs (i.e. until the image is next rebuilt) Signed-off-by: Mike Beaton <mjsbeaton@gmail.com>
Diffstat (limited to 'CryptoPkg/Library')
0 files changed, 0 insertions, 0 deletions