News for hackers. Stuff that matters.
Re:Qt Quick Controls 2.1 and Beyond by plq on Thursday October 06, 2016 @01:59PM (#12654574)
I'd love to see some evidence to back your claims regarding mobile platforms.

To satisfy LGPL, your users need to be able to swap Qt versions. For desktop platforms, that's trivial to do: Use dynamic linking and your users will be able to fiddle with the shared library files to their heart's content.

However, for IOS or Android, the moment the user changes the contents of your package, your signature is void and the vanilla platforms don't let the user install modified versions of your binary. For IOS, there are additional hurdles like the requirement to statically link or the licence incompatiblility when interfacing with IOS which to me boils down to this: If you are distributing a non-free app built with Qt Open Source via Google's Play Store or Apple's App Store, you are in violation of the terms of Qt's license.

The fact that the Qt company tries to play nice with the industry doesn't make it any less so.

I'd love to be proven wrong, but I'm just tired of watching this subject being discussed with nothing more than handwavy arguments, winks and smileys.

Re:Qt Quick Controls 2.1 and Beyond by aeruder on Thursday October 06, 2016 @03:21PM (#12655280)
100% correct. Far too many misinterpretations of the LGPL out there seem to ignore the requirement that the LGPL'd portion must be able to be replaced/updated.

I've seen way too many LGPL-licensed embedded-C libraries and VHDL libraries where it just does not make any sense. If your target platform doesn't have a dynamic linker, then LGPL is the same as GPL. There are some hacks where people distribute unlinked .o/.obj files. This is acceptable as well, but I don't see it too often.

Re:Qt Quick Controls 2.1 and Beyond by zerr on Thursday October 06, 2016 @04:52PM (#12656008)
I've answered below:

https://news.ycombinator.com/item?id=12653246

So for mobile platforms you can publish compiled .obj files.