From: Michael Kinney <michael.d.kinney@intel.com>
To: edk2-devel@lists.01.org
Cc: Liming Gao <liming.gao@intel.com>,
Yonghong Zhu <yonghong.zhu@intel.com>,
Kevin W Shaw <kevin.w.shaw@intel.com>
Subject: [edk2-BuildSpecification PATCH] Declare Pre/Post build scripts in [Defines] section
Date: Mon, 17 Apr 2017 18:05:39 -0700 [thread overview]
Message-ID: <1492477540-41700-1-git-send-email-michael.d.kinney@intel.com> (raw)
https://bugzilla.tianocore.org/show_bug.cgi?id=483
GitHub branch for review:
https://github.com/mdkinney/edk2-BuildSpecification/tree/Bugzilla_483_PrePostBuild
GitHub branch compare against latest DRAFT for review:
https://github.com/tianocore-docs/edk2-BuildSpecification/compare/master...mdkinney:Bugzilla_483_PrePostBuild?w=1
Add support for PREBUILD and POSTBUILD defines in
the [Defines] section of an DSC to declare scripts
that are executed before and after normal DSC/FDF
file processing.
Cc: Liming Gao <liming.gao@intel.com>
Cc: Yonghong Zhu <yonghong.zhu@intel.com>
Cc: Kevin W Shaw <kevin.w.shaw@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Michael Kinney <michael.d.kinney@intel.com>
Michael Kinney (1):
Declare Pre/Post build scripts in [Defines] section
.../106_post_build_processing.md | 61 ++++++++++++++++++++++
.../82_auto-generation_process.md | 33 ++++++++++++
README.md | 1 +
SUMMARY.md | 1 +
4 files changed, 96 insertions(+)
create mode 100644 10_post-build_imagegen_stage_-_flash/106_post_build_processing.md
--
2.6.3.windows.1
next reply other threads:[~2017-04-18 1:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 1:05 Michael Kinney [this message]
2017-04-18 1:05 ` [edk2-BuildSpecification PATCH] Declare Pre/Post build scripts in [Defines] section Michael Kinney
2017-04-18 2:19 ` Zhu, Yonghong
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=1492477540-41700-1-git-send-email-michael.d.kinney@intel.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