From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.byosoft.com.cn (mail.byosoft.com.cn [58.240.74.242]) by mx.groups.io with SMTP id smtpd.web11.1409.1604538958737325661 for ; Wed, 04 Nov 2020 17:15:59 -0800 Authentication-Results: mx.groups.io; dkim=missing; spf=none, err=permanent DNS error (domain: byosoft.com.cn, ip: 58.240.74.242, mailfrom: fengyunhua@byosoft.com.cn) Received: from LAPTOP2AECFQIA ([58.246.60.130]) (envelope-sender ) by 192.168.6.13 with ESMTP for ; Thu, 05 Nov 2020 09:15:53 +0800 X-WM-Sender: fengyunhua@byosoft.com.cn X-WM-AuthFlag: YES X-WM-AuthUser: fengyunhua@byosoft.com.cn From: "fengyunhua" To: , Cc: "'Bob Feng'" , "'Liming Gao'" , "'Yuwei Chen'" References: <20201104075304.382-1-mingyuex.liang@intel.com> In-Reply-To: <20201104075304.382-1-mingyuex.liang@intel.com> Subject: =?UTF-8?B?5Zue5aSNOiBbZWRrMi1kZXZlbF0gW1BBVENIXSBCYXNlVG9vbHM6IENhdGNoIHRoZSBleGNlcHRpb24gaW4gYnVpbGQucHku?= Date: Thu, 5 Nov 2020 09:15:56 +0800 Message-ID: <000001d6b311$36970090$a3c501b0$@byosoft.com.cn> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQIu7s9o3rNpdBtSLeqrNMht9xWJtKkIQTvA Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: quoted-printable Content-Language: zh-cn I tried this patch, modified OvmfPkgIa32.fdf INF OvmfPkg/Sec/SecMain.inf =3D=3D=3D> INM OvmfPkg/Sec/SecMain.inf the error message as below: build.py... c:\work\edk2\OvmfPkg\OvmfPkgIa32.fdf(118): error 3000: Invalid syntax/form= at expected [FD.] near line 110, column 22: TRUE on my opinion, "expected [FD.]" is not correct -----=D3=CA=BC=FE=D4=AD=BC=FE----- =B7=A2=BC=FE=C8=CB: bounce+27952+66996+5049190+8953120@groups.io =B4=FA=B1=ED mliang2x =B7=A2=CB=CD=CA=B1=BC=E4: 2020=C4=EA11=D4=C24=C8=D5 15:53 =CA=D5=BC=FE=C8=CB: devel@edk2.groups.io =B3=AD=CB=CD: Mingyue Liang ; Bob Feng ; Liming Gao ; Yuwei Chen =D6=F7=CC=E2: [edk2-devel] [PATCH] BaseTools: Catch the exception in build= .py. REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3D2988 In FDF file, if INF key word is wrongly written as INT, build tool will report the execption. Build tool should report the error message. build.py In order to capture and handle the exception of fdfparser, the user-defined exception class should be imported. Signed-off-by: Mingyue Liang Cc: Bob Feng Cc: Liming Gao Cc: Yuwei Chen --- BaseTools/Source/Python/build/build.py | 1 + 1 file changed, 1 insertion(+) diff --git a/BaseTools/Source/Python/build/build.py b/BaseTools/Source/Python/build/build.py index 1ab1e60a64..49165ea355 100755 --- a/BaseTools/Source/Python/build/build.py +++ b/BaseTools/Source/Python/build/build.py @@ -62,6 +62,7 @@ from AutoGen.ModuleAutoGenHelper import WorkSpaceInfo, PlatformInfo from GenFds.FdfParser import FdfParser from AutoGen.IncludesAutoGen import IncludesAutoGen from GenFds.GenFds import resetFdsGlobalVariable +from GenFds.FdfParser import Warning =20 ## standard targets of build command gSupportedTarget =3D ['all', 'genc', 'genmake', 'modules', 'libraries', 'fds', 'clean', 'cleanall', 'cleanlib', 'run'] --=20 2.28.0.windows.1