Skip to content

Build & deployment friction on Nix/Flatpak (plus notes on QML component lifetime) #7

Closed

Description

@Theneillsaaco

Description

Building and packaging outside the standard happy path (specifically on Nix and Flatpak) involves several friction points:

  1. Target failure: QtBridgeDeploy_SourceCode_Linux_MacOS fails on Nix unless overridden in Directory.Build.targets (IgnoreExitCode + warning).
  2. AppHost binary: QtBridgePrepareAppHost picks the wrong host binary by default (required a target override setting AppHostSourcePath).
  3. Missing publish artifacts: dotnet publish omits binaries/files like player_app, Application, qt_bridge_metadata.json, and qtdeploy.txt, requiring manual copying in Nix postInstall and Flatpak manifests.
  4. Platform themes: Platform theme plugins are not deployed, breaking Qt's styleHints.colorScheme (solved by reading the XDG portal via busctl/gdbus).
  5. Paths & Configuration: QtDir and CMAKE_PREFIX_PATH must be set manually. Flatpak required building a fake Qt prefix with symlinks.
  6. Project boilerplate: The .csproj requires an extensive block of RID/arch properties and conditions.

(Note / Potential Lifecycle Observation)
QML Component Creation/Destruction Crash:
While building, I encountered a potential crash when rapidly creating and destroying QML components using Loader/Component (e.g., toggling Queue and Lyrics panels quickly). I worked around this by instantiating the panels once and toggling their parent, opacity, and visibility instead. This might be an issue with object lifetimes between C# view models and destroyed QML objects, though it could also be specific to my implementation. Mentioning it here just in case!

Steps to reproduce

.

Expected behavior

Suggestion: Provide a documented Nix/Flatpak packaging recipe and ensure dotnet publish bundles all required metadata/binaries out of the box.

Actual behavior

.

Qt Bridge for C# version

TP (C#)

Qt version

No response

.NET SDK version

No response

Operating system and architecture

No response

Tooling

No response

Logs

Activity

  1. added
    jiraTriaged; adding this label moves the issue to the Qt bug tracker and closes it
    on Nov 12, 2026
  2. github-actions commented on Nov 12, 2026

    @github-actions

    Thank you for the report. It is now tracked as QTBRIDGES-464 in the Qt bug tracker. Please follow up there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingjiraTriaged; adding this label moves the issue to the Qt bug tracker and closes it

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions