From: "Rebecca Cran" <rebecca@bsdio.com>
To: devel@edk2.groups.io, Liming Gao <gaoliming@byosoft.com.cn>,
Bob Feng <bob.c.feng@intel.com>,
Yuwei Chen <yuwei.chen@intel.com>
Cc: Rebecca Cran <rebecca@bsdio.com>
Subject: [edk2-stable202305 PATCH 0/4] BaseTools: Fix CLANGDWARF HII resource rules and paths
Date: Tue, 9 May 2023 17:53:33 -0600 [thread overview]
Message-ID: <20230509235337.1815842-1-rebecca@bsdio.com> (raw)
Fix a few issues with the CLANGDWARF toolchain that was causing OVMF to
assert on boot due to the HII resources not being embedded into
HttpDynamicCommand, TftpDynamicCommand and
LinuxInitrdDynamicShellCommand.
Rebecca Cran (4):
BaseTools: Remove BUILDRULEFAMILY from CLANGDWARF in
tools_def.template
BaseTools: Set the CLANGDWARF OBJCOPY path in tools_def.template
BaseTools: Set CLANGDWARF RC path to llvm-objcopy in
tools_def.template
BaseTools: Remove the CLANGCC build rule for
Hii-Binary-Package.UEFI_HII
BaseTools/Conf/build_rule.template | 2 +-
BaseTools/Conf/tools_def.template | 14 +++++++++-----
2 files changed, 10 insertions(+), 6 deletions(-)
--
2.39.2
next reply other threads:[~2023-05-09 23:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 23:53 Rebecca Cran [this message]
2023-05-09 23:53 ` [edk2-stable202305 PATCH 1/4] BaseTools: Remove BUILDRULEFAMILY from CLANGDWARF in tools_def.template Rebecca Cran
2023-05-09 23:53 ` [edk2-stable202305 PATCH 2/4] BaseTools: Set the CLANGDWARF OBJCOPY path " Rebecca Cran
2023-05-10 11:03 ` [edk2-devel] " Ard Biesheuvel
2023-05-10 12:09 ` Rebecca Cran
2023-05-10 12:10 ` Ard Biesheuvel
2023-05-10 12:33 ` Rebecca Cran
2023-05-09 23:53 ` [edk2-stable202305 PATCH 3/4] BaseTools: Set CLANGDWARF RC path to llvm-objcopy " Rebecca Cran
2023-05-09 23:53 ` [edk2-stable202305 PATCH 4/4] BaseTools: Remove the CLANGCC build rule for Hii-Binary-Package.UEFI_HII Rebecca Cran
2023-05-10 2:36 ` [edk2-devel] [edk2-stable202305 PATCH 0/4] BaseTools: Fix CLANGDWARF HII resource rules and paths Michael D Kinney
2023-05-10 2:40 ` Rebecca Cran
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=20230509235337.1815842-1-rebecca@bsdio.com \
--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