From: "Zhu, Yonghong" <yonghong.zhu@intel.com>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Gao, Liming" <liming.gao@intel.com>,
"Shaw, Kevin W" <kevin.w.shaw@intel.com>,
"Zhu, Yonghong" <yonghong.zhu@intel.com>
Subject: Re: [edk2-BuildSpecification PATCH] Only copy "TianoCore" UserExtensions to AsBuilt INF
Date: Thu, 13 Apr 2017 01:24:51 +0000 [thread overview]
Message-ID: <B9726D6DCCFB8B4CA276A9169B02216D51E5CB8C@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1492031445-27236-2-git-send-email-michael.d.kinney@intel.com>
Reviewed-by: Yonghong Zhu <yonghong.zhu@intel.com>
Best Regards,
Zhu Yonghong
-----Original Message-----
From: Kinney, Michael D
Sent: Thursday, April 13, 2017 5:11 AM
To: edk2-devel@lists.01.org
Cc: Gao, Liming <liming.gao@intel.com>; Zhu, Yonghong <yonghong.zhu@intel.com>; Shaw, Kevin W <kevin.w.shaw@intel.com>
Subject: [edk2-BuildSpecification PATCH] Only copy "TianoCore" UserExtensions to AsBuilt INF
https://bugzilla.tianocore.org/show_bug.cgi?id=471
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>
---
8_pre-build_autogen_stage/87_generated_asbuilt_inf_files.md | 9 +++++----
README.md | 3 ++-
2 files changed, 7 insertions(+), 5 deletions(-)
diff --git a/8_pre-build_autogen_stage/87_generated_asbuilt_inf_files.md b/8_pre-build_autogen_stage/87_generated_asbuilt_inf_files.md
index 64685ce..9e89d83 100644
--- a/8_pre-build_autogen_stage/87_generated_asbuilt_inf_files.md
+++ b/8_pre-build_autogen_stage/87_generated_asbuilt_inf_files.md
@@ -465,7 +465,8 @@ from a sources section.
### 8.7.14 [UserExtensions] Section
-The build tools must copy all of the source INF's `[UserExtensions]` sections -into the generated INF. The EDK II build tools will ignore these sections, -however other vendors may provide tools that have a priori knowledge of how to -process these sections.
+Any `[UserExtensions]` sections that are present in the source INF with
+a UserId of "TianoCore" will be copied into the generated INF.
+`[UserExtensions]` sections with other UserId values will not be copied to the generated INF.
+The EDK II build tools will ignore these sections, however other
+vendors may provide tools that have a priori knowledge of how to process these sections.
diff --git a/README.md b/README.md
index 3bd1d32..5696cc3 100644
--- a/README.md
+++ b/README.md
@@ -200,4 +200,5 @@ Copyright (c) 2008-2017, Intel Corporation. All rights reserved.
| | Remove Unicode file storage requirement; refer to the Multi-String UNI File Format Specification instead. | |
| | Clarify BUILDRULEORDER | |
| | Add support for INF statement in an FD region. | |
-| 1.27 | Convert to Gitbook | March 2017 |
+| 1.27 | Convert to Gitbook | April 2017 |
+| | [#471](https://bugzilla.tianocore.org/show_bug.cgi?id=471) Build spec: only copy the "TianoCore" Userextension section into "As Built" INF | |
--
2.6.3.windows.1
prev parent reply other threads:[~2017-04-13 1:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 21:10 [edk2-BuildSpecification PATCH] Only copy "TianoCore" UserExtensions to AsBuilt INF Michael Kinney
2017-04-12 21:10 ` Michael Kinney
2017-04-13 1:24 ` Zhu, Yonghong [this message]
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=B9726D6DCCFB8B4CA276A9169B02216D51E5CB8C@SHSMSX103.ccr.corp.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