unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Maxime Devos <maximedevos@telenet.be>, Guix-devel <guix-devel@gnu.org>
Cc: Hartmut Goebel <h.goebel@crazy-compilers.com>
Subject: Re: antioxidant update: librsvg builds, and other things (core-updates)
Date: Sat, 27 Aug 2022 21:54:31 +0200	[thread overview]
Message-ID: <52b1f6c4324872a6522e87c01e48b3d21485e21f.camel@gmail.com> (raw)
In-Reply-To: <1a94a3b6-4798-fb44-013c-4452931c29d4@telenet.be>

Am Samstag, dem 27.08.2022 um 12:54 +0200 schrieb Maxime Devos:
> Some questions:
>  * Some Rust crates have 'examples' and 'benchmarks' that can be
> compiled and installed. I could teach antioxidant to compile and
> install them, though it appears to provide very little value at cost
> of more compile time and a greater closure size (more binaries, more
> dependencies and wasn't there some bug with grafts whose fix causes
> outputs to be substituted that ended up unused? Though hopefully
> someone could figure out a better fix ...)
I think you could try building those examples as a separate output or
package.

>  * Due to how regularised the Rust build system is, it's feasible to
> compile tests even when cross-compiling (*), so cross-compiled could
> run the cross-compiled tests on the system they are cross-compiling
> for after the cross-compilation to verify their cross-compiled
> software.
How exactly does this work without emulating the system in question?


  reply	other threads:[~2022-08-27 19:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-27 10:54 antioxidant update: librsvg builds, and other things (core-updates) Maxime Devos
2022-08-27 19:54 ` Liliana Marie Prikler [this message]
2022-08-27 20:01   ` Maxime Devos
2022-08-27 22:04     ` Liliana Marie Prikler
2022-08-28  9:38       ` Maxime Devos
2022-09-01 10:40 ` 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=52b1f6c4324872a6522e87c01e48b3d21485e21f.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=h.goebel@crazy-compilers.com \
    --cc=maximedevos@telenet.be \
    /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).