From: Maxime Devos <maximedevos@telenet.be>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>, guix-devel@gnu.org
Cc: Martin Becze <mjbecze@riseup.net>
Subject: Re: Compiling rust things without cargo (super WIP POC)
Date: Sat, 02 Apr 2022 11:29:22 +0200 [thread overview]
Message-ID: <c6682e19b2feca007ab110885a66c4bec2645128.camel@telenet.be> (raw)
In-Reply-To: <36c1a8dcb363f8780b45156058ea606d0dd50854.camel@telenet.be>
[-- Attachment #1: Type: text/plain, Size: 407 bytes --]
Maxime Devos schreef op do 31-03-2022 om 22:06 [+0200]:
> As a next step, maybe I could try writing a Guix package definition
> for libhello
> and hello-oxygen, gradually making things more complicated (macros,
> transitive
> dependencies, some non-toy Rust dependencies, a Guix build system
> ...)?
Update: it can now build rust-cfg-if, libhello and rust-hello with
Guix!
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-04-02 9:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 11:55 Removing #:skip-build? from the crate importer? Maxime Devos
2022-03-31 19:47 ` Hartmut Goebel
2022-03-31 20:06 ` Compiling rust things without cargo (super WIP POC) Maxime Devos
2022-04-01 6:58 ` Brendan Tildesley
2022-04-01 9:10 ` Ludovic Courtès
2022-04-01 10:05 ` Maxime Devos
2022-04-01 10:08 ` Maxime Devos
2022-04-02 15:01 ` Hartmut Goebel
2022-04-02 9:29 ` Maxime Devos [this message]
2022-04-05 12:08 ` Ludovic Courtès
2022-04-02 15:18 ` Building hexyl (a rust app) without cargo, with antioxidant-build-system Maxime Devos
2022-04-05 16:10 ` Maxime Devos
2022-04-06 15:49 ` Hartmut Goebel
2022-04-06 16:06 ` Maxime Devos
2022-05-30 8:23 ` Efraim Flashner
2022-05-30 13:37 ` raingloom
2022-05-30 15:15 ` Maxime Devos
2022-04-02 15:19 ` Compiling rust things without cargo (super WIP POC) Hartmut Goebel
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=c6682e19b2feca007ab110885a66c4bec2645128.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=guix-devel@gnu.org \
--cc=h.goebel@crazy-compilers.com \
--cc=mjbecze@riseup.net \
/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).