From: Eric Le Bihan <eric.le.bihan.dev@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [Patch v6 0/7] Add support for the Rust programming language
Date: Sat, 1 Jul 2017 13:28:55 +0200 [thread overview]
Message-ID: <20170701112855.GA22905@itchy> (raw)
In-Reply-To: <20170628122035.GB4971@momiji>
Hi!
On 17-06-28 12:20:35, Adrian Perez de Castro wrote:
> Hello Eric (and everybody else :D),
>
> I think it's great that there is work being done to bring Rust support to
> Buildroot, because the languge has been gaining a lot of traction, and people
> are now writing very interesting programs in it (I am a fan of RipGrep myself!
> If you don't know it, take a look at: https://github.com/BurntSushi/ripgrep)
>
> Recently I submitted v2 of a patch to add a LLVM package, and it would be
> interesting to coordinate to make your Rust patchset use it, instead of the
> Rust packaging providing its own copy of LLVM. You can see the patch in
> Patchwork:
>
> https://patchwork.ozlabs.org/patch/777949/
>
> I am addin some comments inline below, please keep reading...
>
> On Sun, 25 Jun 2017 22:56:07 +0200, Eric Le Bihan <eric.le.bihan.dev@free.fr> wrote:
> > This series adds support for the Rust programming language by adding the
> > following packages:
> >
> > - rustc: a virtual package for the Rust compiler.
> > - rust-bin: provides a pre-built version of rustc.
> > - rust: builds rustc from source.
> >
> > Both providers are able to cross-compile code for ARM, MIPS, PowerPC and
> > x86_64 architectures. Only the host variants are provided.
>
> This means that the ?llvm? package should also provide a host variant of the
> package. I did a quick try adding ?$(eval $(host-cmake-package))? plus a few
> minor changs locally and LLVM built just fine.
Yes. To build host-rust, the libraries from host-llvm would be required.
If you could provide a patch adding host-llvm, I'll happily test it.
> Regarding the architecture backends to enable, I imagine we would want host
> variant to have enabled *both* the host-native backend, and the target
> backend. Example: When building for ARM in x86_64, we would enable the ?ARM?
> and ?X86? LLVM backends for ?host-llvm?, and only ?ARM? for ?llvm? (the target
> package). Would this be correct? Do you foresee any situation in which other
> backends should be enabled for either the host or target variants? Should we
> allow selecting from menuconfig which backends are compiled for the target
> ?llvm? package?
IMHO, it is best to keep it simple with only the host and the target archs.
> Last but not least: Right now my patch for adding LLVM only builds the main
> libraries and binaries. Is this enough for Rust?
Yes.
BR,
--
ELB
next prev parent reply other threads:[~2017-07-01 11:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-25 20:56 [Buildroot] [Patch v6 0/7] Add support for the Rust programming language Eric Le Bihan
2017-06-25 20:56 ` [Buildroot] [Patch v6 1/7] pkg-virtual: fix host dependencies handling Eric Le Bihan
2017-07-01 13:07 ` Arnout Vandecappelle
2017-07-02 21:40 ` Thomas Petazzoni
2017-06-25 20:56 ` [Buildroot] [Patch v6 2/7] rustc: new virtual package Eric Le Bihan
2017-06-25 20:56 ` [Buildroot] [Patch v6 3/7] rust-bin: new package Eric Le Bihan
2017-06-25 20:56 ` [Buildroot] [Patch v6 4/7] rustc: expose host variant in menuconfig Eric Le Bihan
2017-06-25 20:56 ` [Buildroot] [Patch v6 5/7] rust-bootstrap: new package Eric Le Bihan
2017-06-25 20:56 ` [Buildroot] [Patch v6 6/7] cargo-bootstrap: " Eric Le Bihan
2017-06-25 20:56 ` [Buildroot] [Patch v6 7/7] rust: " Eric Le Bihan
2017-06-28 9:20 ` [Buildroot] [Patch v6 0/7] Add support for the Rust programming language Adrian Perez de Castro
2017-07-01 11:28 ` Eric Le Bihan [this message]
2017-07-01 13:01 ` Arnout Vandecappelle
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170701112855.GA22905@itchy \
--to=eric.le.bihan.dev@free.fr \
--cc=buildroot@busybox.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox