unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel@gnu.org
Subject: Re: Getting rid of build tools
Date: Tue, 29 Dec 2015 16:33:47 +0100	[thread overview]
Message-ID: <87ziwt1d7o.fsf@gnu.org> (raw)
In-Reply-To: <20151228190536.GA5914@thebird.nl> (Pjotr Prins's message of "Mon, 28 Dec 2015 20:05:36 +0100")

Pjotr Prins <pjotr.public12@thebird.nl> skribis:

> I am not saying we don't need build tools altogether - I'll still use
> make and rake, for example. But we certainly don't need all the
> baggage that comes with the current set of 'complex' Makefile
> generation tools that are automake and cmake.

The main purpose of Automake is to generate makefiles that (1) contain a
lot of non-trivial rules that Make alone does not provide, such as
dependency tracking for C source and headers, and (2) to generate the
rules specified in the GNU Coding Standards that and users have come to
expect:

  http://www.gnu.org/prep/standards/html_node/Standard-Targets.html

I think this remains relevant.

Ludo’.

  parent reply	other threads:[~2015-12-29 15:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-27  8:23 Getting rid of build tools Pjotr Prins
2015-12-28 15:06 ` Christopher Allan Webber
2015-12-28 19:05   ` Pjotr Prins
2015-12-29  1:47     ` Pjotr Prins
2015-12-29  2:42       ` Pjotr Prins
2015-12-29  7:22         ` Ricardo Wurmus
2015-12-29 15:26           ` Pjotr Prins
2015-12-29 15:37       ` Ludovic Courtès
2015-12-29 15:40         ` Pjotr Prins
2015-12-29 22:21         ` Christopher Allan Webber
2015-12-29 23:41           ` Ludovic Courtès
2016-01-01  7:16         ` Pjotr Prins
2015-12-29 15:33     ` Ludovic Courtès [this message]
2015-12-29 15:39       ` Pjotr Prins
2016-01-06  5:22   ` Pjotr Prins

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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ziwt1d7o.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=pjotr.public12@thebird.nl \
    /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/guix.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).