From: divoplade <d@divoplade.fr>
To: "Jérémy Korwin-Zmijowski" <jeremy@korwin-zmijowski.fr>,
help-guix@gnu.org, "Mailing list Guile User" <guile-user@gnu.org>
Subject: Re: Blog post about Hall
Date: Thu, 11 Jun 2020 18:22:27 +0200 [thread overview]
Message-ID: <4958fae7f221e2d2335970c4658e0208a739d8d9.camel@divoplade.fr> (raw)
In-Reply-To: <57247BE9-CB5B-4D8D-89D1-A1C7769E8C22@korwin-zmijowski.fr>
Hello Jérémy,
Le jeudi 11 juin 2020 à 17:10 +0200, Jérémy Korwin-Zmijowski a écrit :
> Dear hackers,
>
> I want to share with you my last blog post about Hall !
>
> Hope it can be helpful.
>
> Here is the english version :
>
> https://jeko.writeas.com/hall-a-project-manager-for-the-guile-programming-language
>
> You can also find the french version on the blog.
This project is a good idea, and it's great to see blog posts. I
considered using it for myself, but as of now C bindings are
unfortunately not supported, so I still have to go with autoscan for
the bindings. When I finish stripping them out of the scheme code, I
will be sure to use hall for the interesting parts!
I really like the fact that I don't have to give up the automake
features. On that note, you may also want to consider adding a quick
line for "make distcheck", which makes sure that the distribution can
be built from source (detect missing files, out-of-tree build errors,
and a few other goodies)
https://www.gnu.org/software/automake/manual/html_node/Checking-the-Distribution.html
Best regards
divoplade
>
> Cheers!
>
> Jérémy
>
>
next prev parent reply other threads:[~2020-06-11 16:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 15:10 Blog post about Hall Jérémy Korwin-Zmijowski
2020-06-11 16:22 ` divoplade [this message]
2020-06-11 16:44 ` Jérémy Korwin-Zmijowski
2020-06-11 17:13 ` Aleix Conchillo Flaqué
2020-06-11 19:30 ` Jérémy Korwin-Zmijowski
2020-06-11 20:07 ` Aleix Conchillo Flaqué
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=4958fae7f221e2d2335970c4658e0208a739d8d9.camel@divoplade.fr \
--to=d@divoplade.fr \
--cc=guile-user@gnu.org \
--cc=help-guix@gnu.org \
--cc=jeremy@korwin-zmijowski.fr \
/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).