>From 3f8c9fca63e3ddeb6f051d9d16e0c21b8cce8a30 Mon Sep 17 00:00:00 2001 From: Alex Sassmannshausen Date: Sun, 24 May 2020 23:18:32 +0200 Subject: [PATCH] Added a reference to Guile Hall in the manual. * doc/ref/scheme-using.texi: Add a section on Hall. --- doc/ref/scheme-using.texi | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) diff --git a/doc/ref/scheme-using.texi b/doc/ref/scheme-using.texi index ac265fcca..55ce778d2 100644 --- a/doc/ref/scheme-using.texi +++ b/doc/ref/scheme-using.texi @@ -744,6 +744,30 @@ using a CPAN-like system. A complete list of guild scripts can be had by invoking @code{guild list}, or simply @code{guild}. +@menu +* Hall:: +@end menu + + +@node Hall +@subsection Bootstrapping projects and distributing them + +There's a tool that doesn't come bundled with Guile and yet can be very +useful in your day to day experience with it. This tool is +@uref{https://gitlab.com/a-sassmannshausen/guile-hall, Hall}. + +Hall helps you create, manage and package your Guile projects through a +simple commandline interface. When you start a new project, Hall +creates a folder containing a scaffold of your new project. It contains +a directory for your tests, for your libraries, for your scripts and for +your documentation. This means you immediately know where to put the +files you are hacking on. + +In addition, the scaffold will include your basic Autotools setup, so +you don't have to take care of that yourself. Having Autotools set up +with your project means you can immediately start hacking on your +project without worrying about whether your code will work on other +people's computers. @node Installing Site Packages @section Installing Site Packages -- 2.23.0