From: Jean-Christophe Helary <jean.christophe.helary@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: building emacs
Date: Wed, 31 May 2017 19:52:31 +0900 [thread overview]
Message-ID: <4FB0DC2E-14DD-49A0-9F66-8C4FA707FABE@gmail.com> (raw)
I'm building emacs with
./configure --with-ns
make install
When I update my git repository (presumably with git pull origin master), do I need to reconfigure the build with the command *each time* I update the code ? Or can I proceed directly to make install ?
Also, are there ways to do incremental builds ? Where only the modified parts are built and the rest stays as it were ?
Jean-Christophe
next reply other threads:[~2017-05-31 10:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 10:52 Jean-Christophe Helary [this message]
2017-05-31 11:19 ` building emacs Tim Visher
2017-05-31 11:24 ` Jean-Christophe Helary
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=4FB0DC2E-14DD-49A0-9F66-8C4FA707FABE@gmail.com \
--to=jean.christophe.helary@gmail.com \
--cc=help-gnu-emacs@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.
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).