Build Linux and macOS clients with platform update feeds
This commit is contained in:
@@ -154,6 +154,40 @@ signed with the key in `~/.config/pipelines/android/` (seeded from
|
||||
`~/.android/debug.keystore` if present), so each build installs over the last.
|
||||
Options: `--server-url ws(s)://host:port/connect`, `--notes TEXT`, `--prefix`.
|
||||
|
||||
### Desktop clients
|
||||
|
||||
```sh
|
||||
./install --linux --output ./dist
|
||||
./install --macos --flutter /path/to/flutter --output ./dist
|
||||
# Offer this desktop build through an installed server's update feed:
|
||||
./install --linux --publish --notes "Release notes"
|
||||
./install --macos --flutter /path/to/flutter --publish
|
||||
```
|
||||
|
||||
Linux builds use Docker on Linux or macOS and target **Linux x64**. Extract the
|
||||
entire `pipelines-linux-x64.tar.gz` archive and run `pipelines-linux-x64/pipelines-app`;
|
||||
keep its `lib/` and `data/` siblings together. The executable has a distinct name
|
||||
from the `pipelines` server CLI. The target Linux desktop needs GTK 3 and its
|
||||
runtime libraries (Debian/Ubuntu: `libgtk-3-0`, `libstdc++6`, `liblzma5`). This is a
|
||||
portable bundle, not a package-manager installation or a server installation.
|
||||
|
||||
macOS 12 or newer is required. macOS builds run natively with Xcode and the pinned Flutter version from
|
||||
`app/.flutter-version`; they do not require Docker. The build targets the build
|
||||
machine's architecture and records the actual executable architecture in the
|
||||
feed. Unzip `Pipelines-macos.zip` and open `Pipelines.app`; move it to Applications
|
||||
if desired. Local builds are not Developer ID notarized distribution packages.
|
||||
Framework symlinks and executable permissions are preserved in the archive.
|
||||
|
||||
Both commands build in isolated source copies/containers, retain cached releases,
|
||||
and do not install, launch or restart the server. `--server-url` optionally sets
|
||||
the first server address; otherwise choose it in the app. `--output` copies the
|
||||
archive to a chosen directory. `--publish` additionally requires an existing
|
||||
installation (`--prefix` supported), copies a versioned archive into its update
|
||||
directory, then atomically updates `/updates/linux-x64/version.json` or
|
||||
`/updates/macos/version.json`. Feeds include platform, actual architectures,
|
||||
version, SHA-256, and release notes. Android's existing feed remains separate.
|
||||
Previously published archives remain available for downloads already in progress.
|
||||
|
||||
`./install --docker` is the optional Compose installation with its own
|
||||
container harness credentials; see [Docker](docker.md). Do not run it
|
||||
alongside a native install on the same ports. Its harnesses are set up with
|
||||
|
||||
@@ -0,0 +1,28 @@
|
||||
# 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.
|
||||
Reference in New Issue
Block a user