Paul Osborne
24f3b6d76b
This resolves https://github.com/jmesmon/meta-rust/issues/1. This change is only necessary for systems (like dizzy) that do not contain poky commit 60d504b431fa7cdc6ded141def7ae18edb1834e5. Without that commit or this change, do_compile for libgit2 would fail with the following error: CMAKE_AR-NOTFOUND cr libgit2.a ... Error running link command: No such file or directory Signed-off-by: Paul Osborne <osbpau@gmail.com>
Introduction
This openembedded layer provides the rust compiler, tools for building packages (cargo), and a few example projects.
What works:
- MACHINE="beaglebone" (TARGET_SYS=arm-poky-linux-gnueabi)
- Building rust-native, rust-cross, rust-hello-world, cargo-native
- Running/using all of these (including rust-hello-world)
What doesn't:
- Probably some of the untested things
What's untested:
- rust (built for target)
- Other TARGETs
Common issues when packaging things using cargo
You may run into errors similar to:
| src/lib.rs:12:1: 12:35 error: can't find crate for `ffi`
| src/lib.rs:12 extern crate "openssl-sys" as ffi;
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Where a "-sys" crate (or other crate) is not found. These are typically caused
by a crate's Cargo.toml including triplet-specific dependencies and then using
the crate based on a feature (most often, #[cfg(unix)]). Until cargo and it's
ecosystem get their act together, you'll need to supply patches to the
misbehaving packages. See recipies/cargo/cargo_*.bb for an example of how to
do this.
Cargo
Cargo may not work with the latest rust. You can try either:
-
use the system cargo:
CARGO_PROVIDED = "cargo-native" ASSUME_PROVIDED += "${CARGO_PROVIDED}"
-
or have cargo use a rust snapshot
PACKAGECONFIG_append_pn-cargo-native = " rust-snapshot"
Note that using the rust-snapshot currently has issues with the targets provided by bitbake, for it to work we need to generate the same target.json that we do for the main compiler.
TODO
- Include downloaded stage0 snapshot in
SRC_URI - -crosssdk and -buildsdk packages
- -runtime? (install target libraries on target)
- Add SRC_URI components so that cargo doesn't use the network
- Convince cargo (via env vars or patching) not to use '$HOME/.cargo' for storing downloaded source code
- Upstream local rustc patches for libdir and bindir support
Pitfalls
- TARGET_SYS must be different from BUILD_SYS. This is due to the way configuration options are tracked for different targets.
Dependencies
On the host: unknown
On the target: unknown
Maintainer(s) & Patch policy
Open a Pull Request
Copyright
MIT/Apache-2.0 - Same as rust