Re: [Patch V2] Build spec: add description for build with binary cache

["Gao, Liming" <liming.gao@intel.com>]

Laszlo:
  --binary-destination is to cache the generated binary in this directory, --binary-source is to fetch the cached binary from this directory. If they are used together, the behavior will be same that --hash option only and Build output directory. We don't think it is the necessary usage model. So, we don't add this support. If you have the real case that depends on their combination, we can plan to add it. 

Thanks
Liming
>-----Original Message-----
>From: Laszlo Ersek [mailto:lersek@redhat.com]
>Sent: Thursday, September 28, 2017 8:14 PM
>To: Zhu, Yonghong <yonghong.zhu@intel.com>; edk2-devel@lists.01.org
>Cc: Kinney, Michael D <michael.d.kinney@intel.com>; Shaw, Kevin W
><kevin.w.shaw@intel.com>; Gao, Liming <liming.gao@intel.com>
>Subject: Re: [edk2] [Patch V2] Build spec: add description for build with binary
>cache
>
>On 09/28/17 14:06, Laszlo Ersek wrote:
>
>> So, how can I invalidate all the cached values? Is it enough to delete
>> the *.hash files?
>
>... I'm asking because I tried the --binary-destination option as well,
>and in the bin cache directory, *.depex and *.inf files were stored as
>well, not just *.hash values.
>
>So I figure, whatever gets stored in the binary cache directory, should
>be deleted when I'd like to invalidate the cache.
>
>Now, removing this separate cache directory altogether would solve my
>question; but that would require me to use "--binary-destination" and
>"--binary-source" together. The idea is that "--hash" would fetch the
>hash values from that separate directory, and it would also write the
>new hash values back to that directory. In addition this directory would
>be very easy to remove, so "--hash" would know whenever the hash was
>empty.
>
>However, it looks like "--binary-destination" and "--binary-source"
>cannot be used together. Why is that?
>
>Thanks,
>Laszlo