all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: guix-devel <guix-devel@gnu.org>
Subject: Android build-tools / prebuild / soong
Date: Mon, 16 Oct 2017 20:39:27 +0200	[thread overview]
Message-ID: <e9f2360f-4707-28d1-8aeb-fa8cfff320a6@crazy-compilers.com> (raw)

Hi,

maybe somebody want to work in this puzzle :-)

Last week I played around upgrading the android libs and tools to the
current release 8.0.0_r17, when I realized that the build-system has
switched from a Makefile-base to one based on "Android.mk" files. These
are meant to be processed by a tool called "soong" (with two `o`).

soong is based on "ninja" an "Blueprint". There are no
build-instructions and no usage examples. So I asked on the
android-building mailinglist how to build and use soong stand-alone. I
got the answer that this is not indented but to be build like this
(fixed by my):

guix environment --ad-hoc repo
repo init -u https://android.googlesource.com/platform/manifest -b
build-tools
repo sync -j32
mkdir OUT
OUT_DIR=OUT prebuilts/build-tools/build-prebuilts.sh

So the script in the last line is the key. It looks acceptable, but I
have no clue about how go programs are build normally. So for me solving
this puzzle is quite time-consuming and I may not be able to work on it
for quite some time. Anybody to take over?

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |

             reply	other threads:[~2017-10-16 18:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-16 18:39 Hartmut Goebel [this message]
2017-10-18  2:36 ` Android build-tools / prebuild / soong Maxim Cournoyer
2017-10-18  8:33   ` Hartmut Goebel

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=e9f2360f-4707-28d1-8aeb-fa8cfff320a6@crazy-compilers.com \
    --to=h.goebel@crazy-compilers.com \
    --cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

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.