libsForQt5.qca-qt5: unbreak on darwin

[wegank]

Description of changes

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
• 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/)
• 23.05 Release Notes (or backporting 22.11 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (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
  • (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes
• Fits CONTRIBUTING.md.

[imincik]

@wegank , @thiagokokada what is the actual change which makes qca-qt5 working on darwin again ?

[thiagokokada]

@wegank , @thiagokokada what is the actual change which makes qca-qt5 working on darwin again ?

I am assuming that we are building Qt 5.15 in darwin now?

[imincik]

Great thanks !

[imincik]

@lsix @sikmir @erictapen @willcohen - chance to get QGIS on darwin ?

[willcohen]

Yes! Two days ago I dusted off #157862 and locally rebased to master (I'm not pushing to the branch so I don't keep spamming darwin-maintainers just yet). Right now I'm at the highly annoying stage of getting all the dylibs to link correctly by manually running install_name_tool on every combination of every dylib being referred to from all the random frameworks, but every time I fix one link error I've gotta re-run the whole build, so it's slow going. I hope in the next couple of days that I finally get through it all and can get it to load.

As soon as QGIS actually builds and starts up I'll push the branch and we can hopefully merge that without much fuss. My preference would be to move all the fine-tuning to later PRs -- there's a strong chance that there'll still be little breakages with the various components, but getting something going is better than waiting for every little bit to be ironed out.

[imincik]

Great thanks @willcohen .

[willcohen]

@imincik any suggestions of how to proceed further based on #157862 (comment) would be much appreciated!