cargo-sysroot 0.4.1

Simply and Easily cross-compile the Rust sysroot crates.
cargo-sysroot-0.4.1 is not a library.
Visit the last successful build: cargo-sysroot-0.8.1

Cargo-sysroot

Crates.io maintenance-as-is

A (dumb) tool to compile libcore and friends for no_std crates.

This is not a wrapper like cargo xbuild or xargo, this is a standalone tool you call once.

Prerequisite

  • A nightly compiler.
  • The rust-src component must be installed for the active toolchain.
  • Your Cargo.toml file must contain package.metadata.cargo-sysroot.target, where target is a target specifiction json file.
    • A rust supported target may also work, but this is untested.
  • OR Pass --target on the commandline, ex cargo sysroot --target path/to/target.json

Example Cargo.toml

[package]
name = "My Project"
version = "0.1.0"
authors = ["Me <Me@Me.com>"]

[package.metadata.cargo-sysroot]
target = "my_custom_target.json" # This is relative to Cargo.toml

Getting Started

  • Run cargo install cargo-sysroot.
  • Run cargo sysroot in the working directory of your project.

This tool will generate a .cargo/config for you that looks something like this

[build]
target = "path/to/your/target/specification/json"
rustflags = [
    "--sysroot",
    "full/path/to/target/sysroot",
]

The sysroot will be located at target/sysroot and the libcore target directory at target/sysroot/target. Multiple target specifictions are supported and will not conflict, and due to the way rust uses the sysroot your generated .cargo/config should not need to be changed, as the base path it uses is not target specific.

Note that this tool is currently quite stupid, so it won't attempt to do anything if that file already exists.

This will allow Cargo to properly build your project with the normal commands such as cargo build. You may wish to modify this file to make use of the target.$triple.runner key. See the Cargo Documentation for details. Note that the author experienced problems with the $triple variant not working, and you may experience better success with the cfg variant.

If you update your Rust nightly version you will need to run cargo-sysroot again. Note that doing this will cause cargo to detect that libcore has changed and rebuild your entire project.

Recomendations

It is recomended you use a tool such as cargo-make if you want to automate this and other pre/post build tasks.

Details

libcore and friends are compiled with the --release switch. libcompilter_builtins is built with the mem feature, which provides memcpy and friends.

TODO

  • Allow specifying a custom rust-src.
  • Allow disabling the mem feature.
  • Liballoc.

Limitations

  • Liballoc is currently unsupported.

FAQ

  • Q: Why are all versions before 0.4.1 yanked?
  • A: They didn't work correctly or at all because i didnt test properly. Oops.

License

Licensed under either of

at your option.

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.