mirror of
https://github.com/Klipper4FlashForge/firmware.git
synced 2026-10-22 21:32:16 -05:00
Oleksandr ShyshatskyiandClaude Opus 5
2e9f2214a0
Master moved twelve commits while this branch ran: patch.sh became
payload.sh, run-pre.sh and run-append.sh became runFirmwareExe.sh, the
install manifest and anvil.conf are gone, and versions.env was trimmed
harder there than here (53 comment lines against 185).
Resolved so the merge contributes comments and nothing else. Verified
mechanically: every one of the 270 files in the tree now carries
exactly master's code, and no file this branch touched is resurrected.
- master's deletions accepted: bin/patch.sh, bin/verify.sh,
installer/run-{pre,append}.sh, anvil.conf.in
- versions.env: master's, which is the better trim
- 26 files master only renamed through: this branch's trim kept, with
patch.sh -> payload.sh applied
- 14 files master rewrote to describe the new installer: master's
text taken wholesale, to be re-trimmed separately
- stale references to the manifest and run-append.sh corrected in
pkgs/3rdparty/busybox/build.sh and pkgs/moonraker/build.sh
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NMMpQTajN7RDJySrhQ2cTE
42 lines
1.9 KiB
Plaintext
42 lines
1.9 KiB
Plaintext
# What bin/build-packages.sh needs to turn build.sh's output into an .ipk.
|
|
# Sourced, so it is shell and may read anything bin/common.sh exports -- which
|
|
# is where $SODIUM_VERSION comes from, so the version in the package is the
|
|
# pin in versions.env and cannot be set twice.
|
|
#
|
|
# THE FIRST RECIPE, and the shape every later one should copy: a build.sh that
|
|
# leaves a $MODDIR-relative tree under work/, and this file saying what to
|
|
# call it. Nothing here knows how libsodium is compiled and nothing in
|
|
# build.sh knows what a package is.
|
|
PKG_NAME=anvil-libsodium
|
|
PKG_VERSION="$SODIUM_VERSION"
|
|
|
|
# The PACKAGING revision, bumped when this recipe changes but the upstream
|
|
# version does not. opkg compares `1.0.20-1` against `1.0.20-2` and upgrades,
|
|
# which is the only way to ship a repackage without lying about which
|
|
# libsodium is inside.
|
|
PKG_RELEASE=1
|
|
|
|
PKG_SECTION=libs
|
|
|
|
# The tree to package, laid out the way it should appear under $MODDIR --
|
|
# which is exactly what build.sh already produces for bin/payload.sh to copy
|
|
# into the payload, so no restaging happens here.
|
|
PKG_ROOT="$SODIUM_BUILD"
|
|
|
|
# build.sh's cache stamp lives in that tree and is a build artefact, not a
|
|
# shipped file. Left in, it would install as $MODDIR/.version.
|
|
PKG_EXCLUDE=".version"
|
|
|
|
# No Depends. libsodium links libc and nothing else, and libc is the rootfs's
|
|
# -- not ours to depend on. The field being genuinely empty rather than merely
|
|
# unwritten is worth stating.
|
|
PKG_DEPENDS=""
|
|
|
|
# Nothing to build against either: libsodium's own sources are the whole
|
|
# build. The field is here rather than left to default because its absence in
|
|
# a recipe that HAS dependencies is the bug it exists to prevent -- pkg_deps
|
|
# would fill an empty sysroot and configure would find the host's headers.
|
|
PKG_BUILD_DEPENDS=""
|
|
|
|
PKG_DESCRIPTION="NaCl-compatible crypto library. Loaded by ctypes from libnacl, which is how Moonraker's authorization component signs its ed25519 JWTs."
|