postit-debian/Makefile
Paul Schneider ad5bc578e7
Some checks failed
Forgejo Release postit-deb / release (push) Failing after 1m28s
Makefile + workflow: -Pcross profile, drop arm64 libs install
For the arm64 cross-build:
- dotnet publish --runtime linux-arm64 cross-compiles natively on
  amd64, no arm64 toolchain required.
- dpkg-buildpackage now runs with -Pcross (cross-build profile),
  which tells debhelper to skip arch-specific helper tools that
  aren't available on the host (e.g. aarch64-linux-gnu-objdump
  used by dh_makeshlibs).
- -d (--no-check-builddeps) skips the build-deps check for arm64
  because dotnet-sdk-10.0:arm64 isn't installed and we don't
  need it — the dotnet publish runs on the host, not on the
  target.

The workflow no longer installs libc6:arm64 etc. via multi-arch
— it was a workaround for dpkg-shlibdeps that we no longer need
once -Pcross handles the cross-build profile correctly.
2026-08-17 18:48:35 +01:00

99 lines
4.9 KiB
Makefile

# Makefile for the postit Debian package.
#
# Targets:
# make deb : build a .deb in the parent directory (or
# $POSTIT_OUT_DIR if set). Equivalent to
# dpkg-buildpackage -us -uc -b.
# make test : run the non-regression tests under tests/.
# The fetch test pins the upstream Git mechanics
# that previously regressed on tag-vs-branch
# handling (1.0.1-rc02). Set SKIP_NETWORK_TESTS=1
# to skip the GitHub-egress parts.
# make clean : rm -rf build/ and the per-package staging tree
# under debian/postit.
# make source : fetch the upstream yavsc source tree under
# build/yavsc-src (no packaging step). Useful for
# debugging the publish step.
#
# Environment overrides (or pass on the make command line):
# POSTIT_GIT_URL default: https://github.com/pazof/yavsc.git
# POSTIT_GIT_TAG default: 1.0.0
# POSTIT_RUNTIME default: linux-x64 (override to linux-arm64 etc.)
# POSTIT_OUT_DIR default: $(CURDIR)/.. (artifacts land here)
POSTIT_GIT_URL ?= https://github.com/pazof/yavsc.git
POSTIT_GIT_TAG ?= 1.0.6
POSTIT_RUNTIME ?= linux-x64
POSTIT_OUT_DIR ?= $(CURDIR)/..
.PHONY: deb clean source test
deb:
@echo " POSTIT_GIT_TAG=$(POSTIT_GIT_TAG) POSTIT_RUNTIME=$(POSTIT_RUNTIME) POSTIT_GIT_URL=$(POSTIT_GIT_URL)"
# Render debian/changelog from debian/changelog.in so the package
# version follows the upstream tag, not the version pinned in the
# repo. dpkg-buildpackage reads debian/changelog before any rule
# runs (in dpkg-source --before-build), so the template must be
# expanded in the Makefile, not in debian/rules. Without this
# step the .deb always comes out as the version hardcoded in
# debian/changelog.in, regardless of POSTIT_GIT_TAG.
sed 's/@VERSION@/$(POSTIT_GIT_TAG)/g' debian/changelog.in > debian/changelog
# Remove any residual .deb from previous runs (same name
# pattern would otherwise be re-used by dpkg-deb if the
# previous run left it lying around).
rm -f ../postit_*$(POSTIT_GIT_TAG)-1*.deb ../postit_*.buildinfo ../postit_*.changes
# Use dpkg-architecture to set the target arch correctly for
# cross-builds. For POSTIT_RUNTIME=linux-arm64, this exports
# DEB_HOST_ARCH=arm64 (and friends) so dpkg-buildpackage names
# the .deb postit_*_arm64.deb instead of postit_*_amd64.deb.
# For linux-x64, it sets the host arch to amd64 explicitly
# (which matches the runner — no-op, but keeps the call site
# uniform). Other RIDs are rejected.
# Compute DPKG_ARCH_ARGS, eval dpkg-architecture, then call
# dpkg-buildpackage — all in ONE shell invocation so the
# vars set by dpkg-architecture are visible to dpkg-buildpackage.
# make runs each recipe line in its own shell, so we use
# backslash continuation to glue everything together.
# Cross-build configuration for dpkg-buildpackage.
#
# We set DEB_HOST_ARCH=arm64 and pass -aarm64 directly to
# dpkg-buildpackage, bypassing dpkg-architecture.
#
# Why bypass dpkg-architecture? It's deliberately conservative:
# it refuses to set up the cross-build env when the C compiler
# (CC) doesn't match the target arch. Our package has no C
# code — dh_auto_build only runs \`dotnet publish --runtime
# linux-arm64\` (a managed-only cross-publish), and we
# disable dh_strip (the only rule that needed an arch-specific
# objcopy). dh_shlibdeps uses the multi-arch arm64 libs we
# apt-get install in the runner. So no arm64 toolchain is
# actually needed; the dpkg-architecture CC check would
# unnecessarily block us.
#
# We do explicitly set the four DEB_* vars dpkg-architecture
# would normally export (host arch, build arch, host GNU
# type, build GNU type) so debhelper rules see a consistent
# cross-build environment.
DPKG_HOST=$$(case "$(POSTIT_RUNTIME)" in linux-arm64) echo arm64 ;; linux-x64) echo amd64 ;; *) echo "unsupported POSTIT_RUNTIME=$(POSTIT_RUNTIME)" >&2; exit 1 ;; esac) && DEB_HOST_ARCH=$$DPKG_HOST DEB_BUILD_ARCH=amd64 DEB_HOST_GNU_TYPE=aarch64-linux-gnu DEB_BUILD_GNU_TYPE=x86_64-linux-gnu POSTIT_GIT_URL=$(POSTIT_GIT_URL) POSTIT_GIT_TAG=$(POSTIT_GIT_TAG) POSTIT_RUNTIME=$(POSTIT_RUNTIME) dpkg-buildpackage -us -uc -b -d -Pcross -a$$DPKG_HOST
# dpkg-buildpackage already writes the produced .deb to
# /src/_src/../ = $POSTIT_OUT_DIR (its default — there's no
# flag to change it). So no 'mv' is needed. The old 'mv'
# caused a 'same file' error when the destination was the
# same as the source (which it always is). Just verify the
# .deb was actually produced.
if ! ls ../postit_*$(POSTIT_GIT_TAG)-1*.deb >/dev/null 2>&1; then \
echo " ERROR: dpkg-buildpackage produced no .deb for POSTIT_GIT_TAG=$(POSTIT_GIT_TAG)" >&2; \
exit 1; \
fi
@echo " ✓ artifacts in $(POSTIT_OUT_DIR)"
clean:
rm -rf build debian/postit
source:
mkdir -p build
git clone --depth=1 --branch $(POSTIT_GIT_TAG) \
$(POSTIT_GIT_URL) build/yavsc-src
test:
@bash tests/test-fetch-upstream.sh