enricobuehler
491a344f23
release / apple (push) Successful in 10m26s
android-screenshots / screenshots (push) Successful in 3m5s
decky / build-publish (push) Successful in 29s
docker / build-push (--build-arg FEDORA_VERSION=44, ci, ci/fedora-rpm.Dockerfile, punktfunk-fedora44-rpm) (push) Successful in 12s
docker / build-push (., web/Dockerfile, punktfunk-web) (push) Successful in 12s
docker / build-push (ci, ci/fedora-rpm.Dockerfile, punktfunk-fedora-rpm) (push) Successful in 11s
docker / build-push (ci, ci/rust-ci-noble.Dockerfile, punktfunk-rust-ci-noble) (push) Successful in 11s
docker / build-push (ci, ci/rust-ci.Dockerfile, punktfunk-rust-ci) (push) Successful in 12s
docker / build-push (docs-site, docs-site/Dockerfile, punktfunk-docs) (push) Successful in 12s
deb / build-publish (push) Successful in 12m14s
deb / build-publish-host (push) Successful in 12m25s
android / android (push) Successful in 13m56s
arch / build-publish (push) Successful in 13m30s
docker / deploy-docs (push) Successful in 17s
web-screenshots / screenshots (push) Successful in 4m11s
linux-client-screenshots / screenshots (push) Successful in 7m6s
flatpak / build-publish (push) Successful in 6m51s
rpm / build-publish (44, fedora-44, punktfunk-fedora44-rpm) (push) Successful in 17m46s
rpm / build-publish (43, bazzite, punktfunk-fedora-rpm) (push) Successful in 18m3s
windows-msix / package (arm64, C:\Users\Public\ffmpeg-arm64, --no-default-features, aarch64-pc-windows-msvc, C:\t-a64) (push) Successful in 6m9s
windows-msix / package (x64, C:\Users\Public\ffmpeg, , x86_64-pc-windows-msvc, C:\t) (push) Successful in 6m53s
windows-host / package (push) Failing after 14m35s
Both MSIX matrix jobs failed at the v0.15.0 tag, for two unrelated reasons, both introduced by this release. 0.13.0 and 0.14.0 shipped both packages; 0.15.0 shipped neither. ARM64 failed to BUILD. The PyroWave Windows un-gating (1ef0229b) moved `pyrowave-sys` in pf-client-core out of `cfg(target_os = "linux")` into a general optional dependency that pf-client-core's own `default = ["pyrowave"]` turns on. The ARM64 leg builds `--no-default-features` precisely to skip it, but that only disables defaults for the two packages named with `-p` — every internal edge kept inheriting them: clients/windows -> pf-client-core, clients/session -> pf-client-core, clients/session -> pf-presenter, and pf-presenter's own `default = ["pyrowave"]` -> pf-client-core. So the vendored Granite C++ compiled on ARM64 and stopped where it always does: muglm.cpp reaching for _MM_TRANSPOSE4_PS/_mm_storeu_ps, then `simd.hpp:103 #error "Implement me."`. Those three internal edges now pass `default-features = false`; the feature is enabled only through an explicit chain (clients/session's `pyrowave` -> pf-client-core/pyrowave + pf-presenter/pyrowave, and pf-presenter's `pyrowave` -> pf-client-core/pyrowave), so `--no-default-features` finally means what it says. Verified by feature resolution rather than assertion — `cargo tree -i pyrowave-sys`: aarch64-pc-windows-msvc, --no-default-features -> not in the graph (was: present) x86_64-pc-windows-msvc, default features -> present x86_64-unknown-linux-gnu, default features -> present PyroWave is NOT dropped from the Windows client. Decode has always run in the spawned punktfunk-session binary, whose own default keeps the feature on, and unification turns it back on for the shared pf-client-core wherever that binary is in the build (x64, Linux). The shell only ever offered "pyrowave" as a codec preference string — it holds no decoder and never called one, so linking the C++ into it was dead weight even on x64. x64 built fine and failed at PACKAGING: `makepri new` rejected the manifest with PRI191 "Appx manifest not found or is invalid" / malformed comment syntax. The console tile added in2508b720documented its flag inside an XML comment, and XML forbids `--` anywhere in a comment body, so the literal flag spelling made the whole manifest unparseable. Reworded, with a note to keep the next person from reintroducing it. Confirmed by parsing both revisions after template substitution: the tagged manifest fails at line 63 col 9, this one parses. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
88 lines
3.9 KiB
XML
88 lines
3.9 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<!--
|
|
MSIX package manifest for the punktfunk Windows client (WinUI 3 via windows-reactor).
|
|
|
|
This is a TEMPLATE: packaging/pack-msix.ps1 substitutes {VERSION} (4-part numeric, e.g.
|
|
0.2.137.0) and {PUBLISHER} (must EXACTLY equal the signing cert's subject DN — default
|
|
`CN=unom` for the self-signed CI cert; a real code-signing cert just passes its own subject).
|
|
|
|
Why this packages cleanly even though the app was built "unpackaged": windows-reactor calls
|
|
MddBootstrapInitialize2 with OnPackageIdentity_NOOP (crates/libs/reactor/src/app.rs), so under
|
|
MSIX package identity the App SDK bootstrapper is a no-op and the runtime is resolved from the
|
|
<PackageDependency> below instead. The framework family + min version mirror what the runner has
|
|
installed and what reactor pins (WINDOWSAPPSDK_RELEASE_MAJORMINOR = 0x20000 = 2.0 ->
|
|
Microsoft.WindowsAppRuntime.2).
|
|
|
|
Full-trust Win32 app (EntryPoint Windows.FullTrustApplication + runFullTrust) — it owns raw D3D11,
|
|
Win32 low-level input hooks, WASAPI and SDL3, none of which fit the UWP app container.
|
|
-->
|
|
<Package
|
|
xmlns="http://schemas.microsoft.com/appx/manifest/foundation/windows10"
|
|
xmlns:uap="http://schemas.microsoft.com/appx/manifest/uap/windows10"
|
|
xmlns:rescap="http://schemas.microsoft.com/appx/manifest/foundation/windows10/restrictedcapabilities"
|
|
IgnorableNamespaces="uap rescap">
|
|
|
|
<Identity
|
|
Name="unom.Punktfunk"
|
|
Publisher="{PUBLISHER}"
|
|
Version="{VERSION}"
|
|
ProcessorArchitecture="{ARCH}" />
|
|
|
|
<Properties>
|
|
<DisplayName>Punktfunk</DisplayName>
|
|
<PublisherDisplayName>unom</PublisherDisplayName>
|
|
<Logo>Assets\StoreLogo.png</Logo>
|
|
</Properties>
|
|
|
|
<Dependencies>
|
|
<TargetDeviceFamily Name="Windows.Desktop" MinVersion="10.0.17763.0" MaxVersionTested="10.0.26100.0" />
|
|
<PackageDependency
|
|
Name="Microsoft.WindowsAppRuntime.2"
|
|
MinVersion="2.2.0.0"
|
|
Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" />
|
|
</Dependencies>
|
|
|
|
<Resources>
|
|
<Resource Language="en-us" />
|
|
</Resources>
|
|
|
|
<Applications>
|
|
<Application Id="Punktfunk" Executable="punktfunk-client.exe" EntryPoint="Windows.FullTrustApplication">
|
|
<uap:VisualElements
|
|
DisplayName="Punktfunk"
|
|
Description="Low-latency desktop and game streaming client"
|
|
BackgroundColor="transparent"
|
|
Square150x150Logo="Assets\Square150x150Logo.png"
|
|
Square44x44Logo="Assets\Square44x44Logo.png">
|
|
<uap:DefaultTile Square71x71Logo="Assets\Square71x71Logo.png" />
|
|
</uap:VisualElements>
|
|
</Application>
|
|
<!--
|
|
Second entry point: the couch/console UI, for an HTPC or a TV-attached box where the
|
|
desktop shell is the wrong first screen. Its own executable (punktfunk-console.exe)
|
|
because an MSIX Application entry cannot pass arguments to a full-trust exe; it hands
|
|
straight off to the session binary's controller-driven browse mode (host list,
|
|
pairing, settings, library) fullscreen.
|
|
|
|
NOTE: never write a double hyphen in this file. XML forbids it inside a comment, and
|
|
makepri rejects the whole manifest ("Appx manifest not found or is invalid") — which
|
|
is exactly how the console flag spelled out here broke the v0.15.0 MSIX build.
|
|
-->
|
|
<Application Id="PunktfunkConsole" Executable="punktfunk-console.exe"
|
|
EntryPoint="Windows.FullTrustApplication">
|
|
<uap:VisualElements
|
|
DisplayName="Punktfunk Console"
|
|
Description="Controller-driven couch interface for TVs and HTPCs"
|
|
BackgroundColor="transparent"
|
|
Square150x150Logo="Assets\Square150x150Logo.png"
|
|
Square44x44Logo="Assets\Square44x44Logo.png">
|
|
<uap:DefaultTile Square71x71Logo="Assets\Square71x71Logo.png" />
|
|
</uap:VisualElements>
|
|
</Application>
|
|
</Applications>
|
|
|
|
<Capabilities>
|
|
<rescap:Capability Name="runFullTrust" />
|
|
</Capabilities>
|
|
</Package>
|