From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: "Dr. Arne Babenhauserheide" <arne_bab@web.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: Thu, 4 Feb 2021 00:07:37 +0100 [thread overview]
Message-ID: <955c4811-724a-4f9c-1704-59a21b5d9916@posteo.de> (raw)
In-Reply-To: <87pn1l5d78.fsf@web.de>
Hello Arne!
Thank you for that! Do you have an example for when one would bake in
system-specific data-paths?
Best wishes,
Zelphir
On 1/31/21 4:38 PM, Dr. Arne Babenhauserheide wrote:
> Zelphir Kaltstahl <zelphirkaltstahl@posteo.de> writes:
>> This may be short sighted or uninformed, but generally I don't know, why
>> I would build anything, except for running it. If I am not confused
> Here are three reasons for building of a pure-guile ication:
>
> - avoid the initial start time due to auto-compilation
> - set specific optimization parameters (i.e. O3)
> - bake-in system-specific data-paths (i.e. images to load)
>
> Best wishes,
> Arne
--
repositories: https://notabug.org/ZelphirKaltstahl
next prev parent reply other threads:[~2021-02-03 23:07 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 [this message]
2021-02-04 0:09 ` Ricardo Wurmus
2021-02-03 18:31 ` Adriano Peluso
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=955c4811-724a-4f9c-1704-59a21b5d9916@posteo.de \
--to=zelphirkaltstahl@posteo.de \
--cc=arne_bab@web.de \
--cc=guile-user@gnu.org \
/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).