1 |
Hey Stephen, |
2 |
|
3 |
I took a brief look at GloDroid. It looks like just another AOSP tree but |
4 |
with support for more devices like you mentioned. |
5 |
But SharkBait aims to build Android on the device itself, the flavour of |
6 |
Android should not matter. And for the same reasons, I chose Lineage's |
7 |
tree because of the massive device support it has. |
8 |
|
9 |
To implement SharkBait, we will have to swap the toolchains AOSP offers |
10 |
with the ones supporting aarch64 host. Once that is sorted out, we could, |
11 |
in theory, implement any flavour of AOSP, be it glodroid, or any other |
12 |
fork, just by tracking SharkBait's toolchain sources. |
13 |
|
14 |
On top of that SharkBait aims also to separate the AOSP modules and |
15 |
provide updates via Portage. But I predict that this would be SharkBait |
16 |
specific. |
17 |
|
18 |
Targeting newer devices like the PinePhone would be like the normal way |
19 |
AOSP forks like Lineage extend support to newer devices. I agree on a |
20 |
PinePhone target. |
21 |
|
22 |
Once again, I thank you for offering me help in getting such devices. |
23 |
But I would politely ask for you to wait until I implement SharkBait on |
24 |
a phone first (the Lineage sources for my phone are easily available). |
25 |
Benda offered me an arm64 server for the project, I think that would be |
26 |
enough to work on, once I succeed in building the toolchain (or fail to |
27 |
do so because of hardware limitations). |
28 |
|
29 |
Thanks, |
30 |
Gunwant |
31 |
|
32 |
|
33 |
|
34 |
On 20/07/24 01:07PM, UnderSampled wrote: |
35 |
> You may find this useful: https://glodroid.github.io/ |
36 |
> This is a modern AOSP tree for OrangePi, RaspberryPi, and Pine64 devices. That includes the Pinebook and PinePhone: https://www.pine64.org/. |
37 |
> |
38 |
> I can get you one of these devices if you think it could help. |
39 |
> |
40 |
> We should definitely consider targeting a build of Shark Bait for the PinePhone. |
41 |
> |
42 |
> |
43 |
> On July 24, 2020 11:02:57 AM EDT, Gunwant Jain <therealgunwant@×××××.com> wrote: |
44 |
> >On 20/07/24 10:08PM, Benda Xu wrote: |
45 |
> >> Gunwant Jain <therealgunwant@×××××.com> writes: |
46 |
> >> |
47 |
> >> > This week, I started managing the structure for the modified |
48 |
> >LineageOS |
49 |
> >> > fork we would keep. Namely the modified `repo-manifest` [1] and |
50 |
> >> > `llvm_android` [2], for now. No patches have been applied to them |
51 |
> >yet |
52 |
> >> > for the reasons discussed below. |
53 |
> >> > |
54 |
> >> > My plan for this week was to start with patching the `llvm_android` |
55 |
> >> > build scripts. Android uses a prebuilt Clang (bundled with the |
56 |
> >repo) |
57 |
> >> > among other stuff to build the toolchain. So I had to emerge Clang |
58 |
> >on my |
59 |
> >> > phone. |
60 |
> >> > Emerging Clang turned out not to be a breeze when I have a phone |
61 |
> >with 3 |
62 |
> >> > gigs of RAM. So for about the longest time, I was busy trying to |
63 |
> >make up |
64 |
> >> > for it. I tried setting up distcc, increased swap/zram, but still |
65 |
> >the |
66 |
> >> > OOM killer got me. |
67 |
> >> > Later last night(/day), I came across the tips for building |
68 |
> >clang/gcc in |
69 |
> >> > an embedded Android environment at [3]. So I followed that and as |
70 |
> >of |
71 |
> >> > now, me writing the mail, OOM has not got me, Clang is emerging. |
72 |
> >> |
73 |
> >> Did it finally go through? |
74 |
> > |
75 |
> >Yes it did. |
76 |
> >I can also report that llvm_android's stage1 clang is compiled for |
77 |
> >aarch64, I am on the stage2 step currently. |
78 |
> > |
79 |
> > |
80 |
> >Regards, |
81 |
> >Gunwant |
82 |
> |
83 |
> -- |
84 |
> Sent from my Android device with K-9 Mail. Please excuse my brevity. |