From: "Lin, Derek (HPS UEFI Dev)" <derek.lin2@hpe.com>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "yonghong.zhu@intel.com" <yonghong.zhu@intel.com>,
"Lin, Derek (HPS UEFI Dev)" <derek.lin2@hpe.com>
Subject: [PATCH] BaseTools: Remove dsc nested include checking.
Date: Wed, 9 May 2018 07:50:38 +0000 [thread overview]
Message-ID: <CS1PR8401MB06789B92CD557D30E99883ADC2990@CS1PR8401MB0678.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20180509073910.19400-1-derek.lin2@hpe.com>
From: Lin, Derek (HPS UEFI Dev)
Sent: Wednesday, May 9, 2018 3:39 PM
To: Lin, Derek (HPS UEFI Dev) <derek.lin2@hpe.com>
Subject: [PATCH] BaseTools: Remove dsc nested include checking.
The dsc nested include checking make unexpected build error when building project A and switch to project B.
---
BaseTools/Source/Python/Workspace/MetaFileParser.py | 19 +++++++++++++++----
1 file changed, 15 insertions(+), 4 deletions(-)
diff --git a/BaseTools/Source/Python/Workspace/MetaFileParser.py b/BaseTools/Source/Python/Workspace/MetaFileParser.py
index 36843643ed..092253530f 100644
--- a/BaseTools/Source/Python/Workspace/MetaFileParser.py
+++ b/BaseTools/Source/Python/Workspace/MetaFileParser.py
@@ -2,7 +2,7 @@
# This file is used to parse meta files # # Copyright (c) 2008 - 2018, Intel Corporation. All rights reserved.<BR> -# (C) Copyright 2015-2016 Hewlett Packard Enterprise Development LP<BR>
+# (C) Copyright 2015-2018 Hewlett Packard Enterprise Development LP<BR>
# This program and the accompanying materials # are licensed and made available under the terms and conditions of the BSD License # which accompanies this distribution. The full text of the license may be found at @@ -1551,10 +1551,21 @@ class DscParser(MetaFileParser):
self.IncludedFiles.add (IncludedFile1)
+ # todo: rework the nested include checking logic
+ # Current nested include checking rely on dsc file order inside build.db.
+ # It is not reliable and will lead to build fail in some case.
+ #
+ # When project A and B include a common dsc file C.
+ # Build project A. It give dsc file A = ID 1 in build.db, and C ID = 2.
+ # Build project B. It give dsc file B ID = 3, and C ID still = 2.
+ # Then, we build project B fail, unless we clean build.db.
+ # In oldder BaseTools, the project B ID will still be 1,
+ # that's why it work before.
+
# Does not allow lower level included file to include upper level included file
- if Parser._From != Owner and int(Owner) > int (Parser._From):
- EdkLogger.error('parser', FILE_ALREADY_EXIST, File=self._FileWithError,
- Line=self._LineIndex + 1, ExtraData="{0} is already included at a higher level.".format(IncludedFile1))
+ #if Parser._From != Owner and int(Owner) > int (Parser._From):
+ # EdkLogger.error('parser', FILE_ALREADY_EXIST, File=self._FileWithError,
+ # Line=self._LineIndex + 1, ExtraData="{0} is already included at a higher level.".format(IncludedFile1))
# set the parser status with current status
--
2.15.1.windows.2
next parent reply other threads:[~2018-05-09 7:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180509073910.19400-1-derek.lin2@hpe.com>
2018-05-09 7:50 ` Lin, Derek (HPS UEFI Dev) [this message]
[not found] <20180509090202.9200-1-derek.lin2@hpe.com>
2018-05-09 9:03 ` [PATCH] BaseTools: Remove dsc nested include checking Lin, Derek (HPS UEFI Dev)
2018-06-11 8:39 ` Zhu, Yonghong
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=CS1PR8401MB06789B92CD557D30E99883ADC2990@CS1PR8401MB0678.NAMPRD84.PROD.OUTLOOK.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