From: "BobCF" <bob.c.feng@intel.com>
To: devel@edk2.groups.io
Cc: Bob Feng <bob.c.feng@intel.com>, Liming Gao <liming.gao@intel.com>
Subject: [Patch] Document: Add PCD_DYNAMIC_AS_DYNAMICEX to defines section
Date: Thu, 11 Apr 2019 16:51:37 +0800 [thread overview]
Message-ID: <20190411085138.24784-1-bob.c.feng@intel.com> (raw)
BZ: https://bugzilla.tianocore.org/show_bug.cgi?id=1688
DynamicEx Pcd supports binary module build well.
It's helpful to add a new build option for build tool
to convert all Dynamic Pcd to DynamicEx Pcd.
Add a new key word in defines section for this function.
Signed-off-by: Bob Feng <bob.c.feng@intel.com>
Cc: Liming Gao <liming.gao@intel.com>
---
2_dsc_overview/23_[defines]_section_processing.md | 1 +
3_edk_ii_dsc_file_format/35_[defines]_section.md | 1 +
README.md | 1 +
3 files changed, 3 insertions(+)
diff --git a/2_dsc_overview/23_[defines]_section_processing.md b/2_dsc_overview/23_[defines]_section_processing.md
index ad0702b..c0f24ca 100644
--- a/2_dsc_overview/23_[defines]_section_processing.md
+++ b/2_dsc_overview/23_[defines]_section_processing.md
@@ -115,10 +115,11 @@ item is required.
| `VPD_TOOL_GUID` | Optional | Registry Format GUID | When this element is present, the build process will be interrupted during the AutoGen stage in order to call an external program, named by GUID that must also be defined in the Conf/tools_def.txt file using a tool code name of VPDTOOL. Refer to the EDK II Build specification for additional information. |
| `PCD_INFO_GENERATION` | Optional | TRUE or FALSE | If present, and set to TRUE, this flag will generate PCD information in the Pcd Database. |
| `PCD_VAR_CHECK_GENERATION` | Optional | TRUE or FALSE | If present and set to TRUE, this flag will generate the variable validation table binary file in the build output FV floder. If not present ro set to FALSE, then the binary file will not be generated. |
| `PREBUILD` | Optional | String of script with arguments | If present, build tool will call the script of this statement to execute. |
| `POSTBUILD` | Optional | String of script with arguments | If present, build tool will call the script of this statement to execute. |
+| `PCD_DYNAMIC_AS_DYNAMICEX` | Optional | TRUE or FALSE | If present, and set to TRUE, this flag will convert Dynamci Pcd to DynamicEx Pcd. |
[^1]: WORKSPACE refers to the combination of the directories specified in the
WORKSPACE system environment variable and the PACKAGES_PATH system environment
variable.
diff --git a/3_edk_ii_dsc_file_format/35_[defines]_section.md b/3_edk_ii_dsc_file_format/35_[defines]_section.md
index ea2077d..6745cb8 100644
--- a/3_edk_ii_dsc_file_format/35_[defines]_section.md
+++ b/3_edk_ii_dsc_file_format/35_[defines]_section.md
@@ -123,10 +123,11 @@ The `!include` statement may be used in a `[Defines]` section.
[<TS> "ISO_LANGUAGES" <Eq> <Iso6392List> <EOL>] [<TS>
"TIME_STAMP_FILE" <Eq> <Filename> <EOL>]
[<TS> "VPD_TOOL_GUID" <Eq> <RegistryFormatGUID>
<EOL>]
[<TS> "PCD_VAR_CHECK_GENERATION" <Eq> <TF> <EOL>]
+ [<TS> "PCD_DYNAMIC_AS_DYNAMICEX" <Eq> <TF> <EOL>]
[<TS> "PREBUILD" <Eq> <Script> <EOL>]
[<TS> "POSTBUILD" <Eq> <Script> <EOL>]
[<TS> <AddressStmts>]
<IncludeStatement>*
<MacroDefinition>*
diff --git a/README.md b/README.md
index 5d774f5..d35206d 100644
--- a/README.md
+++ b/README.md
@@ -193,5 +193,6 @@ Copyright (c) 2006-2017, Intel Corporation. All rights reserved.
| | Add DefaultStores section to describe the default setting | |
| | Add structure PCD field value assignment syntax | |
| | Add !error statement section | |
| |[#1110](https://bugzilla.tianocore.org/show_bug.cgi?id=1110) Extend exclamation statement's keyword to case-insensitive | |
| 1.29 | [#1453](https://bugzilla.tianocore.org/show_bug.cgi?id=1453) Update DSC spec to remove EDK related contents | Mar 2019 |
+| | [#1688](https://bugzilla.tianocore.org/show_bug.cgi?id=1688) In sections 2.3 and 3.5, added new [Defines] boolean entry PCD_DYNAMIC_AS_DYNAMICEX | |
--
2.20.1.windows.1
reply other threads:[~2019-04-11 8:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190411085138.24784-1-bob.c.feng@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