From: Mathieu Othacehe <m.othacehe@gmail.com>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: ARM VM with networking support?
Date: Mon, 25 Nov 2019 15:39:09 +0100 [thread overview]
Message-ID: <875zj8t3zm.fsf@gmail.com> (raw)
In-Reply-To: <87v9r86oiu.fsf@devup.no>
Hey Marius,
> Do you know roughly what's needed to support cross-compiling in
> meson-build-system, apart from creating a '--cross-file'[0]?
Never looked into it, but it seems that nix has proper cross compilation
support for meson (using cross-file.conf as you mentionned), see:
nixpkgs/pkgs/development/tools/build-managers/meson/default.nix
Sadly there are other build-systems where cross-compiling isn't
supported:
* scons.scm
* haskell.scm
* python.scm
* ruby.scm
* perl.scm
* meson.scm
* r.scm
* android-ndk.scm
* go.scm
* waf.scm
* emacs.scm
* asdf.scm
* ocaml.scm
* node.scm
* julia.scm
* dune.scm
* dub.scm
* ant.scm
* linux-module.scm
* rakudo.scm
* cargo.scm
* glib-or-gtk.scm
As I think that using --system is not viable (horribly slow, hard to
find native hardware to cook substitutes), extending cross-compilation
support is very important IMO.
Thanks,
Mathieu
next prev parent reply other threads:[~2019-11-25 14:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-03 14:43 ARM VM with networking support? Ludovic Courtès
2019-11-03 17:09 ` Mathieu Othacehe
2019-11-09 17:24 ` Ludovic Courtès
2019-11-11 7:23 ` Danny Milosavljevic
2019-11-17 17:06 ` Ludovic Courtès
2019-11-11 17:34 ` Mathieu Othacehe
2019-11-17 17:11 ` Ludovic Courtès
2019-11-23 19:01 ` Mathieu Othacehe
2019-11-25 14:04 ` Marius Bakke
2019-11-25 14:39 ` Mathieu Othacehe [this message]
2019-11-26 10:26 ` Ludovic Courtès
2019-12-01 16:30 ` Mathieu Othacehe
2019-12-09 17:35 ` Ludovic Courtès
2019-12-30 21:16 ` Building a bootable disk image for A20-OLinuXino Ludovic Courtès
2019-12-31 9:26 ` Mathieu Othacehe
2019-12-31 11:23 ` Mathieu Othacehe
2020-01-12 11:55 ` Ludovic Courtès
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=875zj8t3zm.fsf@gmail.com \
--to=m.othacehe@gmail.com \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.com \
/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).