From: Eric Le Bihan <eric.le.bihan.dev@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Adding support for the Rust programming language
Date: Fri, 8 Apr 2016 22:45:41 +0200 [thread overview]
Message-ID: <20160408224541.79e1ba4d@itchy> (raw)
Hi all!
I've posted a series of articles about using the Rust programming
language in a Buildroot environment [1].
Rust [2] is a modern, compiled, programming language, oriented towards
safety, memory control and concurrency. Its performances are comparable
to C++.
Rust's features make it a good candidate for writing programs for
embedded systems.
This series will hopefully lead to some patches for properly supporting
Rust in Buildroot.
As explained in one article [3], the Rust compiler is based on LLVM
[4]. When configuring the build, the targeted architecture is given by
its GNU triplet (e.g. "arm-buildroot-linux-gnueabihf"). By default, the
compiler is built with support for x86, ARM and MIPS support
(unfortunately, there is no option to narrow the selection). Then the
Rust standard library is cross-compiled for the configured architecture.
Support for the target is achieved by providing two files:
- the target configuration file: a Makefile fragment where, among
others, the name of of the cross-compiler is given.
- the target specification file: a JSON file describing the
architecture (CPU type, OS, etc).
So, in the future patch series that will properly add support for Rust
in Buildroot:
1. Would it be acceptable to provide a script to generate these files
from the Buildroot configuration file?
2. Would Python be a suitable language for this script? It is better
suited for playing with complex structures and JSON than pure shell.
Comments welcomed.
[1] http://www.elebihan.com/categories/rust.html
[2] https://rust-lang.org/
[3] http://www.elebihan.com/posts/using-rust-with-buildroot-full-build.html
[4] https://llvm.org/
Best regards,
--
ELB
next reply other threads:[~2016-04-08 20:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 20:45 Eric Le Bihan [this message]
2016-04-10 15:57 ` [Buildroot] Adding support for the Rust programming language Arnout Vandecappelle
2016-04-11 8:32 ` Thomas Petazzoni
2016-04-11 9:12 ` Arnout Vandecappelle
2016-04-11 9:13 ` Arnout Vandecappelle
2016-04-11 9:31 ` Thomas Petazzoni
2016-04-11 9:15 ` Baruch Siach
2016-04-11 9:29 ` Arnout Vandecappelle
2016-04-11 11:42 ` Thomas De Schampheleire
2016-04-11 19:03 ` Eric Le Bihan
2016-04-12 20:22 ` 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=20160408224541.79e1ba4d@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.