From: "Bob Feng" <bob.c.feng@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"sean.brogan@microsoft.com" <sean.brogan@microsoft.com>
Subject: Re: [edk2-devel] [EXTERNAL] RE: [edk2-devel] Seeking feedback: example of building OvmfPkg with Pytools
Date: Fri, 6 Dec 2019 06:51:40 +0000 [thread overview]
Message-ID: <08650203BA1BD64D8AD9B6D5D74A85D16157C9DC@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <3885.1575607183837668050@groups.io>
[-- Attachment #1: Type: text/plain, Size: 1542 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 6684 bytes --]
prev parent reply other threads:[~2019-12-06 6:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 0:03 Seeking feedback: example of building OvmfPkg with Pytools Jeremiah Cox
2019-11-27 9:28 ` [edk2-devel] " Laszlo Ersek
2019-11-29 2:50 ` Bob Feng
2019-12-03 0:40 ` [EXTERNAL] " Jeremiah Cox
[not found] ` <MN2PR21MB12620D584417FD5F98564AE6D1420@MN2PR21MB1262.namprd21.prod.outlook.com>
2019-12-03 7:47 ` Bob Feng
[not found] ` <MN2PR21MB12622D6027E9F93768FA4D79D1420@MN2PR21MB1262.namprd21.prod.outlook.com>
2019-12-03 17:51 ` Jeremiah Cox
[not found] ` <MN2PR21MB12622C51F53677E34B8C214AD1420@MN2PR21MB1262.namprd21.prod.outlook.com>
2019-12-03 18:11 ` Sean
2019-12-06 2:35 ` Bob Feng
2019-12-06 4:39 ` [edk2-devel] " Sean
2019-12-06 6:51 ` Bob Feng [this message]
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=08650203BA1BD64D8AD9B6D5D74A85D16157C9DC@SHSMSX104.ccr.corp.intel.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