Well, you are already using version ccache 3.1.9 in Oreo release -
https://android.googlesource.com/platform/prebuilts/misc/+/85bf1819a733f1c5c87e1a1574e52badf9abfa56/linux-x86/ccache/
which as I currently see is licensed under GPL 3 or higher.
I wonder if I'm missing something.
On Tuesday,
ccache changed its license to GPL3, so we are unlikely to upgrade.
On Mon, Sep 4, 2017 at 10:58 PM,
wrote:
> Hello,
> And if I got all that I said in the previous email correct, then,
> from ccache point of view, the fix is to use newer ccache version -
>
Hello,
And if I got all that I said in the previous email correct, then,
from ccache point of view, the fix is to use newer ccache version -
https://ccache.samba.org/releasenotes.html#_ccache_3_3
I'm curious to know if AOSP O r4 branch has any plans to user newer ccache.
regards,
Venkat.
On
Hello,
I suspect a potential side-effect when Ninja, and ccache(shared with
multiple users on a workstation) are working together.
Consider the following scenario. This assumes a shared cache(CCACHE_DIR set
to /ccache/common_cachestore) for both the users.
User A runs a build under /ws/aosp_A