Hi Sean,

You are right. I had a myself built Basetools binaries and did not rebuild them with BaseTools\Edk2ToolsBuild.py.

I clean up my edk2 workspace and follow the steps in https://github.com/out0xb2/edk2/blob/feature/pytoolsForOvmf/OvmfPkg/README-pytools.md.
Everything goes well. Thanks.

I did:
python BaseTools\Edk2ToolsBuild.py -t VS2017
stuart_setup  -c OvmfPkg\PlatformBuild.py
stuart_update  -c OvmfPkg\PlatformBuild.py
stuart_build -c OvmfPkg\PlatformBuild.py TOOL_CHAIN_TAG=VS2017

Thanks,
Bob

From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of Sean via Groups.Io
Sent: Friday, December 6, 2019 12:40 PM
To: Feng, Bob C <bob.c.feng@intel.com>; devel@edk2.groups.io
Subject: Re: [edk2-devel] [EXTERNAL] RE: [edk2-devel] Seeking feedback: example of building OvmfPkg with Pytools

Bob,

Glad to hear it is working for you.  A few questions just to make sure 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 that will trigger pytools to add the folder to the path and set an environment variable as required by edk2 build.

If you build the basetools yourself please delete them 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