From: Eric Le Bihan <eric.le.bihan.dev@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [Patch v4 3/3] rust: new package
Date: Thu, 13 Apr 2017 16:49:18 +0000 [thread overview]
Message-ID: <b2b48a0cb1c4d27ecbdd9d510e0bdb87@free.fr> (raw)
In-Reply-To: <1492063504.4490.1.camel@embedded.rocks>
Le 2017-04-13 06:05, J?rg Krause a ?crit?:
> Hi,
>
> On Mon, 2017-04-10 at 23:43 +0200, Arnout Vandecappelle wrote:
>>
>> On 10-04-17 21:02, J?rg Krause wrote:
[snip]
>> > For now, we could use the host rustc package to fetch the latest stable
>> > binary for the host architecture. Additionally, we could add the option
>> > to build the Rust compiler within Buildroot. In my opinion, this option
>> > only makes sense if the compiler can be configured meaningfully.
>>
>> I agree.
>
> Cool.
>
> @Eric: Do you mind to do that? By default fetch the latest stable
> release, and alternatively offer an option to build a "Custom Rust
> package". I think it would also be helpful to have at least one Rust
> package to add as a proof of concept.
Currently this patch series provides:
- rust-bootstrap, which fetches the binary version N-1 of rust.
- cargo-bootstrap, which fetches a nightly binary version of cargo.
- rust, which uses the two previous packages to build version N of rust.
I also have another patch series which adds a new package for cargo,
which
uses cargo-bootstrap and rust to build Cargo from source.
IMHO, modifying the current version of the rust package to download the
latest version and providing an option to build from source would make
the Makefile of the package more complicated.
Would it not be better to use host virtual packages? Something like:
- rust-rustc: host virtual package, with two providers:
* rustc-bin: fetches binary version N of rustc and libstd (host and
target).
* rustc: builds version N of rustc and libstd (host and target).
Depends on rust-bootstrap (version N-1) and cargo-bootstrap.
- rust-cargo: host virtual package with two providers:
* cargo-bin: fetches binary version N of Cargo.
* cargo: builds version N of Cargo using rust and cargo-bootstrap.
And instead of littering the package directory with rust-* and cargo-*,
how about putting all these packages in a parent directory named
package/rust?
The file package/Config.in.host should also be modified to include
package/rust/Config.in.host, which would present the options to select
the providers for rust-rustc and rust-cargo.
next prev parent reply other threads:[~2017-04-13 16:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-02 19:46 [Buildroot] [Patch v4 0/3] Add support for the Rust programming language Eric Le Bihan
2017-04-02 19:46 ` [Buildroot] [Patch v4 1/3] rust-bootstrap: new package Eric Le Bihan
2017-04-07 7:03 ` Jörg Krause
2017-04-07 8:26 ` Thomas Petazzoni
2017-04-07 8:54 ` Jörg Krause
2017-04-07 9:03 ` Thomas Petazzoni
2017-04-07 9:22 ` Jörg Krause
2017-04-07 10:26 ` Thomas Petazzoni
2017-04-08 9:23 ` Eric Le Bihan
2017-04-02 19:46 ` [Buildroot] [Patch v4 2/3] cargo-bootstrap: " Eric Le Bihan
2017-04-07 7:06 ` Jörg Krause
2017-04-08 9:34 ` Eric Le Bihan
2017-04-08 13:20 ` Thomas Petazzoni
2017-04-02 19:46 ` [Buildroot] [Patch v4 3/3] rust: " Eric Le Bihan
2017-04-07 7:18 ` Jörg Krause
2017-04-08 10:09 ` Eric Le Bihan
2017-04-10 19:02 ` Jörg Krause
2017-04-10 21:43 ` Arnout Vandecappelle
2017-04-13 6:05 ` Jörg Krause
2017-04-13 16:49 ` Eric Le Bihan [this message]
2017-04-13 21:09 ` 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=b2b48a0cb1c4d27ecbdd9d510e0bdb87@free.fr \
--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