Pinned Upstream Release:
Chimera_Client v0.21.1Policy: All milestone references use a pinned semver tag. The moving
latesttag is never used as a stable reference.
This document maps OpenWrt target architectures to upstream Chimera_Client release artifacts for OpenChimera packaging. It is the single source of truth for what is supported, what is blocked, and what is excluded.
| Rust Target | musl/gnu | OpenWrt Compatible (M1) | Status |
|---|---|---|---|
x86_64-unknown-linux-musl |
musl | ✅ Supported | Milestone 1 primary target |
x86_64-unknown-linux-gnu |
gnu | ❌ Excluded | Not OpenWrt musl-compatible |
aarch64-unknown-linux-gnu |
gnu | ❌ Excluded | Not OpenWrt musl-compatible |
aarch64-unknown-linux-musl |
musl | ⏳ Deferred | Blocked — no upstream musl artifact confirmed |
| Icon | Meaning |
|---|---|
| ✅ Supported | Build target is tested and included in milestone 1. |
| ⏳ Deferred | Target is identified but blocked; will be enabled once upstream artifact is verified. |
| ❌ Excluded | Target will not be packaged — inherently incompatible with OpenWrt's musl libc requirement. |
- Status: Supported
- OpenWrt arch:
x86_64 - libc: musl
- Upstream artifact:
clash_chimera-x86_64-unknown-linux-musl(prebuilt binary) - Package:
chimera-coreinstalls to/usr/libexec/chimera - Alternatives:
/usr/bin/mihomo→/usr/libexec/chimera(priority 300)
- Status: Blocked
- OpenWrt arch:
aarch64_cortex-a53/aarch64_generic - libc: musl
- Upstream artifact:
aarch64-unknown-linux-musl— not confirmed in upstream CI - Reason: Metis research found that upstream CI only publishes
aarch64-unknown-linux-gnuartifacts. A musl variant must exist before OpenChimera can support aarch64. - Path to enablement:
- Upstream adds
aarch64-unknown-linux-muslto CI artifact matrix. - Artifact is downloaded and verified (hash, runtime test).
chimera-coreMakefile is updated to add aarch64 musl download block.- SDK compile QA confirms the package for aarch64 OpenWrt target.
- Upstream adds
The following targets produce glibc-linked binaries incompatible with OpenWrt's musl-based libc:
| Target | Why Excluded |
|---|---|
x86_64-unknown-linux-gnu |
glibc-linked — cannot run on OpenWrt musl |
aarch64-unknown-linux-gnu |
glibc-linked — cannot run on OpenWrt musl |
OpenChimera will never package gnu-linked binaries as OpenWrt-compatible. If the upstream CI only provides gnu artifacts for a given architecture, that architecture is considered blocked until a musl variant is published.
- Repository: MFSGA/Chimera_Client
- Pinned version:
v0.21.1 - Version field pattern (per OpenWrt convention, after
.ref/OpenWrt-nikki/mihomo-meta/Makefile):PKG_VERSION:=0.21.1 PKG_SOURCE_VERSION:=v0.21.1
- Artifact naming convention:
clash_chimera-{rust-target}
- Every release of
chimera-corereferences a specific pinnedPKG_VERSION/PKG_SOURCE_VERSION. - The
latesttag is never used — all references are immutable semver tags (v0.21.1, etc.). - Version bumps require:
- New upstream release tag exists
- Artifact hashes are verified
- SDK compile QA passes for all supported architectures
Per upstream .github/workflows/ci.yml, the following artifacts are published:
| Rust Target | Present in CI | musl/gnu |
|---|---|---|
x86_64-unknown-linux-musl |
✅ Yes | musl |
x86_64-unknown-linux-gnu |
✅ Yes | gnu |
aarch64-unknown-linux-gnu |
✅ Yes | gnu |
aarch64-unknown-linux-musl |
❌ No | musl (absent) |
This confirms that aarch64-unknown-linux-musl is not currently produced upstream, blocking aarch64 support until upstream CI is updated.