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 03:27:13 +0200 [thread overview]
Message-ID: <87mxd4bbwu.fsf@wanadoo.es> (raw)
In-Reply-To: <87aa948k9e.fsf@catnip.gol.com> (Miles Bader's message of "Fri, 14 Oct 2011 09:55:09 +0900")
Miles Bader <miles@gnu.org> writes:
> Óscar Fuentes <ofv@wanadoo.es> writes:
>> 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.
>
> Off-topic, but I'm quite skeptical of this claim, compared to
> automake. Makefile.am files tend to be pretty darn close to the
> minimal amount of information required to build (in typical cases: a
> list of source files), and very easy to extend.
>
> Automake's implementation is not very pretty, but the interface
> presented to the user is extremely good.
Well, automake scripts can be easy once you know how to handle them, but
auto* seems hard to learn.
My first experience with a big and complex project was LLVM
(www.llvm.org) What they have now is half as complex as the system I
wrote because they removed features (because of changing trade-off). It
took me a few weekends to write (keep in mind that I was a total
beginner with cmake) being the main time-consuming factor the large
amount of time each test build required. Since, people who had no
previous experience with autoconf/make nor with cmake claim to be more
at easy with the cmake build.
All of this is very subjective, of course. The Emacs build is not your
typical C/C++ project, which cmake is optimized for, but neither it is
LLVM, and it worked very well.
next prev parent reply other threads:[~2011-10-14 1:27 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 [this message]
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
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=87mxd4bbwu.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 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).