If it’s not in the distro, it’s not in the tree, then it’s built by another tool like genie or whatever. vcpkg was because windows had no such capability.
It’s decent but it’s not the best.
If it’s not in the distro, it’s not in the tree, then it’s built by another tool like genie or whatever. vcpkg was because windows had no such capability.
It’s decent but it’s not the best.
This is why nobody can rely on distro managers. Not to mention FlatPaks and so on.
Lastly, KDE maintains their own Qt fork for packaging purposes.
And have you ever had to work on different version of libraries for development and LTS branches of software? Because it doesn't sound like you had? Lastly, KDE maintains their own Qt fork for packaging purposes.
>”Because it doesn’t sound like you had?” was unnecessary and you have no idea who I am.
I was merely stating that most distros have those headers, most distros care about being up to date with stable releases. Yes KDE releases software on Mac and windows, that has nothing to do with vcpkg. If anything, it’s more work.
I’m sick of the “mansplaining” in these comments like I was born yesterday. I wasn’t, and I know how to write C.