unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: CMake build anyone?
Date: Sun, 25 Jul 2010 19:57:50 +0200	[thread overview]
Message-ID: <87wrsjwijl.fsf@telefonica.net> (raw)
In-Reply-To: AANLkTi=UYvaC_Af+2KpK6KiAWj-mXjpmhXUAc9_DeuXE@mail.gmail.com

Juanma Barranquero <lekktu@gmail.com> writes:

> On Sun, Jul 25, 2010 at 19:28, Óscar Fuentes <ofv@wanadoo.es> wrote:
>
>> but if there is interest from any of the build
>> maintainers, I could steer the development for creating a "serious"
>> build specification.
>
> IIUC, with CMake you write configuration files, from which you
> generate "normal" makefiles.

Yes. CMake creates files for your tool of choice (`make', `nmake',
Eclipse, etc.) It is not a build tool itself, but a build generator.

> That would be useful if it allowed us to simplify and reunify the
> GNU/Linux / Unix / MSDOS / Windows makefiles, bulding them from a
> single set of source configuration files. That's not a trivial
> undertaking, though.

I did that for LLVM (1) and it is perfectly doable for Emacs,
AFAIK. Maybe there are a few configuration tests that are not trivial,
but we can "borrow" from autoconf.

Please note that I'm not proposing throwing away the autoconf-based
build (not because CMake can't replace autoconf/automake, but just
because I already created enough controversy here.) Just providing cmake
as an option where autoconf is available, and as the official method
where it isn't.

One caveat: knowing nothing about the emacs MSDOS build, I don't know
how well CMake works for it. Maybe we can use cmake's cross-compiling
feature for driving the MSDOS compiler (DJGPP?)

1: http://www.llvm.org




  reply	other threads:[~2010-07-25 17:57 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 [this message]
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
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=87wrsjwijl.fsf@telefonica.net \
    --to=ofv@wanadoo.es \
    --cc=emacs-devel@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).