From: "Andrew Fish" <afish@apple.com>
To: devel@edk2.groups.io
Cc: Andrew Fish <afish@apple.com>
Subject: [PATCH 0/3] Add PE/COFF resource sections support for XCODE
Date: Sun, 24 May 2020 14:20:08 -0700 [thread overview]
Message-ID: <cover.1590354726.git.afish@apple.com> (raw)
This patch series adds PE/COFF resource section support for XCODE.
It should be possible to use the build_rule.template and GenFw.c
changes on any toolchain. RVCT also has this issue so could be
fixed.
I test this on XCODE on the inject an extra section, and append to
last section path.
Andrew Fish (3):
BaseTools/GenFv: Add PE/COFF resource sections injection to GenFw
BaseTools: Add PE/COFF resource sections support for XCODE
OvmfwPkg: Don't exclude XCODE Modules
BaseTools/Conf/build_rule.template | 15 +-
BaseTools/Source/C/GenFw/GenFw.c | 370 +++++++++++++++++++++++++++++
OvmfPkg/OvmfPkgIa32.dsc | 3 +-
OvmfPkg/OvmfPkgIa32.fdf | 2 -
OvmfPkg/OvmfPkgIa32X64.dsc | 4 +-
OvmfPkg/OvmfPkgIa32X64.fdf | 2 -
OvmfPkg/OvmfPkgX64.dsc | 3 +-
OvmfPkg/OvmfPkgX64.fdf | 2 -
OvmfPkg/OvmfXen.dsc | 3 +-
OvmfPkg/OvmfXen.fdf | 2 -
10 files changed, 386 insertions(+), 20 deletions(-)
--
2.24.1 (Apple Git-126)
next reply other threads:[~2020-05-24 21:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-24 21:20 Andrew Fish [this message]
2020-05-24 21:20 ` [PATCH 1/3] BaseTools/GenFv: Add PE/COFF resource sections injection to GenFw Andrew Fish
2020-05-27 3:15 ` Bob Feng
2020-05-24 21:20 ` [PATCH 2/3] BaseTools: Add PE/COFF resource sections support for XCODE Andrew Fish
2020-05-24 21:20 ` [PATCH 3/3] OvmfwPkg: Don't exclude XCODE Modules Andrew Fish
2020-05-25 19:31 ` [edk2-devel] " Laszlo Ersek
2020-05-26 4:10 ` Andrew Fish
2020-05-26 11:45 ` Laszlo Ersek
2020-05-27 6:05 ` Andrew Fish
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=cover.1590354726.git.afish@apple.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