public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Sean" <spbrogan@outlook.com>
To: devel@edk2.groups.io, rebecca@bsdio.com
Subject: Re: [edk2-devel] Official way to build BaseTools - Edk2ToolsBuild.py?
Date: Tue, 19 May 2020 20:36:55 -0700	[thread overview]
Message-ID: <BN8PR07MB69621C6BE495449E84BAE918C8B60@BN8PR07MB6962.namprd07.prod.outlook.com> (raw)
In-Reply-To: <5eed935b-7a4c-dffb-0643-d7bcf8499202@bsdio.com>

I am not sure what the community wants to do with it.  It was created 
for the CI build so it is tailored to the needs of the CI build but I 
have no problem with updates.

I agree with your feedback and see no reason either of those would be a 
problem for the CI use case.

Although not convenient for local builds it does currently output full 
build log to BaseTools/BaseToolsBuild/BASETOOLS_BUILD.txt.

Thanks
Sean






On 5/19/2020 8:23 PM, Rebecca Cran wrote:
> I'm wondering if using BaseTools/Edk2ToolsBuild.py will become the 
> official/standard way users are expected to build BaseTools? If so, 
> there are a few problems that I'd like to see fixed, which I'll see if I 
> can find some time to work on.
> 
> 
> For example: on Linux, running it without arguments gives "ValueError: 
> Bad VC" - because it defaults to the VS2017 toolchain.
> 
> If you break something in BaseTools and so it fails to build, it prints 
> "Exception: Failed to build." with no further details.
> 
> 
> I'd like to improve it so it detects being run on a non-Windows platform 
> and tries to use GCC, Clang etc. - and perhaps also to add a '--verbose' 
> argument that can be used to give a more specific error message when it 
> fails.
> 
> 

  reply	other threads:[~2020-05-20  3:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-20  3:23 Official way to build BaseTools - Edk2ToolsBuild.py? Rebecca Cran
2020-05-20  3:36 ` Sean [this message]
2020-05-20  8:42   ` [edk2-devel] " Philippe Mathieu-Daudé

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=BN8PR07MB69621C6BE495449E84BAE918C8B60@BN8PR07MB6962.namprd07.prod.outlook.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