1 |
Hey Everyone ! |
2 |
|
3 |
I was about to give a coherent report for what I have been doing for 2 |
4 |
weeks next week, but my mentor suggested to explain my findings briefly. |
5 |
|
6 |
I found out that AOSP has actually been phasing out of using GCC in |
7 |
favour to Clang/LLVM based toolchains. And so, from the last time I |
8 |
gave in my weekly report, I have been checking up on llvm_android [1], |
9 |
the source of the toolchain which AOSP uses to build itself. |
10 |
|
11 |
I built the toolchain for x86 host using the original scripts AOSP |
12 |
provides and found out that they in terms of Bionic (Android's libc), |
13 |
they only copy Bionic's headers, compiles Clang for different targets |
14 |
using a prebuilt toolchain bundled with the entire package. |
15 |
|
16 |
Later, when we build Android, the prebuilt toolchain compiles Bionic and |
17 |
uses it as intermediatories to compile the other bulk of Android |
18 |
(frameworks, etc.). |
19 |
|
20 |
My main objective I think would be to introduce a aarch64 host config |
21 |
for llvm_android, and integrate the toolchain in the AOSP build process. |
22 |
Take this with a grain of salt, as I believe I should put more research |
23 |
into this first, which is why I was taking another week. |
24 |
|
25 |
I would probably write a detailed blog documenting AOSP's build process |
26 |
by the end of this working week, covering everything we need to proceed. |
27 |
|
28 |
|
29 |
Regards, |
30 |
Gunwant |
31 |
|
32 |
[1] https://android.googlesource.com/toolchain/llvm_android/ |