From: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
To: help-guix@gnu.org, Julien Lepiller <julien@lepiller.eu>
Subject: Re: Android.mk build system limitations
Date: Sat, 9 Jul 2022 21:17:27 +0200 [thread overview]
Message-ID: <20220709211727.3e823f9a@primarylaptop.localdomain> (raw)
In-Reply-To: <20220709145710.71fc045c@primarylaptop.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1051 bytes --]
On Sat, 9 Jul 2022 14:57:10 +0200
Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> wrote:
> On Wed, 6 Jul 2022 17:20:27 +0200
> Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> wrote:
> > But it then ends up building the first local-module in the
> > local-modules list, many times, and install it with different names.
> In my previous tests https-send-sms was first in both the
> local-modules list and in the BUILD_EXECUTABLE modules in the
> Android.mk.
>
> After some more tests, I found out that it takes the source code from
> the first target in the Android.mk and apparently not from the
> LOCAL_MODULE= argument passed to make.
>
> Though it uses the name of the produced binary from the LOCAL_MODULE=
> argument.
Apparently the issue doesn't seems to be in Guix but in
android-make-stub: android-make-stub seems to be made for only one
target at a time.
A solution would probably be to teach android-make-stub to be able to
only build a given local-module in an Android.mk with many local
modules.
Denis.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-07-09 19:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 15:20 Android.mk build system limitations Denis 'GNUtoo' Carikli
2022-07-09 12:57 ` Denis 'GNUtoo' Carikli
2022-07-09 19:17 ` Denis 'GNUtoo' Carikli [this message]
2022-07-11 7:22 ` Denis 'GNUtoo' Carikli
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220709211727.3e823f9a@primarylaptop.localdomain \
--to=gnutoo@cyberdimension.org \
--cc=help-guix@gnu.org \
--cc=julien@lepiller.eu \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).