Skip to content

Take the heads' build and packaging from PlatformHeads #51

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
SimonCropp merged 2 commits into from
Oct 11, 2026
Merged

Take the heads' build and packaging from PlatformHeads #51

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8dde07b
Take the heads' build and packaging from PlatformHeads
SimonCropp Oct 11, 2026
621bcee
Add the seven files the commit before this one left out
SimonCropp Oct 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
222 changes: 22 additions & 200 deletions .github/workflows/build-native.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,12 @@ name: Build native
# They are committed rather than built during a normal build so that a plain
# `dotnet build src --configuration Release` produces a shippable package on any machine, and
# contributors never need a C++ toolchain. Run this whenever native/ changes.
#
# The work is PlatformHeads' build-native workflow, which DiffEngine's viewer is built by too: the
# Linux library built in a manylinux_2_28 container and checked for the glibc it needs and the
# libraries it records as needed, the universal dylib, and the pull request with the binaries.
# Each of those was once a copy here, and a fix made to the other copy did not reach this one.
# The tag is the one native/CMakeLists.txt fetches and Directory.Packages.props names.
on:
push:
paths:
Expand All @@ -27,206 +33,22 @@ concurrency:
cancel-in-progress: true

jobs:
build:
name: ${{ matrix.rid }}
runs-on: ${{ matrix.os }}
timeout-minutes: 45
strategy:
fail-fast: false
matrix:
include:
# No Windows entries. That head renders with WinForms and loads no native library.
- rid: linux-x64
os: ubuntu-24.04
- rid: linux-arm64
os: ubuntu-24.04-arm
# One universal binary covers both macOS RIDs; it is copied into each below.
- rid: osx
os: macos-14
steps:
- name: Checkout
uses: actions/checkout@v7

# In a manylinux_2_28 container rather than on the runner, for its glibc 2.28, which is
# RHEL 8's. A library records the glibc symbol versions of the headers it was compiled
# against, and the loader refuses it anywhere older. Built on the runner's own Ubuntu 24.04
# it needed GLIBC_2.38, so the Linux head could not load it on Ubuntu 22.04, Debian 12, or
# RHEL 8 or 9, and BuildMonitor exited there without opening a window.
- name: Build
if: runner.os == 'Linux'
run: docker run --rm -v "$PWD:/src" -w /src "quay.io/pypa/manylinux_2_28_$(uname -m)" bash native/build-linux.sh

# The floor the container is there to hold, checked rather than trusted, since nothing else
# would notice until a user on an older distribution did.
- name: Check glibc floor
if: runner.os == 'Linux'
env:
GLIBC_FLOOR: GLIBC_2.28
run: |
highest=$(objdump -T build/libbuildmonitor_ui.so | grep -o 'GLIBC_[0-9][0-9.]*' | sort -uV | tail -n 1)
echo "Highest glibc symbol version required: $highest"
if [ "$(printf '%s\n' "$GLIBC_FLOOR" "$highest" | sort -V | tail -n 1)" != "$GLIBC_FLOOR" ]; then
echo "::error::libbuildmonitor_ui.so requires $highest, above the $GLIBC_FLOOR floor"
exit 1
fi
# libGL.so.1 is on every machine with a GL driver; libOpenGL.so.0 is not
if objdump -p build/libbuildmonitor_ui.so | grep -q 'NEEDED.*libOpenGL'; then
echo "::error::libbuildmonitor_ui.so links libOpenGL.so.0 rather than libGL.so.1"
exit 1
fi

# Everything recorded as needed has to be on a machine for the library to load at all, so
# the list is held to what any machine that runs .NET and has a display already has. The
# container's linker records every library it is handed, used or not, and raylib hands on
# libSM and libICE, which a stock Ubuntu lacks. native/CMakeLists.txt links with --as-needed
# so that neither is recorded, and this is what notices the list growing by any other route.
- name: Check needed libraries
if: runner.os == 'Linux'
env:
ALLOWED: >-
libc.so.6 libm.so.6 libdl.so.2 libpthread.so.0 librt.so.1 libstdc++.so.6 libgcc_s.so.1
libX11.so.6 libGL.so.1 ld-linux-x86-64.so.2 ld-linux-aarch64.so.1
run: |
needed=$(objdump -p build/libbuildmonitor_ui.so | awk '$1 == "NEEDED" { print $2 }')
echo "Needed:" $needed
failed=0
for library in $needed; do
case " $ALLOWED " in
*" $library "*) ;;
*)
echo "::error::libbuildmonitor_ui.so needs $library, which is not in the list of libraries it may need"
failed=1
;;
esac
done
exit $failed

