From: Gunwant Jain <therealgunwant@gmail.com>
To: gentoo-soc@lists.gentoo.org
Subject: Re: [gentoo-soc] Weekly Report: Portage Powered Android
Date: Tue, 14 Jul 2020 10:31:12 +0530 [thread overview]
Message-ID: <20200714050112.o37mtutfe2uxy2oh@tardis.localdomain> (raw)
In-Reply-To: <87k0z7ne66.fsf@robot.e.airelinux.org>
[-- Attachment #1: Type: text/plain, Size: 1141 bytes --]
On 20/07/14 08:17AM, Benda Xu wrote:
> Gunwant Jain <therealgunwant@gmail.com> writes:
>
> > Like I mentioned in my previous off-timed weekly report, I had been
> > working on studying Android's Build Process this week.
> >
> > I have published a blog [1] regarding the same (most of it is just
> > confirmed workflows). I also laid a plan on how to approach building
> > Android on aarch64 host.
>
> That's an excellent write-up.
Thanks !
> > The next two weeks will be focused on that. I will be setting up an
> > ARM based VPS.
>
> What kind of VPS are you planning to set up?
I don't know actually, I was looking for AWS's EC2 A1
https://aws.amazon.com/ec2/instance-types/a1/
but then I realised that the credits which we get from Github's Student
Pack are for _AWS Educate_. AWS does offer a free tier variant, but it
only provides credits worth 30$ at the moment.
> > Once we are through with natively compiling Android, I plan to
> > separate LLVM/Clang toolchain along with Bionic from the AOSP
> > codebase, Bionic here being the tricky part.
>
> Good.
>
> Benda
Regards,
Gunwant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-07-14 5:01 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 23:09 [gentoo-soc] Weekly Report: Portage Powered Android Gunwant Jain
2020-07-14 0:17 ` Benda Xu
2020-07-14 5:01 ` Gunwant Jain [this message]
2020-07-15 1:04 ` Benda Xu
2020-07-15 1:09 ` UnderSampled
2020-07-15 4:55 ` Gunwant Jain
2020-07-15 4:45 ` Pengcheng Xu
2020-07-15 4:58 ` Gunwant Jain
2020-07-15 4:52 ` Gunwant Jain
2020-07-14 4:05 ` Pengcheng Xu
2020-07-14 5:05 ` Gunwant Jain
-- strict thread matches above, loose matches on Subject: below --
2020-08-17 18:05 Gunwant Jain
2020-08-17 23:15 ` Benda Xu
2020-08-20 6:21 ` Gunwant Jain
2020-08-12 1:41 Gunwant Jain
2020-08-12 7:34 ` EBo
2020-08-14 7:26 ` Gunwant Jain
2020-07-30 15:00 Gunwant Jain
2020-07-20 7:40 Gunwant Jain
2020-07-24 14:08 ` Benda Xu
2020-07-24 15:02 ` Gunwant Jain
2020-07-24 17:07 ` UnderSampled
2020-07-24 18:12 ` Gunwant Jain
2020-07-25 3:00 ` Benda Xu
2020-07-25 8:02 ` Gunwant Jain
2020-07-25 8:21 ` Gunwant Jain
2020-07-08 11:39 Gunwant Jain
2020-07-08 13:53 ` Pengcheng Xu
2020-07-09 1:04 ` Benda Xu
2020-06-29 20:12 Gunwant Jain
2020-06-29 21:27 ` EBo
2020-06-30 21:42 ` Gunwant Jain
2020-07-01 2:37 ` EBo
2020-07-01 3:15 ` Gunwant Jain
2020-07-01 12:40 ` Lucas Ramage
2020-07-01 7:17 ` Benda Xu
2020-07-01 16:12 ` Gunwant Jain
2020-07-01 14:07 ` Pengcheng Xu
2020-07-01 16:53 ` Gunwant Jain
2020-07-02 3:50 ` UnderSampled
2020-07-02 12:14 ` Gunwant Jain
2020-06-22 19:15 Gunwant Jain
2020-06-23 4:45 ` Pengcheng Xu
2020-06-23 11:44 ` Gunwant Jain
2020-07-01 7:14 ` Benda Xu
2020-06-15 8:03 Gunwant Jain
2020-07-01 7:10 ` Benda Xu
2020-06-09 11:39 Gunwant Jain
2020-07-01 7:08 ` Benda Xu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200714050112.o37mtutfe2uxy2oh@tardis.localdomain \
--to=therealgunwant@gmail.com \
--cc=gentoo-soc@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox