From: "Steven Shi" <steven.shi@intel.com>
To: "Gao, Liming" <liming.gao@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Chiu, Chasel" <chasel.chiu@intel.com>,
"Lu, Shifei A" <shifei.a.lu@intel.com>,
"Bi, Dandan" <dandan.bi@intel.com>,
"Kubacki, Michael A" <michael.a.kubacki@intel.com>
Subject: Re: [PATCH 0/2] Add batch option to support build Binary Cache
Date: Thu, 9 May 2019 04:07:50 +0000 [thread overview]
Message-ID: <06C8AB66E78EE34A949939824ABE2B313FFB749E@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E445616@SHSMSX104.ccr.corp.intel.com>
Hi Liming,
User can override the BinCache by set BINARY_CACHE_PATH environment variable, see below code in the patch. The BinCache is only used if user doesn't set the binary cache path variable.
+@if not defined BINARY_CACHE_PATH (
+ echo Info: BINARY_CACHE_PATH is empty, use BinCache as default
+ SET BINARY_CACHE_PATH=BinCache
+)
+
Thanks
Steven Shi
> -----Original Message-----
> From: Gao, Liming
> Sent: Thursday, May 9, 2019 11:37 AM
> To: Shi, Steven <steven.shi@intel.com>; devel@edk2.groups.io
> Cc: Chiu, Chasel <chasel.chiu@intel.com>; Lu, Shifei A <shifei.a.lu@intel.com>;
> Bi, Dandan <dandan.bi@intel.com>; Kubacki, Michael A
> <michael.a.kubacki@intel.com>
> Subject: RE: [PATCH 0/2] Add batch option to support build Binary Cache
>
> Steven:
> Could you let user specify BinCache directory instead of hard code name?
>
> Thanks
> Liming
> > -----Original Message-----
> > From: Shi, Steven
> > Sent: Thursday, May 9, 2019 11:21 AM
> > To: devel@edk2.groups.io
> > Cc: Chiu, Chasel <chasel.chiu@intel.com>; Lu, Shifei A
> <shifei.a.lu@intel.com>; Gao, Liming <liming.gao@intel.com>; Bi, Dandan
> > <dandan.bi@intel.com>; Kubacki, Michael A <michael.a.kubacki@intel.com>
> > Subject: [PATCH 0/2] Add batch option to support build Binary Cache
> >
> > This patch serial is to extend the options in the Kabylake and Purley
> > build batch file to support build Binary Cache produce and consume switch.
> >
> >
> > Steven Shi (2):
> > KabylakeOpenBoardPkg/KabylakeRvp3: Extend build to support Binary
> > Cache
> > PurleyOpenBoardPkg/BoardMtOlympus: Extend build to support Binary
> > Cache
> >
> > .../KabylakeOpenBoardPkg/KabylakeRvp3/bld.bat | 24 +++++++++++++++++-
> -
> > .../PurleyOpenBoardPkg/BoardMtOlympus/bld.bat | 18 ++++++++++++--
> > .../BoardMtOlympus/prebuild.bat | 4 ++--
> > 3 files changed, 40 insertions(+), 6 deletions(-)
> >
> > --
> > 2.17.1.windows.2
next prev parent reply other threads:[~2019-05-09 4:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 3:21 [PATCH 0/2] Add batch option to support build Binary Cache Steven Shi
2019-05-09 3:21 ` [PATCH 1/2] KabylakeOpenBoardPkg/KabylakeRvp3: Extend build to support " Steven Shi
2019-05-09 3:21 ` [PATCH 2/2] PurleyOpenBoardPkg/BoardMtOlympus: " Steven Shi
2019-05-10 5:12 ` Lu, Shifei A
2019-05-10 5:43 ` Chiu, Chasel
2019-05-09 3:37 ` [PATCH 0/2] Add batch option to support build " Liming Gao
2019-05-09 4:07 ` Steven Shi [this message]
2019-05-10 17:14 ` Kubacki, Michael A
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=06C8AB66E78EE34A949939824ABE2B313FFB749E@shsmsx102.ccr.corp.intel.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