# macOS draws with AppKit and Core Text rather than raylib and ImGui, so it is a Swift
# package rather than a CMake project. Both --arch flags in one invocation produce a
# universal binary, so there is no separate lipo step.
- name: Build
if: matrix.rid == 'osx'
run: swift build -c release --arch arm64 --arch x86_64 --package-path native/swift

# The folder panel, and turning AppKit's frames into the ABI's placements, are what this head
# decides by itself rather than drawing from a screen the managed side built, so they are
# what has tests here. A scratch path of its
# own, because a test build is debug and for this machine's architecture alone: left in .build
# its dylib would be among the candidates the collect step below merges.
- name: Test
if: matrix.rid == 'osx'
run: swift test --package-path native/swift --scratch-path native/swift/.build-tests

- name: Collect
shell: bash
run: |
# Laid out as src/{head}/runtimes/{rid}/native, so the propose job below can merge every
# artifact straight into src and the binaries land in the head that loads them.
collect() {
mkdir -p "artifacts/$1/runtimes/$2/native"
cp "$3" "artifacts/$1/runtimes/$2/native/"
}
case "${{ matrix.rid }}" in
linux-*)
# Already stripped, inside the container that owns the build directory
collect BuildMonitor.Native "${{ matrix.rid }}" build/libbuildmonitor_ui.so
;;
osx)
# swift build leaves a per architecture dylib in more than one place. Every candidate
# is checked, and if none is already universal they are merged, so the only thing
# that can be collected is a fat binary. The dSYM holds a DWARF file of the same
# name which is also universal, so it is excluded by path.
candidates=$(find native/swift/.build -name libbuildmonitor_ui.dylib -not -path '*.dSYM/*')
if [ -z "$candidates" ]; then
echo "::error::swift build produced no libbuildmonitor_ui.dylib"
exit 1
fi

dylib=""
for candidate in $candidates; do
archs=$(lipo -archs "$candidate" 2>/dev/null || echo "")
if [[ "$archs" == *x86_64* && "$archs" == *arm64* ]]; then
dylib="$candidate"
break
fi
done

if [ -z "$dylib" ]; then
dylib=universal/libbuildmonitor_ui.dylib
mkdir -p universal
# shellcheck disable=SC2086
lipo -create $candidates -output "$dylib"
fi

archs=$(lipo -archs "$dylib")
echo "collecting $dylib: $archs"
for arch in x86_64 arm64; do
case " $archs " in
*" $arch "*) ;;
*) echo "::error::$dylib is missing the $arch slice"; exit 1 ;;
esac
done

strip -x "$dylib"
# The dylib is universal, so both macOS RIDs get the same file.
collect BuildMonitor.Native osx-x64 "$dylib"
collect BuildMonitor.Native osx-arm64 "$dylib"
;;
esac
ls -lhR artifacts

- name: Upload
uses: actions/upload-artifact@v7
with:
name: native-${{ matrix.rid }}
path: artifacts/
retention-days: 7

propose:
name: propose update
needs: build
# Also on push, not just manual dispatch. workflow_dispatch does not appear in the Actions UI
# until the workflow is on the default branch, so on a feature branch a push is the only way
# to trigger this.
#
# Branches only. Never on pull_request, which would mean opening a PR from a PR, and never on
# a tag: a tag checkout is a detached HEAD with no base branch to target.
if: >-
github.event_name != 'pull_request' &&
startsWith(github.ref, 'refs/heads/') &&
(github.event_name != 'workflow_dispatch' || inputs.commit)
runs-on: ubuntu-latest
native:
uses: SimonCropp/PlatformHeads/.github/workflows/build-native.yml@0.1.0
permissions:
contents: write
pull-requests: write
steps:
- name: Checkout
uses: actions/checkout@v7

- name: Download
uses: actions/download-artifact@v8
with:
pattern: native-*
merge-multiple: true
path: src

- name: Show what changed
run: |
ls -lhR src/BuildMonitor.Native/runtimes
git status --short

# A PR rather than a direct push: these are binaries, so the diff is not reviewable and the
# change deserves an explicit approval.
- name: Open pull request
uses: peter-evans/create-pull-request@v8
with:
branch: native-binaries-${{ github.ref_name }}
title: 'Rebuild native UI binaries'
commit-message: 'Rebuild native UI binaries'
body: |
Rebuilt `buildmonitor_ui` from `native/` for the four RIDs that load one.
Windows is not among them: that head renders with WinForms.

