unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: Miles Bader <miles@gnu.org>
Cc: "Óscar Fuentes" <ofv@wanadoo.es>, emacs-devel@gnu.org
Subject: Re: Multi-platform build system
Date: Fri, 14 Oct 2011 04:05:22 +0200	[thread overview]
Message-ID: <CAAeL0STF5TZ1Z-=rn+ybGbbjoescsrsSN18jdEk_W=aMk-4P3Q@mail.gmail.com> (raw)
In-Reply-To: <87mxd472tp.fsf@catnip.gol.com>

On Fri, Oct 14, 2011 at 03:57, Miles Bader <miles@gnu.org> wrote:

> That is so ... cmake, like most build-systems, requires itself to be
> installed for the builder, not just the packager

But it can generate makefiles. If it trusted the user to have the
compiler, etc. in the PATH, instead of hardcoding their paths, it
could be used like the autotools.

> but of course it's invaluable on unixy systems...]

Of course. I still remember the fist time I compiled Perl on a Unix
system, back in 1991. It used a tool similar to autoconf, and it did
make funny comments when it was unable to find some libraries or it
disliked your platform choice or the like. Very LarryWallesque.

    Juanma



  reply	other threads:[~2011-10-14  2:05 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
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 [this message]
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='CAAeL0STF5TZ1Z-=rn+ybGbbjoescsrsSN18jdEk_W=aMk-4P3Q@mail.gmail.com' \
    --to=lekktu@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=miles@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).