all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dan Mack <mack@macktronics.com>
To: Robert Thorpe <rt@robertthorpeconsulting.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Compiling Emacs from Source
Date: Wed, 08 Nov 2017 10:32:33 -0600	[thread overview]
Message-ID: <m2tvy4buji.fsf@pandora.lan> (raw)
In-Reply-To: <87d14w4byu.fsf@robertthorpeconsulting.com> (Robert Thorpe's message of "Sun, 05 Nov 2017 22:06:33 +0000")

Robert Thorpe <rt@robertthorpeconsulting.com> writes:

> Recently there was some discussion about upgrading Emacs.  Package
> managers and distros were discussed.
>
> I have a more basic question.  The distro I'm using doesn't provide
> Emacs 25, I'm still on 24.4.  So, I want to compile Emacs 25.
>
> The problem for me is the configuration flags.  I don't understand them
> that well.  What configuration flags would this list recommend?
>
> BR,
> Robert Thorpe

My two cents -

The GNU software build process has been refreshingly consistent for
decades.  If you use the tar-balls from https://ftp.gnu.org/pub/gnu/,
you can usually just follow the basic algorithm:

 - untar the tarball
 - cd pkg-ver.min/
 - ./configure --help

Often, the "special" non universial options to configure will be
documented in the output if you pass "--help" - this might vary from
package to package but has served me well since around 1990 or so.

The GNU pakcages usually have a "INSTALL" file which gives build
instructions as well.

Also, if you are building from source on MacOS you can start with the
build scripts here:

   https://github.com/caldwell/build-emacs.git

As for cherry picking options, this can really vary based on how you are
going to use Emacs and your platform.  As above, I usually take the time
to read the output of configure with --help first and read through the
output and think about which ones I want on/off/set/unset etc.  After a
few builds, I come up with my personal "standard" - YMMV.

Good luck,

Dan







  parent reply	other threads:[~2017-11-08 16:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-05 22:06 Compiling Emacs from Source Robert Thorpe
2017-11-05 22:43 ` Jean-Christophe Helary
2017-11-07  5:43   ` Kendall Shaw
2017-11-07 23:58 ` Emanuel Berg
2017-11-08  1:01   ` John Mastro
2017-11-08  1:27     ` Emanuel Berg
2017-11-08  4:26     ` Emanuel Berg
2017-11-11 20:45     ` Robert Thorpe
2017-11-08 16:32 ` Dan Mack [this message]
2017-11-08 19:21   ` Emanuel Berg
  -- strict thread matches above, loose matches on Subject: below --
2010-03-27  3:29 Compiling Emacs from source Henri-Paul Indiogine
2010-03-27  5:05 ` Óscar Fuentes
2010-03-27  9:52 ` 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

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

  git send-email \
    --in-reply-to=m2tvy4buji.fsf@pandora.lan \
    --to=mack@macktronics.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=rt@robertthorpeconsulting.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.