unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: j.e.widen@gmail.com, 65207@debbugs.gnu.org
Subject: bug#65207: 30.0; More instructions for how to build Android emacs, are needed
Date: Thu, 10 Aug 2023 20:25:01 +0300	[thread overview]
Message-ID: <83a5uyizde.fsf@gnu.org> (raw)
In-Reply-To: <s0dleejuenu.fsf@yahoo.com> (bug-gnu-emacs@gnu.org)

> Cc: 65207@debbugs.gnu.org
> Date: Thu, 10 Aug 2023 22:59:17 +0800
> From:  Po Lu via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> Johan Widén <j.e.widen@gmail.com> writes:
> 
> > First I suggest that the emacs repo top level README or INSTALL
> > should include a reference to java/INSTALL. Perhaps something like
> > this: 
> >
> > * For instructions on how to build Android emacs, see .
> >  /java/INSTALL.
> 
> Eli already did this, I think.

Yes, INSTALL now says near its beginning:

  This file contains general information on building GNU Emacs.  If you
  are building an Emacs release tarball on a Unix or a GNU system, the
  instructions in this file should be sufficient.  For other
  configurations, we have additional specialized files:

    . INSTALL.REPO if you build from a Git checkout
    . nt/INSTALL if you build for MS-Windows
    . nextstep/INSTALL if you build for GNUstep/macOS
    . java/INSTALL if you build for Android
    . msdos/INSTALL if you build for MS-DOS





      reply	other threads:[~2023-08-10 17:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-10  9:23 bug#65207: 30.0; More instructions for how to build Android emacs, are needed Johan Widén
2023-08-10 14:59 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-10 17:25   ` Eli Zaretskii [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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=83a5uyizde.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=65207@debbugs.gnu.org \
    --cc=j.e.widen@gmail.com \
    --cc=luangruo@yahoo.com \
    /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/emacs.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).