From mboxrd@z Thu Jan 1 00:00:00 1970 Subject: Re: [edk2-devel] [EXTERNAL] RE: [edk2-devel] Seeking feedback: example of building OvmfPkg with Pytools To: Bob Feng ,devel@edk2.groups.io From: "Sean" X-Originating-Location: Redmond, Washington, US (50.35.74.15) X-Originating-Platform: Windows Chrome 80 User-Agent: GROUPS.IO Web Poster MIME-Version: 1.0 Date: Thu, 05 Dec 2019 20:39:43 -0800 References: <08650203BA1BD64D8AD9B6D5D74A85D16157C55A@SHSMSX104.ccr.corp.intel.com> In-Reply-To: <08650203BA1BD64D8AD9B6D5D74A85D16157C55A@SHSMSX104.ccr.corp.intel.com> Message-ID: <3885.1575607183837668050@groups.io> Content-Type: multipart/alternative; boundary="sUVODVGqturs8gPqIjwu" --sUVODVGqturs8gPqIjwu Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Bob, Glad to hear it is working for you.=C2=A0 A few questions just to make sur= e something wasn't missed. Did you build edk2 base tools using the process here. https://github.com/out0xb2/edk2/blob/feature/pytoolsForOvmf/OvmfPkg/README= -pytools.md#differences-from-edk-classic-build-setup If you follow the process documented it puts a file in the output folder t= hat will trigger pytools to add the folder to the path and set an environme= nt variable as required by edk2 build. If you build the basetools yourself please delete them and use the process= above.=C2=A0 After doing that you should not need to add basetools/bin/win= 32 to your path. Please let me know if that doesn't work. Thanks Sean --sUVODVGqturs8gPqIjwu Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Bob,

Glad to hear it is working for you.  A few questions j= ust to make sure something wasn't missed.  

Did you bu= ild edk2 base tools using the process here. 
https://github.com/out0xb2/edk2= /blob/feature/pytoolsForOvmf/OvmfPkg/README-pytools.md#differences-from-edk= -classic-build-setup

If you follow the process documented it= puts a file in the output folder that will trigger pytools to add the fold= er to the path and set an environment variable as required by edk2 build.&n= bsp; 

If you build the basetools yourself please delete the= m and use the process above.  After doing that you should not need to = add basetools/bin/win32 to your path.  

Please let me = know if that doesn't work. 

Thanks
Sean

--sUVODVGqturs8gPqIjwu--