Re: Re: [ANN] Guile Hall Release (v0.1.1)

[alex sassmannshausen <alex.sassmannshausen@gmail.com>]

Hey Arne,

On Tue, 3 Jul 2018, 09:27 Arne Babenhauserheide, <Arne_Bab@web.de> wrote:

> > Gesendet: Dienstag, 03. Juli 2018 um 09:03 Uhr
> > Von: "alex sassmannshausen" <alex.sassmannshausen@gmail.com>
> > An: "Ludovic Courtès" <ludo@gnu.org>
> > Cc: guile-user@gnu.org
> > Betreff: Re: [ANN] Guile Hall Release (v0.1.1)
> >
> > On Mon, 2 Jul 2018, 17:09 Ludovic Courtès, <ludo@gnu.org> wrote:
> >
> > > Heya,
> > >
> > > Alex Sassmannshausen <alex.sassmannshausen@gmail.com> skribis:
> > >
> > > >> I wonder if it would be useful to have a “standalone” mode, where
> Hall
> > > >> would rely neither on Autoconf/Automake nor on Guix to do basic
> things
> > > >> like building code.  It might help newcomers.  You wouldn’t want to
> > > >> reimplement everything though, so I don’t know if this is a viable
> > > >> approach.  Thoughts?
> > > >
> > > > Interesting idea.  When you say building code, do you mean literally
> > > > compiling a project within the project folder & perhaps generating a
> > > > wrapper script that might update GUILE_LOAD_{COMPILED_}PATH à la
> > > > pre-inst-env, or do you mean some form of installer?
> > >
> > > I’m thinking of a “hall build” command that would build Scheme files
> and
> > > produce a wrapper script, and optionally “hall install” as well.
> >
> >
> > > It’s interesting only if it can be done without reimplementing too much
> > > of the Autoconf/Automake or Guix logic, I suppose.
> > >
> >
> > Agreed. I do think having some easy way of "running" your project would
> be
> > cool.
> >
> > Thanks for your thoughts!
>
> A while ago I started a project which simply sets up autotools:
>
> https://bitbucket.org/ArneBab/conf/src/default/
>
> > conf - Initialize modern autotools projects
> > Inspired by Mozilla Cargo ( http://doc.crates.io/guide.html ) but
> without the NIH and currently more limited in scope.
> > See NEWS for user-visible changes. See ChangeLog or the history for
> detailed changes.
>
> Going that way allows re-using all the features of autotools by providing
> simple templates for common setups — and a starting point for more complex
> ones.
>

From this description, it sounds fairly close to what hall does too! Sounds
like there's some overlap here :)

Then hall build can simply be a wrapper for ./bootstrap.sh && ./configure
> && make
>

Right, that could indeed already be the implementation of hall build
actually. Thanks for that idea!


Alex

Best wishes,
> Arne
>