From: Rebecca Cran <rebecca@bluestop.org>
To: "Gao, Liming" <liming.gao@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Lu, ShifeiX A" <shifeix.a.lu@intel.com>,
"Zimmer, Vincent" <vincent.zimmer@intel.com>,
"Wei, David" <david.wei@intel.com>, Andrew Fish <afish@apple.com>,
"Gao, Liming" <liming.gao@intel.com>
Subject: Re: Improvements to build system etc. for edk2-platforms devel-MinnowBoard3?
Date: Tue, 21 Feb 2017 22:48:17 -0700 [thread overview]
Message-ID: <95a8d930-6bb2-e666-1957-8d78a25efd10@bluestop.org> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14D6E27B3@shsmsx102.ccr.corp.intel.com>
On 2/21/2017 9:50 PM, Gao, Liming wrote:
> Could you introduce what change will be done for build improvement? I am also interested in this topic.
The first change I'd make is to set 'buildthreads' in BuildBIOS to
%NUMBER_OF_PROCESSORS% - that by itself reduces the build time from
around 7 minutes to 2.5 on my system. I also have some changes to the
ReadMe.MD file to convert it to be a MD file instead of plain text,
which massively increases readability on GitHub. I've also been
wondering about allowing more parameters to be passed through to 'build'
such as reducing the verbosity to make compiler warnings more apparent.
Finally, and this is likely more controversial - I've been wondering if
the build scripts like BuildBIOS should be in python instead of Windows
.cmd/.bat since python is already used elsewhere and is more flexible.
--
Rebecca
next prev parent reply other threads:[~2017-02-22 5:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 1:20 Improvements to build system etc. for edk2-platforms devel-MinnowBoard3? Rebecca Cran
2017-02-22 4:50 ` Gao, Liming
2017-02-22 5:11 ` Andrew Fish
2017-02-22 5:48 ` Rebecca Cran [this message]
2017-02-22 7:35 ` Gao, Liming
2017-02-22 16:34 ` Richardson, Brian
2017-02-22 16:52 ` Rebecca Cran
2017-02-22 19:10 ` Richardson, Brian
2017-02-23 2:49 ` Wei, David
2017-02-23 18:53 ` Brian J. Johnson
2017-02-23 19:10 ` Rebecca Cran
2017-02-23 23:11 ` Richardson, Brian
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=95a8d930-6bb2-e666-1957-8d78a25efd10@bluestop.org \
--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