Produced by the `build-native` workflow from ${{ github.sha }}.
add-paths: |
src/BuildMonitor.Native/runtimes
with:
library: buildmonitor_ui
linux-runtimes: src/BuildMonitor.Native/runtimes
swift-package: native/swift
mac-runtimes: src/BuildMonitor.Native/runtimes
# The folder panel, and turning AppKit's frames into the ABI's placements, are what the
# macOS head decides by itself rather than drawing from a screen the managed side built, so
# they are what has tests there.
swift-test: true
# Also on push, not just manual dispatch. workflow_dispatch does not appear in the Actions
# UI until the workflow is on the default branch, so on a feature branch a push is the only
# way to trigger this.
propose: ${{ github.event_name != 'workflow_dispatch' || inputs.commit }}
pull-request-title: Rebuild native UI binaries
2 changes: 1 addition & 1 deletion .github/workflows/build.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -70,7 +70,7 @@ jobs:
if-no-files-found: ignore
retention-days: 14

# BM0001 warns when a RID has no native renderer. Shipping a package that cannot run on a
# PH0001 warns when a RID has no native renderer. Shipping a package that cannot run on a
# platform it claims to support is worse than failing the release.
- name: Verify every RID has a native renderer
if: startsWith(github.ref, 'refs/tags/')
Expand Down
3 changes: 2 additions & 1 deletion claude.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -61,7 +61,8 @@ BuildMonitor is a tray app that polls CI services and shows one row per pipeline
- `Auth/` — OAuth browser flow (PKCE + loopback listener), device flow, and per-OS secret stores. Secrets never go in settings.json.
- `Protocol/` — the loopback socket the tray binds (single-instance gate) and the line protocol the launcher and the MCP server use to talk to it.
- `src/BuildMonitor.Windows/` — WinForms head (`BuildMonitor.Tray.exe`): `NotifyIcon` tray, owner-drawn rows, real controls for form pages.
- `src/BuildMonitor.Native/` — macOS and Linux head (`BuildMonitor.Tray`) over the C ABI in `native/include/bm.h`; Swift/AppKit on macOS (`native/swift`), raylib + Dear ImGui on Linux (`native/`). Binaries are committed under `runtimes/{rid}/native` and regenerated by the `build-native` workflow, which opens a PR. The Linux library is built in a `manylinux_2_28` container (`native/build-linux.sh`), so it needs no glibc newer than 2.28: built on the runner's own Ubuntu 24.04 it needed 2.38, and would not load on Ubuntu 22.04 or Debian 12. It is linked with `--as-needed`, since that container's linker otherwise records libSM and libICE, which a stock Ubuntu lacks, and `build-native` fails a build above the floor or one whose `NEEDED` entries are outside a short list. The Linux tray is StatusNotifierItem over D-Bus in managed code.
- `src/BuildMonitor.Native/` — macOS and Linux head (`BuildMonitor.Tray`) over the C ABI in `native/include/bm.h`; Swift/AppKit on macOS (`native/swift`), raylib + Dear ImGui on Linux (`native/`). Binaries are committed under `runtimes/{rid}/native` and regenerated by the `build-native` workflow, which opens a PR. The Linux library is built in a `manylinux_2_28` container, so it needs no glibc newer than 2.28: built on the runner's own Ubuntu 24.04 it needed 2.38, and would not load on Ubuntu 22.04 or Debian 12. It is linked with `--as-needed`, since that container's linker otherwise records libSM and libICE, which a stock Ubuntu lacks, and `build-native` fails a build above the floor or one whose `NEEDED` entries are outside a short list. The Linux tray is StatusNotifierItem over D-Bus in managed code.
- The build and packaging of the heads is PlatformHeads' (`D:\Code\PlatformHeads`, github.com/SimonCropp/PlatformHeads), which DiffEngine's viewer is to share: it was a copy here, and fixes made to DiffEngine's copy did not reach this one. Three pins name one tag of it and move together: the `uses:` of `.github/workflows/build-native.yml`, the `GIT_TAG` in `native/CMakeLists.txt`, and `PlatformHeads` in `Directory.Packages.props`. The workflow is its reusable `build-native`; the CMake module pins raylib and Dear ImGui and carries the raylib 6.0 option workarounds; the package's targets publish and bundle the `PlatformHead` items of `BuildMonitor.csproj` (`PH0001` for a native head with no library, `PH0002` for an apphost that was not staged). A fix to any of that goes there, not here. To build the Linux library by hand, from the repository root: `docker run --rm -v "$PWD:/src" -v "D:/Code/PlatformHeads/native:/ph:ro" -w /src -e LIBRARY=buildmonitor_ui "quay.io/pypa/manylinux_2_28_$(uname -m)" bash /ph/build-linux.sh`.
- `src/BuildMonitor/` — the one package (`dotnet tool install -g BuildMonitor`). A launcher that starts the head for the current RID from `heads/{rid}/`, plus the `mcp` (stdio MCP server) and `status` verbs. It is `WinExe` so the tool shim is GUI subsystem and can sit in the Run-at-login key. Set `BuildMonitor_Head` to a head executable to run a local build through it.
- Heads are bundled, never packaged on their own.

Expand Down
Loading
Loading