Repository navigation
feat(ci): add OpenHarmony CI and add it to tier2 - #2599
Conversation
|
Any idea what is the minimal Rust version required for these 3 targets? |
Maybe 1.70.0 and 1.73.0 I want to split it a unique task and use rust with 1.79.0, how about it? |
|
I tend to use the workaround that Loongarch uses:
|
Sorry for missing this, if 1.73 will work, we should use it (the minimal one) |
1.73 is tier3, if use 1.73, we need to add them into tier3 task. I think using 1.79 be better? |
Thanks for letting me know. Right, we want the Rust tier 2 support. According to this comment, we should use 1.78 as rust-lang/compiler-team#719 was included in 1.78 |
So sorry that i made a mistake in remembering :( and already fixed it. |
No need to be sorry:) |
The published cloud CI run failed: portable-pty 0.8.1 pulls nix 0.25.1 transitively, which predates OHOS support and misclassifies target_env="ohos" as glibc-shaped in its cfg_attr repr gating, producing type mismatches (u32 vs i32/usize) when cross-compiling aarch64-unknown-linux-ohos from a stock toolchain. nix 0.30+ added proper *-unknown-linux-ohos handling (nix-rust/nix#2599/#2587/#2456), but Cargo's [patch.crates-io] can't bump a transitive dependency to a different same-registry version ("patches must point to different sources") — so, mirroring the existing fix in the bun-pty Homebrew formula (Formula/b/bun-pty.rb), vendor a copy of portable-pty 0.9.0 with just its nix requirement bumped from "0.28" to "0.31", and path-depend on that instead of the crates.io version. Verified locally (native aarch64-unknown-linux-ohos build): compiles clean with nix 0.31.3 resolved, and a real dlopen + PTY spawn/kill round-trip still passes. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
What does this PR do
Add OpenHarmony target into CI and Update documents.
The official support: arm64,arm and x86_64, so i add three targets:
Checklist:
CONTRIBUTING.md