From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: Xue Fuqiao <xfq.free@gmail.com>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: What should I do when building Emacs again with different configure options?
Date: Sun, 28 Jul 2013 00:53:01 +0200 [thread overview]
Message-ID: <E2461E30-7C88-4F5C-AD70-102C23C96CC0@Web.DE> (raw)
In-Reply-To: <CAAF+z6E3cLVV684Nz9D9xeLABvQZiXHLMG-XozgnHgr7PMgYDQ@mail.gmail.com>
Am 28.07.2013 um 00:30 schrieb Xue Fuqiao:
> So could we remove the "./configure"?
No! Without invoking configure at least once after the 'make distclean' or out-packing the sources no Makefile is there and so GNU Emacs cannot be built. The configure run creates the Makefiles in the top level directory and in sub-directories with some kind of sources that need to be compiled to something more useful – these are for example the TEXI or LISP files, which become INFO or ELC files – and the 'make distclean' removes these Makefiles. It might be useful to document that configure can be invoked with arguments to prepare an optimised build. And that the build/install options can be retrieved by invoking "./configure --help"?
Or, if you want to remove something from the INSTALL file, then I'd recommend
* intlfonts-VERSION.tar.gz
These are pretty old bitmapped fonts. They cannot be used with GNU Emacs' font shaping capabilities. The GNU Freefonts (FreeSerif, FreeSans, FreeMono) exist and offer support for many scripts and languages.
--
Greetings
Pete
Either this man is dead or my watch has stopped.
- Groucho Marx
next prev parent reply other threads:[~2013-07-27 22:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-27 1:59 What should I do when building Emacs again with different configure options? Xue Fuqiao
2013-07-27 2:06 ` Glenn Morris
2013-07-27 22:30 ` Xue Fuqiao
2013-07-27 22:53 ` Peter Dyballa [this message]
2013-07-28 13:38 ` Xue Fuqiao
2013-07-28 2:03 ` Hongxu Chen
2013-07-28 8:39 ` Thien-Thi Nguyen
2013-07-28 13:33 ` Xue Fuqiao
2013-07-28 15:19 ` Thien-Thi Nguyen
2013-07-28 15:44 ` Peter Dyballa
2013-07-28 22:56 ` Xue Fuqiao
2013-07-28 23:47 ` Glenn Morris
2013-07-29 1:32 ` Xue Fuqiao
2013-07-28 13:50 ` Xue Fuqiao
2013-07-27 9:17 ` Peter Dyballa
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=E2461E30-7C88-4F5C-AD70-102C23C96CC0@Web.DE \
--to=peter_dyballa@web.de \
--cc=help-gnu-emacs@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.
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).