From: Pjotr Prins <pjotr.public12@thebird.nl>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Getting rid of build tools
Date: Tue, 29 Dec 2015 16:39:09 +0100 [thread overview]
Message-ID: <20151229153909.GC9031@thebird.nl> (raw)
In-Reply-To: <87ziwt1d7o.fsf@gnu.org>
On Tue, Dec 29, 2015 at 04:33:47PM +0100, Ludovic Courtès wrote:
> 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.
Sure, but with less targets, thanks to GNU Guix, we could get a much
simpler system. Automake and cmake make my head hurt every time I deal
with them.
Pj.
--
next prev parent reply other threads:[~2015-12-29 15:39 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
2015-12-29 15:39 ` Pjotr Prins [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151229153909.GC9031@thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=guix-devel@gnu.org \
--cc=ludo@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.