performance - Android ccache sharing among workspaces -
I'm using a workspace designed to use other workspace Sikas would like to share, so that Sikas data A copy of the same source code to be used to compile.
Ex: 1) A workspace (home / user / source_code1) has been created. 2) server has been synchronized code here 3) USE_CCACHE = 1
Code went compiled as I am now I have the following
Case 1: 1) a workspace (Home / User / Source_code 2) has been created. 2) The same source code is integrated from the server 3) The same compilation as I did earlier in the workspace.
Case 2: 1) Delete Workspace home / user / source_code1 2) Rebuild the first workspace (home / user / source code 1). 2) synced again address the server is compiled code with 3) USE_CCACHE = 1
would like to use ccache designed source_code1 up I want source_code2 compilation and when I have the same scope Remove and re-create, then I need to compile the cache with the already created cache.
The result is that I am now seeing in both cases above, even though this cache has been created, it has never been used or any hit is not it, whenever it is making a new workspace is used, if I have any old source code (home / user / Srot_ code1) clean only construction and re-compile the same workspace without deleting am, then jumps ccache compilation and hit that A To be used to help make
There is also the idea that even when using a new workspace is not see me hit any catches?
I always have "cash hit" (direct), or, cash hit (preprocessed). Besides "Cash Hit" is always 0.
I have the following variables are determined.
CCACHE_BASEDIR = / home / user USE_CCACHE = 1 Sisiaacamdiaiar = / home / user / ccache CCACHE_SLOPPINESS = time_macros, file_macro Please Tell me that I'm missing something here.
Ccache must replace. 3.x or above.
I know, well in Android source are included in the tree seek. 2.4. and CCACHE_BASEDIR ccache working 3.x You can refer to the link below.
The Android Build script will use their pre-built tools, not your system was installed. / P>
Comments
Post a Comment