public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
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-DscSpecification PATCH] Declare Pre/Post build scripts in [Defines] section
Date: Mon, 17 Apr 2017 18:08:15 -0700	[thread overview]
Message-ID: <1492477696-44816-1-git-send-email-michael.d.kinney@intel.com> (raw)

https://bugzilla.tianocore.org/show_bug.cgi?id=484

GitHub branch for review:

  https://github.com/mdkinney/edk2-DscSpecification/tree/Bugzilla_484_PrePostBuild
  
GitHub branch compare against latest DRAFT for review:

  https://github.com/tianocore-docs/edk2-DscSpecification/compare/master...mdkinney:Bugzilla_484_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

 2_dsc_overview/23_[defines]_section_processing.md | 11 +++++++++++
 3_edk_ii_dsc_file_format/35_[defines]_section.md  |  2 ++
 README.md                                         |  1 +
 3 files changed, 14 insertions(+)

-- 
2.6.3.windows.1



             reply	other threads:[~2017-04-18  1:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-18  1:08 Michael Kinney [this message]
2017-04-18  1:08 ` [edk2-DscSpecification PATCH] Declare Pre/Post build scripts in [Defines] section Michael Kinney
2017-04-18  2:21   ` 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=1492477696-44816-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