> These are just packaging issues, typically (but not only) on Linux. Dedicated developers know what to do to avoid all of that. Isn't that the point? It's ea

> These are just packaging issues, typically (but not only) on Linux. Dedicated developers know what to do to avoid all of that. Isn't that the point? It's easy for a packager to get into a situation that gives the end user a shitty experience. You shouldn't need to be a "dedicated developer" just to be a user, and making the packaging situation straightforward for the distributor is firmly in framework provider's ballpark. This isn't something Qt should be allowed to shrug off, it's exactly the job they should be doing. >> Then once you finally get it to work, be prepared to spend time on Stack Overflow researching arcane QT_ environment variables to fix things like display scaling and added additional library paths at runtime. Just to add my n=1 anecdata here, FreeCAD (a QT app) consistently gets scaling wrong, on all the platforms I regularly use it on (Windows, MacOS, Linux). It's just... not good, to the extent that I actively avoid plugging external monitors in rather than screw with it once I've got a tolerable setup.