You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I personally don't like QT licensing headaches and the complexities involved in them.
I would like to create a closed-source, potentially commercial node-gui desktop app and use this to pack the app in a manner such that it can hopefully satisfy QT's LGPL licensing limitations.
Can I simply trust that the result of this packer can be distributed to potential customers without thinking about QT "stuff" and licensing?
Or do I still have to send my users a link and have them install QT by themselves?
The text was updated successfully, but these errors were encountered:
I personally don't like QT licensing headaches and the complexities involved in them.
I would like to create a closed-source, potentially commercial node-gui desktop app and use this to pack the app in a manner such that it can hopefully satisfy QT's LGPL licensing limitations.
Can I simply trust that the result of this packer can be distributed to potential customers without thinking about QT "stuff" and licensing?
Or do I still have to send my users a link and have them install QT by themselves?
The text was updated successfully, but these errors were encountered: