public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gao, Liming" <liming.gao@intel.com>
To: Laszlo Ersek <lersek@redhat.com>,
	"Frank.Orr@dell.com" <Frank.Orr@dell.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: FeatureFlagExpression
Date: Wed, 23 Aug 2017 02:47:28 +0000	[thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14D77483A@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <12eaddeb-bfc8-6cf2-fd52-0d377be5e776@redhat.com>

Frank:
  This is unsupported feature. Now, FeatureFlagExpression is ignored. 

Thanks
Liming
>-----Original Message-----
>From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
>Laszlo Ersek
>Sent: Wednesday, August 23, 2017 7:55 AM
>To: Frank.Orr@dell.com; edk2-devel@lists.01.org
>Subject: Re: [edk2] FeatureFlagExpression
>
>On 08/23/17 01:21, Frank.Orr@dell.com wrote:
>> Dell - Internal Use - Confidential
>>
>>  I'm trying to use this feature as described in various edk2 documents with
>zero success.
>> For example, in the INF spec 1.25, the following is defined for the protocols
>section :
>>
>>
>>
>> The formats for entries in this section is:
>>
>> gEfiProtocolCName [ | FeatureFlagExpression] ## Usage comment
>>
>> When a FeatureFlagExpression is present, if the expression evaluates to
>TRUE, then the Protocal entry is valid. If the expression evaluates to FALSE,
>then the EDK II build tools must ignore the entry.
>>
>> The following is an example of the [Protocols] section.
>>
>> [Protocols]
>>
>> gEfiDecompressProtocolGuid
>>
>> gEfiLoadFileProtocolGuid
>>
>>
>> Does anyone have any examples showing the use of a
>FeatureFlagExpression ?
>
>See e.g. "MdePkg/Library/UefiLib/UefiLib.inf".
>
>Thanks
>Laszlo
>_______________________________________________
>edk2-devel mailing list
>edk2-devel@lists.01.org
>https://lists.01.org/mailman/listinfo/edk2-devel


      reply	other threads:[~2017-08-23  2:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-22 23:21 FeatureFlagExpression Frank.Orr
2017-08-22 23:54 ` FeatureFlagExpression Laszlo Ersek
2017-08-23  2:47   ` Gao, Liming [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=4A89E2EF3DFEDB4C8BFDE51014F606A14D77483A@shsmsx102.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