public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Michael Kubacki" <mikuback@linux.microsoft.com>
To: devel@edk2.groups.io, michael.d.kinney@intel.com,
	"rebecca@bsdio.com" <rebecca@bsdio.com>,
	"Kubacki, Michael" <michael.kubacki@microsoft.com>
Subject: Re: [edk2-devel] edk2-wiki: "How to build with Stuart" - suggested changes/additions
Date: Tue, 3 Jan 2023 10:42:42 -0500	[thread overview]
Message-ID: <eb69fa44-4b83-2e09-b8a2-f0063498a891@linux.microsoft.com> (raw)
In-Reply-To: <CO1PR11MB4929DC0A973EC7213168511BD2F39@CO1PR11MB4929.namprd11.prod.outlook.com>

Please feel free to send a wiki patch or directly make updates.

On 12/29/2022 12:41 PM, Michael D Kinney wrote:
> + Michael Kubacki
> 
>> -----Original Message-----
>> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Rebecca Cran
>> Sent: Saturday, December 24, 2022 9:38 AM
>> To: Kinney, Michael D <michael.d.kinney@intel.com>; devel@edk2.groups.io
>> Subject: [edk2-devel] edk2-wiki: "How to build with Stuart" - suggested changes/additions
>>
>> 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.
>>
I tried to avoid specifying exact versions where possible as they tend 
to get stale quickly. In a case like this, I lean toward pointing to a 
single location where we track the Python version supported and then 
provide a statement that says to use the python command for that version.

Though I'm fine with other approaches that best help people and can try 
to minimize likelihood of misinforming due to staleness over time.

>> 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.
>>
You're right that the instructions do not directly mention the impact of 
the certain flags on the update process. I added that just now.

>> Lastly, the "stuart_update" command listed doesn't work: it seems you
>> need to specify a TOOL_CHAIN_TAG to have it download anything.
>>
You need to specify a tool chain tag to have it download tool chain 
specific binaries. It will download anything that has a scope set (like 
common binaries) irrespective of the tool chain tag. In some cases, the 
default tool chain may either download the required binaries or not 
require any downloads via stuart_update.

I added more info about the impact of parameters on the command just now.
>>
>> --
>> Rebecca Cran
>>
>>
>>
>>
>>
> 
> 
> 
> 
> 
> 

  reply	other threads:[~2023-01-03 15:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-24 17:37 edk2-wiki: "How to build with Stuart" - suggested changes/additions Rebecca Cran
2022-12-29 17:41 ` [edk2-devel] " Michael D Kinney
2023-01-03 15:42   ` Michael Kubacki [this message]
     [not found] <1733CB594E21CFEA.12545@groups.io>
2022-12-29  3:47 ` Rebecca Cran
2022-12-29 17:22   ` Michael D Kinney
2022-12-30  7:07     ` Sean
2022-12-30  7:24       ` Rebecca Cran
2023-01-03 15:12         ` 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=eb69fa44-4b83-2e09-b8a2-f0063498a891@linux.microsoft.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