From: Juanma Barranquero <lekktu@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Óscar Fuentes" <ofv@wanadoo.es>, emacs-devel@gnu.org
Subject: Re: CMake build anyone?
Date: Mon, 26 Jul 2010 05:42:01 +0200 [thread overview]
Message-ID: <AANLkTi=C_EXS6u8CodNM5bxMpAWH0hK1scN1FU0haOEi@mail.gmail.com> (raw)
In-Reply-To: <83hbjnaqli.fsf@gnu.org>
On Mon, Jul 26, 2010 at 05:07, Eli Zaretskii <eliz@gnu.org> wrote:
> The Windows build requires only `cp' and `rm'
Also makeinfo, etc. if the user wants to build info files.
> I think it's inconvenient even on GNU/Linux.
Well, that means that we will never be able to switch to another build
system; all will have some external requirements.
But I think the point is that Óscar is not proposing switching to it,
but having the two side by side. That has upsides and downsides (one
of them being that you have to maintain two mutually incompatible
build systems, with the oportunity to neglect one of them).
I must confess that I would prefer what I was asking for: a tool to
make (re)generation of the makefiles easier, instead.
Now, I think I know what you will say: that tool exists, and it's
called "sed" ;-)
Juanma
next prev parent reply other threads:[~2010-07-26 3:42 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 [this message]
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
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=C_EXS6u8CodNM5bxMpAWH0hK1scN1FU0haOEi@mail.gmail.com' \
--to=lekktu@gmail.com \
--cc=eliz@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).