[Interest] Qt Creator licensing for companies with Qt Commercial developers

[Krzysztof Kawa]

> Are you talking about an API that *your game* will use (e.g. for IAPs)?
> Or just the process of submitting your content to be distributed?

Could be both. Game stores provide stuff like cloud saves,
achievements, chat etc. This often gets compiled into the game.
Or it could be just some manifest or script that describes your
package. The store's packaging tool could be using Qt. Different
stores different APIs. While API itself might not be Qt based some
parts of that store "project" could be and small tidbits of it get
included in your app.

> *You* are fine, so long as publishing doesn't prevent you from
> fulfilling your [L]GPL obligations.
> The store, OTOH... I have no idea. (Lucky for you that's not *your*
> problem.)

Yeah, what if it's the other way around? Store uses open-source and I
buy commercial? Publishers often require or downright add DRM
protection so this forces you to go commercial because there's no
legal way to re-link the app. If the store also happens to use
open-source Qt and you need to use their API you're pretty much out of
luck. Sounds like a minefield.

śr., 1 kwi 2020 o 22:30 Matthew Woehlke <mwoehlke.floss at gmail.com> napisał(a):
>
> On 31/03/2020 16.12, Krzysztof Kawa wrote:
> > This got me thinking about quite a simple case that doesn't seem so
> > simple now: Lets say I make a game using open-source licensed Qt, or
> > even just open-source licensed Qt Creator. After few years of
> > development I decide to publish the game. It just so happens that my
> > publisher has a storefront app using commercial Qt or even just
> > written in Qt Creator under commercial license. To put my app in their
> > store there's usually some API, config file or whatever that
> > technically makes it mixing the two, even if not through Qt based
> > interface.
>
> Are you talking about an API that *your game* will use (e.g. for IAPs)?
> Or just the process of submitting your content to be distributed?
>
> > Does that mean I can't publish my app in that store?
>
> *You* are fine, so long as publishing doesn't prevent you from
> fulfilling your [L]GPL obligations.
>
> The store, OTOH... I have no idea. (Lucky for you that's not *your*
> problem.)
>
> --
> Matthew