feat: add OpenWrt ipk packaging support for x86_64 and aarch64 - #288
Open
hashbk wants to merge 4 commits into
Open
feat: add OpenWrt ipk packaging support for x86_64 and aarch64#288hashbk wants to merge 4 commits into
hashbk wants to merge 4 commits into
Conversation
Ship prebuilt musl SEA binaries (Node.js + sqlite3 + sharp) as .ipk packages for OpenWrt/ImmortalWrt soft routers, managed via procd. - Add scripts/build-openwrt-ipk.sh to assemble .ipk from SEA dist - Add openwrt/ feed: Makefile (binary package), procd init script, default env config, and README - Extend release.yml and nightly.yml with a musl-build job that builds SEA in node:24-alpine (musl) for linux/amd64 and linux/arm64, packages .ipk, and uploads tarball + ipk to the release - Document OpenWrt deployment in README.md
Add build-openwrt-apk.sh to produce .apk packages (apk-tools 3.x / OpenWrt 24.10+) using concatenated control + data tar.gz streams with .PKGINFO metadata. Both .ipk and .apk are now built and uploaded in release and nightly workflows.
The previous .apk builder produced concatenated tar.gz streams which is the legacy v2 format. OpenWrt 24.10+ snapshots use apk-tools 3.x which expects the new ADB binary format. Rewrite build-openwrt-apk.sh to use 'apk mkpkg' inside an alpine:edge container, and update the workflows to invoke the script there. Also convert nightly version suffixes (-nightly.) to apk-compatible _p suffixes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add OpenWrt/ImmortalWrt deployment support by shipping prebuilt musl SEA binaries as
.ipkpackages for x86_64 and aarch64 soft routers, managed viaprocd.Changes
scripts/build-openwrt-ipk.sh— assembles a.ipk(data + control archive viaar) from the SEA dist directory, with procd init script, default config, and wrapper.openwrt/— OpenWrt feed definition:Makefile(binary package style: downloads prebuilt musl tarball from Releases; no Node.js compilation in buildroot)files/rustdesk-console.init(procd init: respawn, env injection from config file)files/rustdesk-console.env(default config, conffile)README.md(install, config, feed integration docs).github/workflows/release.yml/nightly.yml— newmusl-buildmatrix job: builds SEA innode:24-alpine(musl) forlinux/amd64andlinux/arm64, packages.ipk, uploads tarball + ipk to the release.README.md— OpenWrt deployment section.Why musl needs a separate build
The existing
linux-x64/linux-arm64SEA artifacts are built on Ubuntu (glibc) and won't run on OpenWrt (musl). This PR builds SEA insidenode:24-alpineto produce musl binaries;sqlite3andsharpautomatically pick up theirlinuxmuslprebuilds.Notes
openwrt/README.md).sharpis retained (soft routers have sufficient resources).Depends: libc, libstdcpp, libgcc.Close #287