Alex Sassmannshausen <alex.sassmannshau...@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