From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: emacs-devel@gnu.org
Subject: Re: Multi-platform build system
Date: Fri, 14 Oct 2011 09:18:17 -0400 [thread overview]
Message-ID: <jwvaa93wwvn.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87vcrsbgzb.fsf_-_@wanadoo.es> ("Óscar Fuentes"'s message of "Fri, 14 Oct 2011 01:37:44 +0200")
> Time ago I volunteered to write a CMake [1] build spec for Emacs. It was
> considered unnecessary by the people who does most of the work on the
> current build systems. I will have some free time (sigh) on the next
> months, so I reiterate the offer in case anyone changed his mind.
I'm not sure I understand the way the discussion is going (at least from
a rational point of view ;-). So I'll start over from the beginning.
Currently Emacs has 2 build systems: one that is a mix of old-style
ad-hoc config files (predefined per system in src/m and src/s) and
autoconf+make, and another one for Windows builds.
We could use CMake to replace either (or both) of them:
- I don't think only replacing the Windows build systems would be
a great improvement.
- Getting rid of the duplication between the two build systems would be nice.
- I don't know what would be the benefit of replacing the autoconf
system: I'd be very happy to get rid of the src/m and src/s config
files (we've already made significant progress in this direction) but
I don't think using CMake would magically do that for us. And it
would add `cmake' as an additional build-dependency (compared to
autoconf which is not absolutely needed to build Emacs).
I have no experience with CMake, so it's hard to know whether it would
be a good change or not. But I would be interested to see what that
would look like.
Stefan
next prev parent reply other threads:[~2011-10-14 13:18 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 21:01 Building Emacs on Windows with MinGW+MSYS (was: Emacs pretest 24.0.90) Dani Moncayo
2011-10-13 22:03 ` Eli Zaretskii
2011-10-13 22:23 ` Dani Moncayo
2011-10-13 23:37 ` Multi-platform build system (was: Building Emacs on Windows with MinGW+MSYS) Óscar Fuentes
2011-10-14 0:09 ` Multi-platform build system Miles Bader
2011-10-14 0:31 ` Óscar Fuentes
2011-10-14 0:55 ` Miles Bader
2011-10-14 1:27 ` Óscar Fuentes
2011-10-14 0:41 ` Multi-platform build system (was: Building Emacs on Windows with MinGW+MSYS) Dan Nicolaescu
2011-10-14 1:43 ` Multi-platform build system Óscar Fuentes
2011-10-14 6:17 ` Dan Nicolaescu
2011-10-14 1:06 ` Multi-platform build system (was: Building Emacs on Windows with MinGW+MSYS) Juanma Barranquero
2011-10-14 1:18 ` Christoph Scholtes
2011-10-14 1:20 ` Juanma Barranquero
2011-10-14 1:47 ` Multi-platform build system Óscar Fuentes
2011-10-14 1:33 ` Óscar Fuentes
2011-10-14 1:43 ` Juanma Barranquero
2011-10-14 2:52 ` Óscar Fuentes
2011-10-14 3:17 ` Juanma Barranquero
2011-10-14 1:57 ` Miles Bader
2011-10-14 2:05 ` Juanma Barranquero
2011-10-14 2:28 ` Miles Bader
2011-10-14 2:31 ` Juanma Barranquero
2011-10-14 5:01 ` Stephen J. Turnbull
2011-10-14 13:18 ` Stefan Monnier [this message]
2011-10-14 8:20 ` Building Emacs on Windows with MinGW+MSYS (was: Emacs pretest 24.0.90) Eli Zaretskii
2011-10-13 23:09 ` Building Emacs on Windows with MinGW+MSYS Miles Bader
2011-10-14 8:16 ` Eli Zaretskii
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=jwvaa93wwvn.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=ofv@wanadoo.es \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).