From: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
To: Julien Lepiller <julien@lepiller.eu>
Cc: 42734@debbugs.gnu.org
Subject: [bug#42734] Export android-platform-system-core
Date: Mon, 10 Aug 2020 05:19:49 +0200 [thread overview]
Message-ID: <20200810051949.737d799e@primarylaptop.localdomain> (raw)
In-Reply-To: <13A86DDA-5411-495A-B6AC-042A9F932065@lepiller.eu>
[-- Attachment #1: Type: text/plain, Size: 2097 bytes --]
On Fri, 07 Aug 2020 07:33:03 -0400
Julien Lepiller <julien@lepiller.eu> wrote:
> Unfortunately, android-platform-core should first be fixed to accept
> a hash as an argument, otherwise any other version will fail. Don't
> know why we haven't done that before…
I don't understand what the hash would be here, nor the consequences
you describe. Do you have some pointers on the documentation or source
code that I should read to better understand that?
By the way I find it a bit strange to refer to have to manually extract
android-platform-system-core to be able to refer its include path.
Beside the native-input, this results in the following code:
> #:make-flags (list (string-append "CFLAGS= "
> "-I core/include "
> [...]))
>
> [...]
>
> #:phases
> (modify-phases %standard-phases
> (add-after 'unpack 'unpack-core
> (lambda* (#:key inputs #:allow-other-keys)
> (mkdir-p "core")
> (with-directory-excursion "core"
> (invoke "tar" "axf" (assoc-ref inputs "android-core")
> "--strip-components=1"))
> #t))
> [...])
Instead of just that:
> #:make-flags (list (string-append "CFLAGS= "
> "-I " (assoc-ref %build-inputs "android-core")
> "/include "))
> [...]))
Another potential improvement would be to remove the
android-platform-version argument completely and set version to it in
android.mk like that:
> (define-public (android-platform-system-core
> [...]
> (version (android-platform-version))
> [...]
That would make the native-input look like that:
> (native-inputs
> `(
> ("android-core" ,android-platform-system-core)))
And if we need the version 9.0.0_r3 we could define a new package:
> (define-public android-platform-system-core-9
> (package
> (inherit android-platform-system-core)
> (version "9.0.0_r3"))))
and use it:
> (native-inputs
> `(
> ("android-core" ,android-platform-system-core-9)))
Are both proposal a good idea? Or does it have any downsides that I
didn't think of?
Denis.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-08-10 3:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 0:44 [bug#42734] Export android-platform-system-core Denis 'GNUtoo' Carikli
2020-08-07 2:10 ` [bug#42734] [PATCH 1/2] gnu: android: Export android-platform-version Denis 'GNUtoo' Carikli
2020-08-07 2:10 ` [bug#42734] [PATCH 2/2] gnu: android: Export android-platform-system-core Denis 'GNUtoo' Carikli
2020-08-07 8:24 ` bug#42734: [PATCH 1/2] gnu: android: Export android-platform-version Mathieu Othacehe
2020-08-07 11:33 ` [bug#42734] Export android-platform-system-core Julien Lepiller
2020-08-10 3:19 ` Denis 'GNUtoo' Carikli [this message]
2020-08-10 3:27 ` Denis 'GNUtoo' Carikli
2020-08-10 3:46 ` Denis 'GNUtoo' Carikli
2020-08-10 13:50 ` Julien Lepiller
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=20200810051949.737d799e@primarylaptop.localdomain \
--to=gnutoo@cyberdimension.org \
--cc=42734@debbugs.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).