From: Xue Fuqiao <xfq.free@gmail.com>
To: Mathieu Lirzin <mthl@gnu.org>
Cc: eliz@gnu.org, eggert@cs.ucla.edu, emacs-devel <emacs-devel@gnu.org>
Subject: Re: Switch to Automake?
Date: Mon, 14 Dec 2015 08:34:57 +0800 [thread overview]
Message-ID: <CAAF+z6EhT-oEFJZsJJvmm3fup=d0fqKCmTPpF06s_=WYW2-P6g@mail.gmail.com> (raw)
In-Reply-To: <87bn9ueaaw.fsf@gnu.org>
On Sun, Dec 13, 2015 at 9:40 PM, Mathieu Lirzin <mthl@gnu.org> wrote:
> Hi,
Hi Mathieu,
> In order to improve the maintainability of Emacs and to enforce the
> usage of conventions described by GNU Coding Standards, I think it would
> be a good idea to use Automake in Emacs build system.
Wikipedia says that Emacs uses Automake[1] ;-)
Although IIUC only lib/ (which is imported from Gnulib) uses Automake.
I think documenting the Emacs build system (i.e., how Emacs uses
Autoconf, Make/Automake and Gnulib) is really helpful for developers who
are not familiar with the GNU build system, like me. I'm aware of
`(info "(elisp) Building Emacs")', but it only explains the `temacs'
executable file, the `loadup', `site-load', and `site-init' libraries,
the doc strings in `etc/DOC', and some functions. It doesn't mention
how Emacs uses Autotools.
> Before starting to work on the conversion, I would like to know if such
> change would be accepted. If yes I would like to request some advices
> on how to proceed or comments about any potential issue.
Maybe Paul and Eli can comment on this suggestion. I've added them to Cc.
[1] https://en.wikipedia.org/wiki/Automake#Notable_applications_that_use_Automake
next prev parent reply other threads:[~2015-12-14 0:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-13 13:40 Switch to Automake? Mathieu Lirzin
2015-12-14 0:34 ` Xue Fuqiao [this message]
2015-12-14 3:32 ` Eli Zaretskii
2015-12-14 10:41 ` Mathieu Lirzin
2015-12-14 2:43 ` Paul Eggert
2015-12-15 15:55 ` Mathieu Lirzin
2015-12-14 20:28 ` John Wiegley
2015-12-15 16:15 ` Mathieu Lirzin
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='CAAF+z6EhT-oEFJZsJJvmm3fup=d0fqKCmTPpF06s_=WYW2-P6g@mail.gmail.com' \
--to=xfq.free@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mthl@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 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).