all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Óscar Fuentes" <ofv@wanadoo.es>
To: Miles Bader <miles@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Multi-platform build system
Date: Fri, 14 Oct 2011 02:31:13 +0200	[thread overview]
Message-ID: <87r52gbei6.fsf@wanadoo.es> (raw)
In-Reply-To: <87fwiw8mcy.fsf@catnip.gol.com> (Miles Bader's message of "Fri, 14 Oct 2011 09:09:49 +0900")

Miles Bader <miles@gnu.org> writes:

> Óscar Fuentes <ofv@wanadoo.es> writes:
>> 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.
>
> If this were in the repo, would it become a maintenance burden once
> you don't have time to do so yourself?  Obviously the Emacs build
> process is relatively complex, so presumably maintenance would require
> more than updating lists of files occasionally.
>
> Of course, maybe it would be _less_ of a burden than maintaining the
> current scripts etc...

Experience shows that a cmake spec usually is a fraction of the length
of the equivalent autoconf+automake/Makefile spec,
line-wise. Maintenance work is proportionally reduced. It's easier to
add new features, too.

> (presuming the additional dependency on cmake is acceptable)

Yep, that was the inconvenience that people voiced the last time. The
cmake build would work everywhere as long as cmake is present but now,
like then, I'm thinking mostly on the Windows users, who already have to
install other software besides the compiler for building Emacs. You'll
remove the GnuWin32 dependency and replace it with cmake. The gain is,
precisely, on the simplification of maintenance and the added value of
the multiple features cmake offers [1]. The people who maintains the
Windows scripts said that maintaining those is no problem, so my
proposal was dumped.

[1]: http://www.vtk.org/Wiki/Really_Cool_CMake_Features (that's not a
complete list)



  reply	other threads:[~2011-10-14  0:31 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 [this message]
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
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

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

  git send-email \
    --in-reply-to=87r52gbei6.fsf@wanadoo.es \
    --to=ofv@wanadoo.es \
    --cc=emacs-devel@gnu.org \
    --cc=miles@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.
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.