unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@gnu.org>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: emacs-devel@gnu.org
Subject: Re: Multi-platform build system (was: Building Emacs on Windows with MinGW+MSYS)
Date: Thu, 13 Oct 2011 20:41:27 -0400	[thread overview]
Message-ID: <yxqk488ievc.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87vcrsbgzb.fsf_-_@wanadoo.es> ("Óscar Fuentes"'s message of "Fri, 14 Oct 2011 01:37:44 +0200")

Óscar Fuentes <ofv@wanadoo.es> writes:

> [snip]
>
> 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.

The current build system works, it's complex mostly because of what
emacs needs (dumping is a big factor).  We are using the standard GNU
tools, and there's a lot of collective experience dealing with those
tools. 
Whatfor emacs 's the advantage of yet another build system that has not yet 
What is the advantage for emacs of yet another build system that has not
been widely adopted by GNU projects? 



  parent reply	other threads:[~2011-10-14  0:41 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       ` Dan Nicolaescu [this message]
2011-10-14  1:43         ` Ó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
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=yxqk488ievc.fsf@fencepost.gnu.org \
    --to=dann@gnu.org \
    --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).