text
.__ __
___________|__|/ |_
_/ ___\_ __ \ \ __\
\ \___| | \/ || |
\___ >__| |__||__|
\/
Work in progress.
```console $ cd example
$ crit
$ ls .crit aarch64-apple-darwin aarch64-linux-android aarch64-unknown-linux-gnu ... ```
By default, crit builds in release mode (-- -r).
See crit -h for more options.
https://crates.io/crates/crit
https://github.com/mcandre/crit/releases
console
$ cargo install --path .
FreeBSD
asdf reshim after each Rust application binary installation)For more details on developing crit itself, see DEVELOPMENT.md.
First, check that your project is able to build with conventional cross or cargo commands. A project which does not compile, will naturally have difficulty cross-compiling.
Note that Rust introduces new, under-supported targets all the time. We try to keep up, but sometimes we miss a few of these. Regardless, you can declare which targets are disabled, by writing a custom pattern for the -e / --exclude-targets flag.
Some targets may lack stock support for the Rust std library. This is common for bare metal or embedded targets. For these kinds of targets, you have several strategies for resolution:
std implementation. Reach out to specialists for the specific target involved.std library, in both your code, as well as the dependency tree. This is actually common practice for many Rust projects, as an proactive stance on embedded development support.