freecad: remove qt5 and explicit wayland builds

[LordGrimmauld]

Qt5 support is was officially reduced by qt [1].

FreeCAD supports both Qt5 and Qt6. While their github
build still uses Qt5, the official flatpak uses Qt6 [2].

Additionally, keeping Qt5 support requires pinning
python to 3.12 or older, as shiboken2 would break.
Currently, this breakage is imminent: #412204 unpinned
python, with the next staging-next merge updating py to 3.13.

Qt will figure out which platform plugin to use. Many of our packages already explicitly unset QT_QPA_PLATFORM, it makes little sense to force it here.

[1] https://www.qt.io/blog/extended-security-maintenance-for-qt-5.15-begins-may-2025
[2] https://github.com/flathub/org.freecad.FreeCAD/blob/ad843adc0a29a2c78bdd60624376aab61445ed63/org.freecad.FreeCAD.yaml#L62

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• Nixpkgs 25.11 Release Notes (or backporting 24.11 and 25.05 Nixpkgs Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
• NixOS 25.11 Release Notes (or backporting 24.11 and 25.05 NixOS Release notes)
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md, pkgs/README.md, maintainers/README.md and other contributing documentation in corresponding paths.

---

Add a 👍 reaction to pull requests you find important.

[LordGrimmauld]

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 416741
Commit: 34a33ec1bf0e19457ac3f14c9e3932f840ab0093

---

x86_64-linux

✅ 1 package built:

• freecad

[LordGrimmauld]

Hmm i might also be able to clean up the wrapping, this currently triple-wraps...

[LordGrimmauld]

Alright, no more duplicate wrapping. Just running the passthru tests now to make sure i didn't accidentially break the python path, but i don't think i did.

[LordGrimmauld]

Indeed passthru tests still work (which do check the python path)

[LordGrimmauld]

(oops, misclick with the close...)

[pbsds]

lib.getInclude?

[LordGrimmauld]

Doesn't actually append /include, it only would get the $include output. And pyside6 only has the one default output. So would not do anything.

[pbsbot]

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 416741
Commit: d72cbf576f98d6756d08565166f9803ba28f0d59

---

x86_64-linux

✅ 1 package built:

• freecad

[pbsds]

The python wrapper usually also adds the /bin folders to PATH, are any of the pytohn dep entrypoints needed by freecad?

[LordGrimmauld]

The python wrapper usually also adds the /bin folders to PATH, are any of the pytohn dep entrypoints needed by freecad?

The python wrapper wasn't even used before i think - even before it was just --prefix PYTHONPATH : "$PYTHONPATH" in the Qt wrapper, no explicit python wrapper statements. The environment should be basically the same. And i am still setting python path, just using nix instead of bash to do it (and avoiding double wrapping in the process)

[pbsds]

Ah, my eyes skipped past the old qtWrapperArgs+=(...) in the diff, LGTM