From: Jean-Christophe Helary <jean.christophe.helary@gmail.com>
To: Tim Visher <tim.visher@gmail.com>
Cc: emacs <help-gnu-emacs@gnu.org>
Subject: Re: building emacs
Date: Wed, 31 May 2017 20:24:03 +0900 [thread overview]
Message-ID: <E6BC2AD9-80F0-4CA5-A0B2-7D1CDFC002CB@gmail.com> (raw)
In-Reply-To: <CAHa53uzgsA86x89H-gfHuWZ6i6Yj8oKfxK5DQ-NpnfD+QHk=MA@mail.gmail.com>
> On May 31, 2017, at 20:19, Tim Visher <tim.visher@gmail.com> wrote:
>
> I'm not an authoritative source but:
>
> 1. I'd generally always run ./configure again no matter what the software is unless I absolutely knew the ins and outs of the configure script and knew nothing had changed.
OK.
> 2. make is an incremental build system generally, though emacs use of it might not be such. Have you tested it? Just run make and then modify a single source file and run make again and see what happens.
I did build emacs twice today and the second time did not feel noticeably shorter than the first. But I'll check again. I thought maybe there was a parameter to make to have it work incrementally.
Thank you.
Jean-Christophe
next prev parent reply other threads:[~2017-05-31 11:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 10:52 building emacs Jean-Christophe Helary
2017-05-31 11:19 ` Tim Visher
2017-05-31 11:24 ` Jean-Christophe Helary [this message]
2017-05-31 11:26 ` Eli Zaretskii
2017-05-31 11:41 ` Jean-Christophe Helary
2017-05-31 12:09 ` Emanuel Berg
2017-05-31 13:22 ` Skip Montanaro
2017-05-31 14:00 ` Emanuel Berg
2017-06-01 7:19 ` Shakthi Kannan
2017-06-01 13:36 ` Jean-Christophe Helary
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=E6BC2AD9-80F0-4CA5-A0B2-7D1CDFC002CB@gmail.com \
--to=jean.christophe.helary@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=tim.visher@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.
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).