Am Tue, 8 Oct 2019 10:16:45 +0300
schrieb Vyacheslav Lanovets :
> 2 persons use *Mac* to make the app work on iOS (static linking!).
what about going lgpl and delivering object files to enable relinking
statically with another qt version?
--
/*
* Your lucky number has been disconnected.
*/
Hi Vyacheslav,
Where are you located? It is probably easiest that our regional sales team or
local reseller is in contact to discuss.
Commercial Qt licensing is developer based, so each person working on the same
project (e.g. same end user application) needs to have a commercial license.
One
> I hope to hear expert opinions on the following.
>
> Let's say the company has 10 developers who develop a Mobile app for
> consumer phones.
>
> 2 persons use *Mac* to make the app work on iOS (static linking!).
> Another 2 persons work from PCs on supporting Android specifics
> (shared linking).
Il 08/10/19 10:24, Yves Maurischat ha scritto:
I dont think that you'll get a definitive answer from this list as
The other side of the coin: this list is NOT for sales or detailed
licensing questions. It's about technical questions related to the usage
of Qt (and, specifically, the parts of
Let me answer that shortly with the gist of severeal other threads on
this list: "It depends. Please contact the sales representatives of The
Qt Company."
I dont think that you'll get a definitive answer from this list as
licensing seems to depend on your project, the mood of the sales rep,
w
Am Wed, 16 May 2018 10:49:06 +
schrieb "Trillmann, Jens" :
> every other file in the platformplugin is LGPL licensed. From my
> understanding I would violate the LGPL license if I would try to
> distribute the app in this form, because a user could not easily swap
> the provided Qt-library
> From my understanding I would violate the LGPL license if I would try to
distribute the app in this form, because a user could not easily swap
the provided Qt-library with his own. The app itself is under the
non-compatible EUPL.
You can ship your app's .o files to allow other people to relink
Hi,
I'm currently trying to link our app on iOS dynamically against Qt. From
the technical standpoint everything seems to be working, but I have a
problem with the licensing.
I would like to conform to the LGPL license, meaning that I want to link
against all Qt parts dynamically, but I have t
there were some discussions on this topic several times now, i feel free to
just repost some mails on this in Qt-interest Digest, Vol 19, Issue 20.
Today's Topics:
2. Re: Licensing (Jan)
3. Re: Licensing (Jeroen De Wachter)
4. Re: Licensing (Kustaa Nyholm)
-
Thanks everyone
> From: sierd...@gmail.com
> Date: Wed, 2 Apr 2014 13:08:38 +0200
> Subject: Re: [Interest] Licensing Questions
> To: alfarobi0...@yahoo.com
> CC: qtsa...@outlook.com; interest@qt-project.org
>
> On 2 April 2014 12:55, alfa wrote:
> > Hi Sarah,
On 2 April 2014 12:55, alfa wrote:
> Hi Sarah,
>
> If I understand it correctly regarding the licensing issue, you may want to
> use LGPL(as opposed to GPL), that does not require you to release the source
> code, however, perhaps somebody who are more experienced than me can explain
> on this, be
Hi Sarah,
If I understand it correctly regarding the licensing issue, you may want to use
LGPL(as opposed to GPL), that does not require you to release the source code,
however, perhaps somebody who are more experienced than me can explain on this,
because I'm also interested in knowing this is
Hi
I team and I are planning to release our desktop application that is
dynamically linked to the Qt library.
As I understand it this means that, if requested by a customer, I must make the
source code for Qt available.
In addition I must make the object code or source code for the application
13 matches
Mail list logo
