From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Gerd Hoffmann" <kraxel@redhat.com>
Subject: [PULL 1/5] roms/efi: clean up edk2 build config
Date: Wed, 20 Mar 2024 08:08:44 +0100 [thread overview]
Message-ID: <20240320070851.18933-2-kraxel@redhat.com> (raw)
In-Reply-To: <20240320070851.18933-1-kraxel@redhat.com>
Needed to avoid stale toolchain configurations breaking firmware builds.
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Message-ID: <20240314115307.628118-2-kraxel@redhat.com>
---
roms/Makefile | 1 +
1 file changed, 1 insertion(+)
diff --git a/roms/Makefile b/roms/Makefile
index 8e5d8d26a9a0..edc234a0e886 100644
--- a/roms/Makefile
+++ b/roms/Makefile
@@ -187,6 +187,7 @@ clean:
rm -rf seabios/.config seabios/out seabios/builds
$(MAKE) -C ipxe/src veryclean
$(MAKE) -C edk2/BaseTools clean
+ rm -rf edk2/Conf/{.cache,BuildEnv.sh,build_rule.txt,target.txt,tools_def.txt}
$(MAKE) -C SLOF clean
rm -rf u-boot/build-e500
$(MAKE) -C u-boot-sam460ex distclean
--
2.44.0
next prev parent reply other threads:[~2024-03-20 7:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 7:08 [PULL 0/5] Edk2 20240320 patches Gerd Hoffmann
2024-03-20 7:08 ` Gerd Hoffmann [this message]
2024-03-20 7:08 ` [PULL 2/5] roms/efi: drop workaround for edk2-stable202308 Gerd Hoffmann
2024-03-20 7:08 ` [PULL 3/5] roms/efi: exclude efi shell from secure boot builds Gerd Hoffmann
2024-03-20 7:08 ` [PULL 4/5] roms/efi: use pure 64-bit build for edk2-x86_64-secure-code.fd Gerd Hoffmann
2024-03-20 7:08 ` [PULL 5/5] update edk2 binaries for arm, risc-v and x86 secure boot Gerd Hoffmann
2024-03-20 16:58 ` [PULL 0/5] Edk2 20240320 patches Peter Maydell
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-all 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=20240320070851.18933-2-kraxel@redhat.com \
--to=kraxel@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).