bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org
Cc: Po Lu <luangruo@yahoo.com>
Subject: Android environments
Date: Tue, 27 Dec 2022 08:04:09 +0100	[thread overview]
Message-ID: <3496294.aeNJFYEL58@nimes> (raw)

Po Lu wrote:
> The compilation is done on the host machine that's building Emacs (to
> produce emacs.so), which is then copied to the lib directory in the APK
> package.

I see. There are two ways to build C programs for Android:

  (A) The way it is designed by Google: With the Android NDK,
      that includes a cross-compiler. For the runtime, use an emulator
      (based on qemu) or a physical connection to a real device.

  (B) Inside a terminal emulator app (Termux [1][2] for Android ≥ 7,
      Terminal-IDE [3] for Android < 5).

(A) is a POSIX-like environment only at the C level; it has no shell and no

(B) is a POSIX-like environment including shell and utilities.

For building a real app, the approach (A) is what one needs.

But for building and testing a library, the approach (B) provides
  - an environment that allows to reuse build infrastructure (configure etc.)
    from GNU,
  - faster turnaround cycles.

For Gnulib, we have only used approach (B). We *hope* that the resulting
source code will also work well in situation (A). But when you hit a problem
in situation (A), you are on your own. Because I won't install an NDK and
get into the complexities of cross-compilation, APK packaging, and so on.

> > Again, what is the Android API level that you are using?
> 19.

This is supported with Gnulib, as I have done a lot of testing with Android 4.3
(API level 18).


[1] https://f-droid.org/en/packages/com.termux/
[2] https://wiki.termux.com/wiki/Main_Page
[3] https://www.spartacusrex.com/terminalide.htm

             reply	other threads:[~2022-12-27  7:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-27  7:04 Bruno Haible [this message]
2022-12-27  8:04 ` Android environments Po Lu
2022-12-27 13:56   ` Jeffrey Walton

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:

  List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3496294.aeNJFYEL58@nimes \
    --to=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=luangruo@yahoo.com \


* 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).