From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 0/3] Fix two android-tools build issues
Date: Wed, 4 Dec 2024 22:52:48 +0100 [thread overview]
Message-ID: <20241204225248.065dbf00@windsurf> (raw)
In-Reply-To: <43db1477-708a-44fb-8cf9-ef418d376045@mind.be>
On Wed, 4 Dec 2024 22:48:11 +0100
Arnout Vandecappelle <arnout@mind.be> wrote:
> Series applied to master,thanks. Though I don't like the "we're too far from
> upstream" part too much :-)
Me neither of course... but that android-tools stuff is really really
far from upstream. I recently discovered
https://github.com/nmeum/android-tools/ which seems to be an attempt
at having a "common" place for a CMake build system for those
android-tools.
They also have lots of patches, though:
https://github.com/nmeum/android-tools/tree/master/patches
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
prev parent reply other threads:[~2024-12-04 21:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 20:47 [Buildroot] [PATCH 0/3] Fix two android-tools build issues Thomas Petazzoni via buildroot
2024-12-04 20:48 ` [Buildroot] [PATCH 1/3] package/android-tools: convert all patches to Git-formatted patches Thomas Petazzoni via buildroot
2024-12-06 22:44 ` Peter Korsgaard
2024-12-04 20:48 ` [Buildroot] [PATCH 2/3] package/android-tools: fix build issue on mips64 and powerpc64 Thomas Petazzoni via buildroot
2024-12-06 22:44 ` Peter Korsgaard
2024-12-04 20:48 ` [Buildroot] [PATCH 3/3] package/android-tools: fix b64_pton() issue with GCC >= 14.x Thomas Petazzoni
2024-12-06 22:44 ` Peter Korsgaard
2024-12-04 21:48 ` [Buildroot] [PATCH 0/3] Fix two android-tools build issues Arnout Vandecappelle via buildroot
2024-12-04 21:52 ` Thomas Petazzoni [this message]
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=20241204225248.065dbf00@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=arnout@mind.be \
--cc=buildroot@buildroot.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.