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-BuildSpecification PATCH] Use macros in !include file paths
Date: Wed, 12 Apr 2017 14:38:58 -0700	[thread overview]
Message-ID: <1492033139-8604-1-git-send-email-michael.d.kinney@intel.com> (raw)

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

GitHub branch for review:

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

  https://github.com/tianocore-docs/edk2-BuildSpecification/compare/master...mdkinney:Bugzilla_472_MacrosInIncludes?w=1

The EBNF already allows !include statements to use
$(MACRO) values in the file path.  This change updates
the description and examples for !include statements
to allow the use of macros and specific environment
variables in !include file paths.

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):
  Use macros in !include file paths

 8_pre-build_autogen_stage/82_auto-generation_process.md | 4 ++--
 README.md                                               | 3 ++-
 2 files changed, 4 insertions(+), 3 deletions(-)

-- 
2.6.3.windows.1



             reply	other threads:[~2017-04-12 21:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-12 21:38 Michael Kinney [this message]
2017-04-12 21:38 ` [edk2-BuildSpecification PATCH] Use macros in !include file paths Michael Kinney
2017-04-13  2:25   ` 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=1492033139-8604-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