summaryrefslogtreecommitdiff
path: root/BaseTools
diff options
context:
space:
mode:
authorklu2 <klu2@6f19259b-4bc3-4df7-8a09-765794883524>2009-05-18 07:09:48 +0000
committerklu2 <klu2@6f19259b-4bc3-4df7-8a09-765794883524>2009-05-18 07:09:48 +0000
commit8968742e88751da9b11c93fb75e06a8288e219fe (patch)
tree7c3ea7b134f07d22d3457d87c5a405013de35b5c /BaseTools
parent7d28e82d92741620dbe77f56f97f40c81ba6fe5e (diff)
downloadedk2-platforms-8968742e88751da9b11c93fb75e06a8288e219fe.tar.xz
Originally, there are following implementation:
1) The collect action of platform's dynamic PCD database is trigged by module's autogen action. 2) If platform is used for more than one architecture, two platform object will be created Above two rules will cause an issue for single module building that if 1) platform support IA32 and X64 2) do single module for X64 module then, the dynamic PCD for IA32 modules will missed in PCD database, because no IA32 module need autogen so collection action for IA32 module is not trigged. Now, I think the collection action for platform dynamic PCD should be explicitly called after PlatformAutoGen is created. git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@8323 6f19259b-4bc3-4df7-8a09-765794883524
Diffstat (limited to 'BaseTools')
-rwxr-xr-xBaseTools/Bin/Win32/build.exebin1685098 -> 1685047 bytes
1 files changed, 0 insertions, 0 deletions
diff --git a/BaseTools/Bin/Win32/build.exe b/BaseTools/Bin/Win32/build.exe
index ba90163cad..6f4d5daa07 100755
--- a/BaseTools/Bin/Win32/build.exe
+++ b/BaseTools/Bin/Win32/build.exe
Binary files differ