From: "Rebecca Cran" <rebecca@bsdio.com>
To: Sean Brogan <spbrogan@outlook.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"michael.d.kinney@intel.com" <michael.d.kinney@intel.com>,
"Kubacki, Michael" <michael.kubacki@microsoft.com>
Subject: Re: [edk2-devel] edk2-wiki: "How to build with Stuart" - suggested changes/additions
Date: Fri, 30 Dec 2022 00:24:21 -0700 [thread overview]
Message-ID: <7ee92398-4004-9fbf-ce2f-046bc5b92edd@bsdio.com> (raw)
In-Reply-To: <BY3PR19MB490003CF42AC581334B737C6C8F09@BY3PR19MB4900.namprd19.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 2670 bytes --]
Thanks! That was the step I was missing - I was still running edksetup.bat instead of Edk2ToolsBuild.py.
--
Rebecca Cran
On 12/30/22 00:07, Sean Brogan wrote:
> Rebecca,
>
> I don't see detailed instructions for how to build the base tools in
> the new wiki pages. But if you use the python /pytool method then a
> path file is generated and Stuart will set the path correctly.
>
> This file should be used to build the base tools
> https://github.com/tianocore/edk2/blob/master/BaseTools/Edk2ToolsBuild.py
>
> You can read a little more about the feature here.
> https://www.tianocore.org/edk2-pytool-extensions/features/sde/#path_env-descriptors
>
> Thanks
> Sean
>
>
> ------------------------------------------------------------------------
> *From:* devel@edk2.groups.io <devel@edk2.groups.io> on behalf of
> Michael D Kinney <michael.d.kinney@intel.com>
> *Sent:* Thursday, December 29, 2022 9:22 AM
> *To:* devel@edk2.groups.io <devel@edk2.groups.io>; rebecca@bsdio.com
> <rebecca@bsdio.com>; Kubacki, Michael <michael.kubacki@microsoft.com>
> *Cc:* Kinney, Michael D <michael.d.kinney@intel.com>
> *Subject:* Re: [edk2-devel] edk2-wiki: "How to build with Stuart" -
> suggested changes/additions
> +Michael Kubacki
>
> > -----Original Message-----
> > From: Rebecca Cran <rebecca@bsdio.com>
> > Sent: Wednesday, December 28, 2022 7:47 PM
> > To: Kinney, Michael D <michael.d.kinney@intel.com>; devel@edk2.groups.io
> > Subject: Re: [edk2-devel] edk2-wiki: "How to build with Stuart" -
> suggested changes/additions
> >
> > I also found a problem on Windows. It seems that BaseTools\Bin\Win32
> > isn't added to %PATH% unless you run edksetup.bat - or, if you're using
> > PowerShell, you can run:
> >
> >
> > $Env:PATH =
> > "$pwd\BaseTools\Bin\Win32$([System.IO.Path]::PathSeparator)$Env:PATH"
> >
> >
> > --
> > Rebecca Cran
> >
> >
> > On 12/24/22 10:37, Rebecca Cran wrote:
> > > Mike,
> > >
> > >
> > > I tried following the "How to build with Stuart" document and ran into
> > > a some issues on my Ubuntu 20.04 system:
> > >
> > >
> > > First, we now need to use "python3.9" on Ubuntu 20.04 since "python3"
> > > is 3.8 which no longer works.
> > >
> > >
> > > Secondly, the loongarch64 gcc download is 930MB - 3.2GB once unpacked.
> > > We might want to add something about specifying "-a LOONGARCH64" etc.
> > > if you want to build it, or '-a X64,AARCH64' etc. if you want to skip
> > > it. I ended up canceling "stuart_update" because I thought it had
> hung.
> > >
> > >
> > > Lastly, the "stuart_update" command listed doesn't work: it seems you
> > > need to specify a TOOL_CHAIN_TAG to have it download anything.
> > >
> > >
>
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 7542 bytes --]
next prev parent reply other threads:[~2022-12-30 7:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1733CB594E21CFEA.12545@groups.io>
2022-12-29 3:47 ` [edk2-devel] edk2-wiki: "How to build with Stuart" - suggested changes/additions Rebecca Cran
2022-12-29 17:22 ` Michael D Kinney
2022-12-30 7:07 ` Sean
2022-12-30 7:24 ` Rebecca Cran [this message]
2023-01-03 15:12 ` Michael Kubacki
2022-12-24 17:37 Rebecca Cran
2022-12-29 17:41 ` [edk2-devel] " Michael D Kinney
2023-01-03 15:42 ` Michael Kubacki
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=7ee92398-4004-9fbf-ce2f-046bc5b92edd@bsdio.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