From: Adriano Peluso <randomlooser@riseup.net>
To: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
Cc: guile-user@gnu.org
Subject: Re: build system for pure Guile library (was Re: Help making a GNU Guix package for pure GNU Guile library)
Date: Wed, 03 Feb 2021 19:31:27 +0100 [thread overview]
Message-ID: <ea2a02fbc65578e470d119038f5aa7009728be8d.camel@riseup.net> (raw)
In-Reply-To: <f72f1bd3-f5c8-d92c-a435-ef7a94610984@posteo.de>
Il giorno dom, 31/01/2021 alle 15.16 +0100, Zelphir Kaltstahl ha
scritto:
>
>
> However, if anyone told me a good reason to also use autotools to
> manage
> a build process of my code, and I can get it working and understand
> how
> to do it, then why not.
One good reason could be that your Guile based project wraps some C
library, like guile-git
In that case, if you want to support shipping your project to non guix
platforms, the services of autoconf (for testing if the C library is
available on that platform, in which version, if it has this and that
functionality) could be useful
And this goes not only with wrapping C libraries but also with
extensions
If your project doesn't deal with any C code, the reason to use the
autotools is for installing it in a way that it's available to all the
users on a Unix machine
And finally, it could help distributions in packaging it
These 2 points could be true for the Guile build system too, I don't
know
Hope this helps
next prev parent reply other threads:[~2021-02-03 18:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-30 17:17 Help making a GNU Guix package for pure GNU Guile library Zelphir Kaltstahl
2021-01-30 17:55 ` Jérémy Korwin-Zmijowski
2021-01-30 19:56 ` divoplade
2021-01-31 3:26 ` Zelphir Kaltstahl
2021-01-30 18:35 ` John Cowan
2021-01-30 19:43 ` Dr. Arne Babenhauserheide
2021-01-30 20:16 ` divoplade
2021-01-30 21:15 ` Ricardo Wurmus
2021-01-31 0:26 ` build system for pure Guile library (was Re: Help making a GNU Guix package for pure GNU Guile library) pelzflorian (Florian Pelz)
2021-01-31 6:29 ` Ricardo Wurmus
2021-01-31 14:16 ` Zelphir Kaltstahl
2021-01-31 15:38 ` Dr. Arne Babenhauserheide
2021-02-03 23:07 ` Zelphir Kaltstahl
2021-02-04 0:09 ` Ricardo Wurmus
2021-02-03 18:31 ` Adriano Peluso [this message]
2021-01-31 3:19 ` Help making a GNU Guix package for pure GNU Guile library Zelphir Kaltstahl
2021-02-03 18:43 ` Adriano Peluso
2021-02-03 23:12 ` Zelphir Kaltstahl
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=ea2a02fbc65578e470d119038f5aa7009728be8d.camel@riseup.net \
--to=randomlooser@riseup.net \
--cc=guile-user@gnu.org \
--cc=zelphirkaltstahl@posteo.de \
/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).