CI: build inside bread-ecosystem's shared Arch container
All checks were successful
dev release / build (push) Successful in 5m25s
All checks were successful
dev release / build (push) Successful in 5m25s
Ports breadsearch onto the shared, pinned Arch build image already proven in breadpad, so this repo's release CI stops installing its toolchain/GTK4 stack directly on the bare self-hosted runner. - ci/build.sh + ci/bread-ecosystem.rev: thin wrapper cloning bread-ecosystem pinned to a commit sha and delegating to its own ci/build.sh. - dev-release.yml/rc-release.yml/release.yml: route the existing build/test cargo invocations through ci/build.sh, unchanged otherwise. - check.yml: fast clippy/test signal on feature/** and fix/** pushes. No ci/deps.txt: breadmill's npu/rocm/cuda/openvino features (pulled in by --features full) all use ort's load-dynamic (dlopen) mode, so none of them link against a real ONNX Runtime EP at build time — confirmed against breadmill/Cargo.toml and by breadpad already building ort with its own rocm feature against the same base image with no extra packages. The GUI's librsvg system dep is a runtime icon-loader dependency (bakery.toml's system_deps), not something linked at build/link time, so the base image's gtk4/gtk4-layer-shell already cover what compiling breadsearch needs.
This commit is contained in:
parent
0e3c8a1668
commit
4f9f4de911
6 changed files with 52 additions and 6 deletions
1
ci/bread-ecosystem.rev
Normal file
1
ci/bread-ecosystem.rev
Normal file
|
|
@ -0,0 +1 @@
|
|||
147cfbbf96ae4b171027defa1130d2caddb934b1
|
||||
Loading…
Add table
Add a link
Reference in a new issue