From: "ryderkeys via groups.io" <ryderkeys=proton.me@groups.io>
To: devel@edk2.groups.io
Cc: "lersek@redhat.com" <lersek@redhat.com>,
Sean Brogan <sean.brogan@microsoft.com>
Subject: Re: [edk2-devel] BaseTools KeyError When Building EmulatorPkg
Date: Mon, 27 Nov 2023 22:48:49 +0000 [thread overview]
Message-ID: <gXTdmNPhCrZ5uZfNuKyGYs4xlv2s9_j2qyCz5tJq43b0aOzlckPGrJGd8mO8gx9ZS6rfEdbZOelOY9fJgVyAR48kznn4cJB3_QjT_Hxn7D8=@proton.me> (raw)
In-Reply-To: <BY3PR19MB4900B6E04A3DE9A5057AE18DC8BDA@BY3PR19MB4900.namprd19.prod.outlook.com>
On Monday, November 27th, 2023 at 2:43 PM, Sean via groups.io wrote:
> In the meantime there are two easy workarounds (pick one).
>
> 1. Create your venv named something like "venv" instead of ".venv". It just must come later in the default directory sort than "Basetools".
>
> or
>
> 2. Create your venv outside the edk2 source code tree. Generally this is what I do as I don't like my virtual environment mixed with my source code.
>
> As mentioned before don't forget to build the basetools. From there, my experience is everything works. Thanks for reporting your issue.
Hi Sean,
Thanks for the reply and the swift resolution. Regarding your suggestions:
0. I can confirm that after uninstalling the pip basetools, the error disappears and the build works.
1. It also works if I rename ".venv" to something that starts after B (such as venv)
2. It also works if I place the venv outside the source tree.
Thanks once again for the help,
Ryder
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#111762): https://edk2.groups.io/g/devel/message/111762
Mute This Topic: https://groups.io/mt/102698986/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2023-11-27 22:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-19 22:43 [edk2-devel] BaseTools KeyError When Building EmulatorPkg ryderkeys via groups.io
2023-11-21 16:22 ` Laszlo Ersek
2023-11-27 18:16 ` Sean
[not found] ` <179B8D98556E51B3.32091@groups.io>
2023-11-27 19:43 ` Sean
2023-11-27 22:48 ` ryderkeys via groups.io [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='gXTdmNPhCrZ5uZfNuKyGYs4xlv2s9_j2qyCz5tJq43b0aOzlckPGrJGd8mO8gx9ZS6rfEdbZOelOY9fJgVyAR48kznn4cJB3_QjT_Hxn7D8=@proton.me' \
--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