staging/xback/target/sdk, branch master

libstd-rust: build and package the Rust standard library

2026-10-30T10:06:08Z

Build the sysroot crate with the selected Cargo and rustc, using the source tarball's vendored crates and shared target CPU flags. Stage the rlibs and shared library through normal package-owned target staging, and include that sysroot in the SDK. Separate Cargo output by ABI identity to keep dependency artefacts from different configurations in their own build directories. Name the shared library and package ABI from compiler, source, target and build configuration inputs, with configuration changes triggering a rebuild. Declare libgcc as a runtime dependency for libgcc_s.so.1. Release builds optimise for size, abort on panic and emit no unwind tables. They also take the size options of unstable rustc, which the sysroot build permits anyway: panics carry no location (-Zlocation-detail=none) and derived Debug output is reduced to type names (-Zfmt-debug=shallow). RUST_PANIC_IMMEDIATE_ABORT, on by default, builds with -Cpanic=immediate-abort and without the panic-unwind feature: a panic stops the program at once, without formatting a message. rustc requires the same panic strategy for all crates of a program, the standard library included, so this is a build-wide option. Debug builds retain unwinding, panic messages and full Debug output. Build paths are mapped out of the library as iremap in rules.mk does for C, unless CONFIG_DEBUG is set without CONFIG_REPRODUCIBLE_DEBUG_INFO. The map stays out of the inputs of the ABI identity, which would otherwise depend on the build path. rust-values.mk maps the OpenWrt target to its Rust target triple and CPU flags; the mapping is derived from lang/rust in the packages feed by Luca Barbato and Donald Hoskins. The mips64 ABI comes from CONFIG_MIPS64_ABI, which every mips64 configuration sets, and n64 maps to the muslabi64 and gnuabi64 triples. These are hard-float, so soft-float mips64 with musl uses mips64-openwrt-linux-musl, the soft-float n64 target of rustc, and the other soft-float mips64 and mips64el configurations, which have no Rust target, get no Rust packages. The e500v2 of mpc85xx has no FPU but shares the hard-float powerpc triple, whose hard-float feature is turned off with CONFIG_SOFT_FLOAT. When the target triple is the build host's, as for x86_64 and aarch64 glibc targets, Cargo links build scripts with the target linker as well but keeps target rustflags off them, so the target linker is passed as a rustflag in that case. include/scan.mk rescans the package metadata when an include/rust-*.mk file changes, as for include/package*.mk. Co-developed-by: Brian Redbeard Signed-off-by: Brian Redbeard Co-developed-by: Aditya Nugraha Signed-off-by: Aditya Nugraha Signed-off-by: Daniel Golle

sdk: add support to sign each .apk package by sdk

2026-04-29T10:43:54Z

Add support to signing each package's .apk file into SDK. This adds into SDK the feature added by f20794a to the normal builds. Currently SDK does not sign the compiled packages, causing untrusted package errors at package installation. The reason is the logic of defaulting to 'n' in BUILDBOT and 'y' elsewhere. As downloadable SDKs are compiled by the buildbot, the option gets 'n' set as the default. And the option is not among the few build options exposed in the SDK menuconfig, so the user can't easily change it. Enable the feature by default: * Exclude the SIGN_EACH_PACKAGE option from sdk/convert-config.pl * Default to 'y' and expose the option in the SDK config menu. (Avoiding untrusted errors naturally requires the user to copy the public key into the router, quite similar as with full builds.) Signed-off-by: Hannu Nyman Link: https://github.com/openwrt/openwrt/pull/23104 Signed-off-by: Robert Marko

sdk: use TOOLCHAIN_DIR_NAME for STAGING_SUBDIR_TOOLCHAIN

2026-03-10T12:34:31Z

Like a STAGING_SUBDIR_TARGET which uses TARGET_DIR_NAME, we can use TOOLCHAIN_DIR_NAME for STAGING_SUBDIR_TOOLCHAIN to avoid code duplication. Signed-off-by: Nikita Ostrenkov Link: https://github.com/openwrt/openwrt/pull/22315 Signed-off-by: Christian Marangi

toolchain: sdk: ib: allow external toolchain override

2026-02-20T21:54:26Z

Allow building imagebuilder and/or sdk with dependency on the same external toolchain as used to build the imagebuilder or sdk (so that ib and sdk may be built using an external toolchain). Signed-off-by: Daniel Dickinson Original patch: https://lists.openwrt.org/pipermail/openwrt-devel/2016-January/012552.html [rebased to current main, impvove commit title] Signed-off-by: Pawel Dembicki Link: https://github.com/openwrt/openwrt/pull/22089 Signed-off-by: Robert Marko

treewide: drop CVS support

2026-02-13T14:40:13Z

We have no CVS-managed package in official repositories. This commit drops obsolete SCM system support. Signed-off-by: Yanase Yuki Link: https://github.com/openwrt/openwrt/pull/21340 Signed-off-by: Robert Marko

sdk: use GIT_COMMIT for buildbot SDK

2025-12-04T18:20:55Z

Instead of using tag name, directly use git commit for the base feed string if we detect we are generating an SDK from a buildbot (using CONFIG_BUILDBOT) This improve security and generates consistent feed.conf.default files following the pattern used by feeds repository. Signed-off-by: Christian Marangi

sdk: invert logic for GIT_BRANCH and GIT_TAGNAME

2025-12-04T18:20:38Z

There is currently a logic error with generating the base feed string. In the scenario where the commit of a Tag match the latest commit of a stable branch, the stable branch have priority over the tag name. This results in generating SDK that actually target the branch instead of the specific tag. To fix this invert the logic and give priority to the tag name. Fixes: #18583 Signed-off-by: Christian Marangi

sdk: filter out main on GIT_BRANCH parsing

2025-12-04T18:08:08Z

Branch named main was never filter out on parsing the GIT_BRANCH define. Add main to the name of branch that should be filtered. Signed-off-by: Christian Marangi

Revert "sdk: use git-src-full to allow Git versioning"

2025-10-29T20:09:57Z

This reverts commit f795ecc0ddb40a3d796e6faaa177b545923efc70. Now that AUTORELEASE has been dropped from main, we can go back on shallow clone it for faster SDK usage. Link: https://github.com/openwrt/openwrt/pull/20586 Signed-off-by: Christian Marangi

sdk: set package as the root directory for base feed

2025-10-13T09:47:08Z

To produce consistent source entry for package compiled from non-SDK and SDK build, set the "--root=package" flag for the base feed. This will set the root directory for the base feed to the OpenWrt core repository "package" directory. This fix the reproducible problem of package build from SDK that have the source entry set to "feeds/base/package/..." for every package coming from the base feed. Link: https://github.com/openwrt/openwrt/pull/20396 Signed-off-by: Christian Marangi