public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "yi1 li" <yi1.li@intel.com>
To: devel@edk2.groups.io
Cc: yi1 li <yi1.li@intel.com>, Bob Feng <bob.c.feng@intel.com>,
	Liming Gao <liming.gao@intel.com>,
	"Zhiju . Fan" <zhijux.fan@intel.com>
Subject: [PATCH 0/2] BaseTools:Add the FeatureFlagExpression usage to the InfBuildData
Date: Tue,  8 Mar 2022 15:07:09 +0800	[thread overview]
Message-ID: <cover.1646721943.git.yi1.li@intel.com> (raw)

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

FeatureFlagExpression Support in LibraryClasses/Guids/Ppi/Protocols/
Source section of INF file. The Pcd value in the expression is from 
INF or DEC When a FeatureFlagExpression is present,if the expression
evaluates to TRUE,then the entry is valid. If the expression evaluates
to FALSE, then the EDK II build tools must ignore the entry.

This patch is going to add this feature.

Cc: Bob Feng <bob.c.feng@intel.com>
Cc: Liming Gao <liming.gao@intel.com>
Signed-off-by: yi1 li <yi1.li@intel.com>
Signed-off-by: Zhiju.Fan <zhijux.fan@intel.com>

yi1 li (2):
  BaseTools:Add the FeatureFlagExpression usage to the InfBuildData
  BaseTools:Add the FeatureFlagExpression usage to the Source Section

 BaseTools/Source/Python/Common/Expression.py  |  2 +-
 BaseTools/Source/Python/Common/GlobalData.py  |  1 +
 .../Source/Python/Workspace/InfBuildData.py   | 79 ++++++++++++++++---
 .../Source/Python/Workspace/MetaFileParser.py |  4 +
 .../Python/Workspace/WorkspaceCommon.py       | 10 ++-
 5 files changed, 84 insertions(+), 12 deletions(-)

-- 
2.33.0.windows.2


             reply	other threads:[~2022-03-08  7:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-08  7:07 yi1 li [this message]
2022-03-08  7:07 ` [PATCH 1/2] BaseTools:Add the FeatureFlagExpression usage to the InfBuildData yi1 li
2022-03-08  7:07 ` [PATCH 2/2] BaseTools:Add the FeatureFlagExpression usage to the Source Section yi1 li

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=cover.1646721943.git.yi1.li@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