@rktech How you write it does not matter. You must observe the LGPL terms of (most of, assuming you stick to that) Qt. Which means that you don't have to publish your sources, and if you do not alter the Qt sources you don't need to publish them either. I am not a lawyer. This is an opinion, not legal advice.

@VRonin said in Qt 5.15 licensing update: I think this is a requirement of GPL not of LGPL It's what I thought for a long time as well. There was another discussion in this forum about this. Finally, we figured out that as of version 3 the LGPL starts by including the GPL and granting a few more rights. It does not rephrase the requirements for distributing the source code. Maybe I was a little bit unclear (if that is the confusion): You only need to provide the source code of Qt. In no case do you need to provide the source code of your own software when using Qt under the LGPL.

@SGaist Hi, Thank you for your reply. I understand your point, so I set this topic solved. I just realized that C:\Qt\Licenses\LISENSE do not include the GPL v3 exception stated above. Hence, the argument above does not hold.

@jordanbaucke Sure, since you have commercial license you can bring the point directly to support.

@VRonin Thanks for the answer. Just to be sure, this is my output when I run otool -L on my .app Does that look ok? @executable_path/../Frameworks/libopencv_core.3.1.dylib (compatibility version 3.1.0, current version 3.1.0) @executable_path/../Frameworks/libopencv_imgcodecs.3.1.dylib (compatibility version 3.1.0, current version 3.1.0) @executable_path/../Frameworks/libopencv_highgui.3.1.dylib (compatibility version 3.1.0, current version 3.1.0) @executable_path/../Frameworks/libopencv_imgproc.3.1.dylib (compatibility version 3.1.0, current version 3.1.0) @executable_path/../Frameworks/libopencv_objdetect.3.1.dylib (compatibility version 3.1.0, current version 3.1.0) @rpath/QtWidgets.framework/Versions/5/QtWidgets (compatibility version 5.6.0, current version 5.6.0) @rpath/QtGui.framework/Versions/5/QtGui (compatibility version 5.6.0, current version 5.6.0) @rpath/QtCore.framework/Versions/5/QtCore (compatibility version 5.6.0, current version 5.6.0) /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL (compatibility version 1.0.0, current version 1.0.0) /System/Library/Frameworks/AGL.framework/Versions/A/AGL (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 120.1.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1226.10.1)

@Spirrwell Yep, that would be a good option indeed :)

Thank you, @tekojo, for your answer.

Qt's sources are covered by the same set of license, GPL, LGPL and Commercial. There's no one widget with a license and another with another license. You have to choose which license you want to use with your project and then abide by its rules. The commercial license being only available once you bought it.

This is the case, thank you very much. Since it is a community, you can advertise here when I develop a game :)

Para resumir: se sua aplicação depende das DLL's/shared librarys, você pode manter seu fonte fechado e vender. Se você "consumir" o Qt estaticamente (.lib), aí você quebrou a LGPL. Resumo: É possível vender minha aplicação usando o LGPL? Para Windows: é possível. Para Linux: é possível. Para MacOS: é possível. Para Android: é possível. Para IOS: não é possível. Isso pq a AppStore não permite shlib. Logo sua aplicação deve ser compilada com o Qt estático. Como o mundo mobile gira em torno de Android/IOS.......

@mcosta Thanks. It would help to have a link to Commercial Features & Benefits instead of the main download page.

@SGaist said: Where did you got these informations ? Nowhere. I just wanted to make certain that this was not true. Your extra information about the Apple Store is very useful -- thanks.

No you don't, again, just check what the LGPL license requires and conform to it, then you'll be good.

@scrolling said: But, what does "dynamic linking" means? It applies only to Qt linking. This means that you can use LGPL version for closed source software only if you link dynamically QT libraries

Thanks Huulivoide and Jeroen3. I carefully read your reply and I study LGPL license and Qt license FAQ again. So I got some conclusions： provide the Qt source code use dynamic link library notified the user: the application is used by LGPL license provide the LGPL licensed contents

@BaldSpoon Hi, please see this article: http://www.qt.io/faq/

@PSI_lbc The only thing I did to get the purchasing demo to work was to upload the APK to Google Play, create in-app purchase identifiers which corresponds to the two identfiers found in the Hangman example and then test the APK as a alpha/beta tester.

Thanks, I will speak to them soon, the indie license seems promising but I wish they had QtTranasactions ;/, oh well, my new problem is Qt fails to compile my APK, something dealing with java but I don't know much about java, and the console isn't helping me much.