Skip to content
OpenEmbedded/Yocto layer for Rust and Cargo
Branch: master
Clone or download
Latest commit 0621067 Mar 5, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github
classes Correct proxy variable Feb 19, 2019
conf conf/layer.conf: Add thud to the LAYERSERIES_COMPAT Oct 20, 2018
lib drop the old fetch behavior for pre Cargo 0.13.0 Dec 7, 2016
recipes-devtools Update to rust version 1.33.0 Mar 2, 2019
recipes-example rustfmt: bump to 0.8.0 and use cargo-bitbake Jun 21, 2017
scripts Don't bother erroring out if the rsync fails Nov 3, 2017
.gitignore
COPYING.MIT
Jenkinsfile
README.md README: swath of updates to reflect the current state Dec 29, 2016

README.md

Introduction

This OpenEmbedded layer provides the rust compiler, tools for building packages (cargo), and a few example projects.

What works:

  • Building rust-native and cargo-native
  • Building Rust based projects with Cargo for the TARGET
    • e.g. rustfmt which is used by the CI system
  • -buildsdk and -crosssdk packages

What doesn't:

  • Using anything but x86_64 as the build environment
  • rust (built for target) issue #81

What's untested:

  • cargo (built for target)

Building a rust package

When building a rust package in bitbake, it's usually easiest to build with cargo using cargo.bbclass. If the package already has a Cargo.toml file (most rust packages do), then it's especially easy. Otherwise you should probably get the code building in cargo first.

Once your package builds in cargo, you can use cargo-bitbake to generate a bitbake recipe for it. This allows bitbake to fetch all the necessary dependent crates, as well as a pegged version of the crates.io index, to ensure maximum reproducibility.

NOTE: You will have to edit the generated recipe based on the comments contained within it

TODO

Pitfalls

  • TARGET_SYS must be different from BUILD_SYS. This is due to the way Rust configuration options are tracked for different targets. This is the reason we use the Yocto triples instead of the native Rust triples. See rust-lang/cargo#3349.

Dependencies

On the host:

  • Any -sys packages your project might need must have RDEPENDs for the native library.

On the target:

  • Any -sys packages your project might need must have RDEPENDs for the native library.

Maintainer(s) & Patch policy

Open a Pull Request.

The master branch supports the latest master of poky. When poky creates releases, we will create a branch with the same name as the poky release. This release branch should always work with that poky release. Note that these release branches will typically be less tested than the master branch.

All new patches against rust, rust-llvm, and cargo must have referenced upstream issues or PRs opened or an explanation why the patch cannot be upstreamed. This cooresponds to the OpenEmbedded policy for other meta layers.

More info can be seen on the wiki.

Copyright

MIT OR Apache-2.0 - Same as rust

You can’t perform that action at this time.