all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mathieu Lirzin <mthl@gnu.org>
To: Xue Fuqiao <xfq.free@gmail.com>
Cc: eliz@gnu.org, eggert@cs.ucla.edu, emacs-devel <emacs-devel@gnu.org>
Subject: Re: Switch to Automake?
Date: Mon, 14 Dec 2015 11:41:00 +0100	[thread overview]
Message-ID: <87bn9te2ir.fsf@gnu.org> (raw)
In-Reply-To: <CAAF+z6EhT-oEFJZsJJvmm3fup=d0fqKCmTPpF06s_=WYW2-P6g@mail.gmail.com> (Xue Fuqiao's message of "Mon, 14 Dec 2015 08:34:57 +0800")

Hi Xue,

Xue Fuqiao <xfq.free@gmail.com> writes:

> On Sun, Dec 13, 2015 at 9:40 PM, Mathieu Lirzin <mthl@gnu.org> wrote:
>
>> 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.

Yes I should have mentioned that it was already used partially.  :)

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

I agree that this would help.  Since Automake is well documented, It
would be possible to document the Emacs build system by linking to the
related parts in Automake manual for generic stuff, and describe more
precisely Emacs idiosyncrasies.

> Maybe Paul and Eli can comment on this suggestion.  I've added them to Cc.

Thanks,

--
Mathieu Lirzin



  parent reply	other threads:[~2015-12-14 10:41 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
2015-12-14  3:32   ` Eli Zaretskii
2015-12-14 10:41   ` Mathieu Lirzin [this message]
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

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

  git send-email \
    --in-reply-to=87bn9te2ir.fsf@gnu.org \
    --to=mthl@gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=xfq.free@gmail.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.