From: Arne Babenhauserheide <arne_bab@web.de>
To: alex.sassmannshausen@gmail.com
Cc: "Ludovic Courtès" <ludo@gnu.org>, guile-user@gnu.org
Subject: Re: [ANN] Guile Hall 0.3.0 released
Date: Mon, 18 May 2020 07:43:28 +0200 [thread overview]
Message-ID: <87d071u7b3.fsf@web.de> (raw)
In-Reply-To: <87wo5acmd6.fsf@gmail.com>
Alex Sassmannshausen <alex.sassmannshausen@gmail.com> writes:
>> m4 is just a very simple templating language. Should not be too hard
>> to implement it in Guile.
>
> Again, this has come up in the past. I love the idea of having a Guile
> way to do the work that m4, autoreconf and automake do — I think any
> piecemeal or module work towards this would super valuable.
>
> I hope for now, in the absence of those things existing, having Hall
> provide a kludgy bridge between autotools and Guile might be the best of
> both worlds…
I have yet to use it (I’m still doing the autotools setup by hand; but
that’s mostly because my Guile tools are mostly wisp so I need custom
stuff), but yes: having autotools autogenerated is extremely valuable.
If you have automated autotools setup - something that just works - it’s
like all those project-setup tools other languages have (Java with
Maven, Javascript with npm, Rust with cargo, Go …), but with the
difference that it works everywhere.
I have used several different build tools in the past, and once you
stray even slightly outside the usual path, autotools (with all its
cludginess) still outdoes them all.
Sidenote: Does guile hall setup help for Make?
→ https://hg.sr.ht/~arnebab/conf/browse/Makefile.am?rev=314983dd7beb661ac931aa33a4937bd7cccd30c1#L26
(shows rule lines with ## comments as help output for commands)
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken
next prev parent reply other threads:[~2020-05-18 5:43 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-16 15:41 [ANN] Guile Hall 0.3.0 released Alex Sassmannshausen
2020-05-16 16:14 ` Jack Hill
2020-05-16 16:22 ` Catonano
2020-05-16 20:57 ` Alex Sassmannshausen
2020-05-17 5:13 ` Catonano
2020-05-17 15:35 ` Alex Sassmannshausen
2020-05-17 17:37 ` Catonano
2020-05-17 18:31 ` Arne Babenhauserheide
2020-05-17 20:55 ` Alex Sassmannshausen
2020-05-18 5:43 ` Arne Babenhauserheide [this message]
2020-05-17 20:48 ` Alex Sassmannshausen
2020-05-18 16:19 ` Catonano
2020-05-20 11:45 ` Catonano
2020-05-20 11:46 ` Alex Sassmannshausen
2020-05-20 15:58 ` Catonano
2020-05-21 10:00 ` Catonano
2020-05-21 10:03 ` Alex Sassmannshausen
2020-05-22 5:16 ` Catonano
2020-05-24 21:22 ` Alex Sassmannshausen
2020-05-25 6:31 ` Catonano
2020-05-25 7:13 ` Alex Sassmannshausen
2020-05-25 7:51 ` Catonano
2020-05-26 14:37 ` Catonano
2020-05-27 20:52 ` Ludovic Courtès
2020-05-28 5:01 ` Catonano
2020-05-28 12:32 ` Ludovic Courtès
2020-05-28 12:35 ` Catonano
2020-05-28 15:54 ` Ludovic Courtès
2020-05-28 17:26 ` Catonano
2020-05-29 8:27 ` Ludovic Courtès
2020-05-29 9:09 ` Catonano
2020-05-29 10:52 ` Alex Sassmannshausen
2020-05-17 16:36 ` Christopher Lemmer Webber
2020-05-17 20:40 ` Alex Sassmannshausen
2020-05-17 20:21 ` Jérémy Korwin-Zmijowski
2020-05-18 15:43 ` Nala Ginrut
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d071u7b3.fsf@web.de \
--to=arne_bab@web.de \
--cc=alex.sassmannshausen@gmail.com \
--cc=guile-user@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.
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).