[maemo-developers] How to resolve network connectivity without using Qt Mobility in Qt?
From: Marius Vollmer marius.vollmer at nokia.comDate: Thu Jul 22 11:33:52 EEST 2010
- Previous message: How to resolve network connectivity without using Qt Mobility in Qt?
- Next message: How to resolve network connectivity without using Qt Mobility in Qt?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
ext Sascha Mäkelä <sascha.makela at gmail.com> writes: > So according your opinion, should I wait for this issue to be resolved at > Nokia's end or should I try to make changes to my app? Don't wait for us, try to work around the problem on your side. > The one suggestion I've been given several times is to statically > include Qt Mobility, but I'm not so sure if that is a great idea and > even if it was, I don't know how to do that. I would do what you have started this thread for: do without QtMobility. I'll reply to your original mail with some hints. When statically linking QtMobility, there might also be license issues. QtMobility is LGPLv2.1 (unless you have a commercial Qt license which I assume you don't), and that means that you can't really copy code out of it into your sources (which I assume are non-free), and even if you distribute QtMobility in your package, you need to satisfy the LGPL: static linking is not allowed (unless the user can do it, too), you need to provide source for QtMobility upon request, etc. Maybe Nokia gives an exception that allows static linking of QtMobility, and Nokia isn't likely to sue you over this anyway, but still, Nokia shouldn't really make the suggestion to statically link QtMobility without clearly stating that they give permission for that eventhough the license of QtMobility forbids it.
- Previous message: How to resolve network connectivity without using Qt Mobility in Qt?
- Next message: How to resolve network connectivity without using Qt Mobility in Qt?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]