ztr/CPC
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

Update cross-compile instructions to work for Rust 1.50

Browse Source
This commit is contained in:
Kasper 2021-03-24 17:58:34 +01:00
parent 794b47e448
commit c59918b080
1 changed files with 12 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
README.md
View File

@ -179,22 +179,23 @@ match string {
- Angles - Angles
- Flow rate - Flow rate
### Cross-compiling ### Cross-compiling (from x86_64 macOS)
For some reason `cross` stopped working for me in Rust 1.50 ([rust-lang/rust#83154](https://github.com/rust-lang/rust/issues/83154)).
1. [Install Docker](https://docs.docker.com/get-docker/) 1. [Install Docker](https://docs.docker.com/get-docker/)
2. Install [cross](https://github.com/rust-embedded/cross): 2. Install [`cross`](https://github.com/rust-embedded/cross). `cross` works by installing toolchains for whatever target you're building for, then using those toolchains to compile in Docker containers
``` ```
cargo install cross cargo install cross
``` ```
3. Build for x86_64 macOS, Linux and Windows: 3. Set rustup profile to minimal. This means things like `rustdoc` won't be included in new toolchain installations. You can run `rustup set profile default` to reset this afterwards.
```sh
cargo build --release --target x86_64-apple-darwin && cross build --release --target x86_64-unknown-linux-musl && cross build --release --target x86_64-pc-windows-gnu
``` ```
- Building for `x86_64-apple-darwin` only works on macOS rustup set profile minimal
- For more targets, check out [the targets `cross` supports](https://github.com/rust-embedded/cross#supported-targets) ```
- If you run `cross build` in parallel, you might get a `cargo not found` error 4. Build for x86_64 macOS, Linux and Windows. For more targets, check out [the targets `cross` supports](https://github.com/rust-embedded/cross#supported-targets)
```
The compiled binaries will now be available inside `target/<target>/release/`. The filename will be either `cpc` or `cpc.exe`. cargo build --release --target x86_64-apple-darwin &&
cross build --release --target x86_64-unknown-linux-musl &&
cross build --release --target x86_64-pc-windows-gnu
```
5. The compiled binaries will now be available inside `target/<target>/release/`. The filename will be either `cpc` or `cpc.exe`.
### Releasing a new version ### Releasing a new version