From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, zhijux.fan@intel.com
Cc: "Gao, Liming" <liming.gao@intel.com>,
"Feng, Bob C" <bob.c.feng@intel.com>
Subject: Re: [edk2-devel] [PATCH] BaseTools:Add the FeatureFlagExpression usage to the InfBuildData
Date: Tue, 21 May 2019 23:09:57 +0200 [thread overview]
Message-ID: <330e5eb6-5220-5026-74da-d4fb1622cca9@redhat.com> (raw)
In-Reply-To: <FAD0D7E0AE0FA54D987F6E72435CAFD50AF610FD@SHSMSX101.ccr.corp.intel.com>
On 05/17/19 02:57, Fan, ZhijuX wrote:
> BZ:https://bugzilla.tianocore.org/show_bug.cgi?id=1446
>
> FeatureFlagExpression Support in LibraryClasses/Guids/Ppi/Protocols
> 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: Zhiju.Fan <zhijux.fan@intel.com>
> ---
> BaseTools/Source/Python/Common/Expression.py | 2 +-
> BaseTools/Source/Python/Common/GlobalData.py | 1 +
> BaseTools/Source/Python/Workspace/InfBuildData.py | 69 ++++++++++++++++++++--
> .../Source/Python/Workspace/WorkspaceCommon.py | 10 +++-
> 4 files changed, 73 insertions(+), 9 deletions(-)
This feature has missed edk2-stable201905.
Please postpone the following BZ reference:
https://bugzilla.tianocore.org/show_bug.cgi?id=1446
from
https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Planning#edk2-stable201905-tag-planning
to
https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Planning#edk2-stable201908-tag-planning
Thanks,
Laszlo
prev parent reply other threads:[~2019-05-21 21:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 0:57 [PATCH] BaseTools:Add the FeatureFlagExpression usage to the InfBuildData Fan, ZhijuX
2019-05-21 21:09 ` Laszlo Ersek [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=330e5eb6-5220-5026-74da-d4fb1622cca9@redhat.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