ci: use Docker directly instead of cross to avoid host toolchain resolution
Some checks failed
Build MIPS Binary / build (push) Failing after 31s
Some checks failed
Build MIPS Binary / build (push) Failing after 31s
This commit is contained in:
@@ -40,11 +40,13 @@ jobs:
|
|||||||
fi
|
fi
|
||||||
|
|
||||||
- name: Build Backend (MIPS)
|
- name: Build Backend (MIPS)
|
||||||
env:
|
|
||||||
CROSS_NO_WARNINGS: 0
|
|
||||||
run: |
|
run: |
|
||||||
cd backend
|
docker run --rm \
|
||||||
cross +nightly build --target mips-unknown-linux-musl --release -Z build-std=std,panic_abort
|
-v "$PWD":/project \
|
||||||
|
-v "$HOME/.cargo/registry":/root/.cargo/registry \
|
||||||
|
-w /project \
|
||||||
|
ghcr.io/cross-rs/mips-unknown-linux-musl:main \
|
||||||
|
sh -c 'rustup default nightly && rustup component add rust-src && cd backend && cargo build --target mips-unknown-linux-musl --release -Z build-std=std,panic_abort'
|
||||||
|
|
||||||
- name: Rename Binary
|
- name: Rename Binary
|
||||||
run: mv target/mips-unknown-linux-musl/release/backend target/mips-unknown-linux-musl/release/vibetorrent-mips
|
run: mv target/mips-unknown-linux-musl/release/backend target/mips-unknown-linux-musl/release/vibetorrent-mips
|
||||||
|
|||||||
Reference in New Issue
Block a user