From: Eli Zaretskii <eliz@gnu.org>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: emacs-devel@gnu.org
Subject: Re: CMake build anyone?
Date: Mon, 26 Jul 2010 06:07:05 +0300 [thread overview]
Message-ID: <83hbjnaqli.fsf@gnu.org> (raw)
In-Reply-To: <874ofnw8j4.fsf@telefonica.net>
> From: Óscar Fuentes <ofv@wanadoo.es>
> Date: Sun, 25 Jul 2010 23:34:07 +0200
>
> > As long as you are not asking the end users to have CMake installed
> > (and I hope you don't), the DOS build will be okay.
>
> A CMake install is required. Maybe that is an issue for MSDOS users,
Forget MSDOS. It's a problem for everyone. It means to build Emacs
the end users will have to install a tool that is not there out of the
box. I think this is a serious argument against using CMake.
> because there is no cmake port for MSDOS AFAIK.
That should be the least of our problems.
> If you imply that requiring cmake for Windows people is too a serious
> inconvenience, it should be noted that cmake makes gnuwin32/msys
> unnecessary
MSYS is already unnecessary (and even not recommended), and GnuWin32
is just a bunch of ported programs with no relation to one another.
The Windows build requires only `cp' and `rm', and they don't have to
be from GnuWin32.
> For the time being, we can put MSDOS aside and go ahead if cmake is seen
> as convenient enough by the Windows maintainers.
I think it's inconvenient even on GNU/Linux.
next prev parent reply other threads:[~2010-07-26 3:07 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 [this message]
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
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=83hbjnaqli.fsf@gnu.org \
--to=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).