From: Hilton Chain <hako@ultrarare.space>
To: guix-devel@gnu.org
Cc: dan <i@dan.games>, "Efraim Flashner" <efraim@flashner.co.il>,
"Ekaitz Zarraga" <ekaitz@elenq.tech>,
"Motiejus Jakštys" <motiejus@jakstys.lt>,
"Noé Lopez" <noe@xn--no-cja.eu>
Subject: Re: Bootstrapping Zig with no binary blobs: status update and call for packages.
Date: Thu, 05 Dec 2024 14:28:32 +0800 [thread overview]
Message-ID: <87plm6prsf.wl-hako@ultrarare.space> (raw)
In-Reply-To: <87a5dip0j5.wl-hako@ultrarare.space>
On Fri, 29 Nov 2024 22:39:10 +0800,
Hilton Chain wrote:
>
> Other new arguments, #:skip-build? and #:zig-inputs, like the ones in
> cargo-build-system, are available. Note that packages and sources in
> #:zig-inputs must have their output names starting with "zig-".
Amend: #:zig-inputs will be removed in the end. Now it's recommended to add Zig
dependencies to the standard inputs and propagated-inputs fields, and change
dependency names within package sources instead of embed the name mapping into
build system arguments.
A new procedure 'rename-zig-dependencies' is added for producing the needed
origin snippet. Examples are available in zig-xyz.scm.
prev parent reply other threads:[~2024-12-05 7:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-01 20:39 Bootstrapping Zig with no binary blobs: status update and call for packages Ashvith Shetty
2024-11-29 14:39 ` Hilton Chain
2024-12-01 23:19 ` Hilton Chain
2024-12-02 7:34 ` Efraim Flashner
2024-12-02 11:30 ` Ashvith Shetty
2024-12-03 15:37 ` Hilton Chain
2024-12-04 17:57 ` Hilton Chain
2024-12-02 13:18 ` Ludovic Courtès
2024-12-05 6:28 ` Hilton Chain [this message]
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87plm6prsf.wl-hako@ultrarare.space \
--to=hako@ultrarare.space \
--cc=efraim@flashner.co.il \
--cc=ekaitz@elenq.tech \
--cc=guix-devel@gnu.org \
--cc=i@dan.games \
--cc=motiejus@jakstys.lt \
--cc=noe@xn--no-cja.eu \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).