From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Christian Stewart <christian@paral.in>
Cc: "Yann E . MORIN" <yann.morin.1998@free.fr>,
Christian Stewart via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [RFC PATCH v1 1/1] package/android-tools: update to version 5.1.1.r38
Date: Fri, 29 Jul 2022 11:42:51 +0200 [thread overview]
Message-ID: <20220729114251.217a4104@windsurf> (raw)
In-Reply-To: <CA+h8R2rq1GonYRs0o=BN_gcJnJwYCVosjY9FEeZs-3os97Kt8w@mail.gmail.com>
Hello Christian,
On Thu, 28 Jul 2022 08:24:18 -0700
Christian Stewart <christian@paral.in> wrote:
> ACK on your comments.
>
> However, I think even this updated version is still extremely old.
>
> It doesn't have all of the arguments like --page-size or even --version
>
> The Gentoo package reports version 31.0.3-android-tools
>
> That's way way way more recent than 5.x, right?
>
> I'm a bit confused on these version schemes.
>
> https://github.com/nmeum/android-tools
I have no idea how this is maintained. It's probably a bit crappy as
this is forked from the Android code base. So far, we were using the
android-tools packaged in Ubuntu, therefore available on Launchpad.
This other Github repository you're pointing to perhaps uses a
different version scheme.
> This package has a Cmake version of building it which seems much
> cleaner, and also brings in all the other tools like simg.
>
> To be able to build it, it requires using the Git submodules method:
>
> ANDROID_TOOLS_VERSION = 31.0.3p1
> ANDROID_TOOLS_SITE = https://github.com/nmeum/android-tools
> ANDROID_TOOLS_SITE_METHOD = git
> ANDROID_TOOLS_LICENSE = Apache-2.0
> ANDROID_TOOLS_GIT_SUBMODULES = YES
>
> And carries its own patches for adb, etc.
>
> Would it be desirable to switch to this version instead? I certainly
> would prefer it for my purposes.
This seems like a reasonable solution. I see that a Go compiler is
needed. Is it because the android tools developed by Google are now
written in Go?
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-07-29 9:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-24 23:47 [Buildroot] [RFC PATCH v1 1/1] package/android-tools: update to version 5.1.1.r38 Christian Stewart via buildroot
2022-07-26 17:11 ` Thomas Petazzoni via buildroot
2022-07-28 15:24 ` Christian Stewart via buildroot
2022-07-29 9:42 ` Thomas Petazzoni via buildroot [this message]
2022-07-31 22:59 ` Christian Stewart via buildroot
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=20220729114251.217a4104@windsurf \
--to=buildroot@buildroot.org \
--cc=christian@paral.in \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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