Files
pipelines/docs/notes/desktop-client-builds.md
T

1.7 KiB

Desktop client build options

Added ./install --linux (Docker Linux x64) and ./install --macos (native pinned Flutter + Xcode, host architecture). Both produce full client archives without installing or restarting a server. macOS requires 12+; its existing 10.15 project target failed against Xcode 27 and was corrected. The supported Flutter FLUTTER_XCODE_ARCHS setting explicitly selects the native host architecture; the cache includes that host identity. This avoids claiming a universal binary, and feeds use actual lipo -archs output.

--publish offers versioned archives via the existing authenticated update file server. Feeds carry platform, actual architectures, epoch-minute build code, SHA-256, release notes, and relative archive filename. The same build code is compiled into the client. Archive publication precedes atomic feed replacement; old filenames remain available for in-flight downloads. Older builds cannot overwrite newer feeds. Builds work without a server manifest unless publication is requested.

Verification: 15 Python builder/cache/packaging/publication tests passed; Python compilation, shell syntax, and diff checks passed. Real Docker x64 Linux release and native macOS arm64 release both built with Flutter 3.44.6. The macOS archive retained nine framework symlinks, and codesign --verify --deep --strict passed. Linux archive retained the complete lib/data bundle and executable mode 0755; ldd inside the Debian builder found no missing libraries. Logs: /tmp/pipelines-{linux,macos}-build.log and /tmp/pipelines-linux-linkage.log. No desktop UI/device interaction was run; these build checks do not establish runtime UI parity or public deployment. Final app-source integration requires rebuilding changed-source artifacts.