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] Add support for Private declarations in a package
Date: Mon, 24 Apr 2017 18:11:46 -0700 [thread overview]
Message-ID: <1493082707-4972-1-git-send-email-michael.d.kinney@intel.com> (raw)
https://bugzilla.tianocore.org/show_bug.cgi?id=465
GitHub word diff view of the patches in this series
* https://github.com/mdkinney/edk2-BuildSpecification/commit/97290a0b1e926c946959ed11f931fd2db26ad04b?w=1
Process new syntax in the DEC file that specifies
information that can only be used by modules within
the package. When modules outside the packages attempt
to use this content, the EDK II build system must
break with an error regarding content not found.
The four sections, Includes, Ppis, Guids and Protocols
headers will be the keyword, Private, following the
architecture modifier. If Private is not present, then
the content is usable by modules outside the package.
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):
Add support for Private declarations in a package
.../82_auto-generation_process.md | 35 ++++++++++++++--------
.../84_auto-generated_pcd_database_file.md | 6 ++++
README.md | 3 +-
3 files changed, 30 insertions(+), 14 deletions(-)
--
2.6.3.windows.1
next reply other threads:[~2017-04-25 1:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-25 1:11 Michael Kinney [this message]
2017-04-25 1:11 ` [ edk2-BuildSpecification PATCH] Add support for Private declarations in a package Michael Kinney
2017-04-25 1:53 ` Zhu, Yonghong
2017-04-25 2:36 ` Kinney, Michael D
2017-04-25 2:37 ` Zhu, Yonghong
2017-04-25 2:46 ` Kinney, Michael D
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=1493082707-4972-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