From: Juanma Barranquero <lekktu@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: ofv@wanadoo.es, schwab@linux-m68k.org, emacs-devel@gnu.org
Subject: Re: CMake build anyone?
Date: Mon, 26 Jul 2010 22:11:39 +0200 [thread overview]
Message-ID: <AANLkTi=Uve2JwcwStY3M-LtL8oBa=ZsMv-t_W81oeF0w@mail.gmail.com> (raw)
In-Reply-To: <837hkib28j.fsf@gnu.org>
On Mon, Jul 26, 2010 at 19:07, Eli Zaretskii <eliz@gnu.org> wrote:
> No, Andreas got my drift correctly. I was thinking first and foremost
> about building a release tarball.
Building a release tarball is not something most users do, so the
number of prerequisites is less important.
> Which won't work if I need to fix a bug or add a feature. This is
> still Free Software, right?
I don't get your meaning. If you need to build, there are a bunch of
things you *have* to have installed. You talked about cp and rm (and
somehow considered GCC/MinGW a given) but surely free software users
also do fix the info files and will need makeinfo, won't they?
The point being: I'm not pushing for or against CMake, but at the end
of the day, it is just *one* more prerequisite among quite a few.
I think you see it as less useful because for you the makefiles wok
pretty well, as you said. Personally, I hate having to modify a
makefile or a .bat script. Not to mention having to study changes in
the Unix build system to determine whether they make sense in the
Windows side.
Juanma
next prev parent reply other threads:[~2010-07-26 20:11 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-25 17:28 CMake build anyone? Óscar Fuentes
2010-07-25 17:42 ` Juanma Barranquero
2010-07-25 17:57 ` Óscar Fuentes
2010-07-25 18:21 ` Juanma Barranquero
2010-07-25 19:44 ` Óscar Fuentes
2010-07-25 20:47 ` Juanma Barranquero
2010-07-25 20:57 ` Eli Zaretskii
2010-07-25 20:54 ` Eli Zaretskii
2010-07-25 21:34 ` Óscar Fuentes
2010-07-25 23:04 ` Juanma Barranquero
2010-07-25 23:44 ` Óscar Fuentes
2010-07-26 0:05 ` Juanma Barranquero
2010-07-26 0:16 ` Óscar Fuentes
2010-07-26 3:07 ` Eli Zaretskii
2010-07-26 3:42 ` Juanma Barranquero
2010-07-26 9:18 ` Andreas Schwab
2010-07-26 9:54 ` Juanma Barranquero
2010-07-26 10:11 ` Andreas Schwab
2010-07-26 10:16 ` Juanma Barranquero
2010-07-26 17:12 ` Eli Zaretskii
2010-07-26 20:19 ` Juanma Barranquero
2010-07-26 20:33 ` Eli Zaretskii
2010-07-26 21:19 ` Miles Bader
2010-07-26 21:59 ` Juanma Barranquero
2010-07-26 17:07 ` Eli Zaretskii
2010-07-26 20:11 ` Juanma Barranquero [this message]
2010-07-26 21:33 ` Stefan Monnier
2010-07-26 22:04 ` Óscar Fuentes
2010-07-26 23:11 ` Stefan Monnier
2010-07-26 23:32 ` Miles Bader
2010-07-27 0:34 ` Wojciech Meyer
2010-07-27 3:06 ` Tom Tromey
2010-07-27 3:21 ` Miles Bader
2010-07-27 15:43 ` Alfred M. Szmidt
2010-07-27 10:36 ` Stefan Monnier
2010-07-26 4:15 ` Óscar Fuentes
2010-07-26 4:45 ` Óscar Fuentes
2010-07-26 17:03 ` Eli Zaretskii
2010-07-26 20:02 ` Juanma Barranquero
2010-07-26 20:31 ` Eli Zaretskii
2010-07-26 17:01 ` 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='AANLkTi=Uve2JwcwStY3M-LtL8oBa=ZsMv-t_W81oeF0w@mail.gmail.com' \
--to=lekktu@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=ofv@wanadoo.es \
--cc=schwab@linux-m68k.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).