Possible upgrade qtcontrib with qt 5.7 who now use mingw53?

[Massimo Belgrano]

Possible update qtcontrib with Last qt have updated version of Mingw!

http://download.qt.io/official_releases/qt/5.7/5.7.0/qt-opensource-windows-x86-mingw530-5.7.0.exe


SET MGWHOME=C:\dvl\Qt\Qt5.7.0\Tools\mingw530_32

SET QTHOME=C:\dvl\Qt\Qt5.7.0\5.7\mingw53_32

I have Recompiled qt with error

C:/dvl/Qt/Qt5.7.0/5.7/mingw53_32/include/QtCore/qbasicatomic.h:61:4: error: #error "Qt requires C++11 support"

--

Massimo Belgrano
Delta Informatica S.r.l. (Cliccami per scoprire ) 

[Pritpal Bedi]

Hi Massimo

Possible update qtcontrib with Last qt have updated version of Mingw!

For this to happen, we need to fix few headers in the core.

Plus, may be you are aware, but for generic overview, Qt 5.7 is only LGPL v3.0 complaint release,

and hence is not suitable for closed source development unless you buy Qt license.

I have already compiled HbQt on Qt 5.7.0 and have found only few issues which I already have fixed.

But I am not sure will it be a wise decision to go this way or not.

Pritpal Bedi

a student of software analysis & concepts

 

[Luigi Ferraris]

Il 22/06/2016 1.44, Pritpal Bedi ha scritto:

Plus, may be you are aware, but for generic overview, Qt 5.7 is only LGPL v3.0 complaint release,

and hence is not suitable for closed source development unless you buy Qt license.

I have already compiled HbQt on Qt 5.7.0 and have found only few issues which I already have fixed.

But I am not sure will it be a wise decision to go this way or not.

Hi Pritpal, in my little opinion: I think it would be good evolve HBQT project by following the QT changes otherwise it means to stop (arrest) the HBQT project

Yes, Qt licensing was changed but I think this can't be / it should not be a reason to stop, without follow evolutions.
I read on internet  some documents about license (I'm not an expert); I think next link can show more clear (I hope) the changes: http://www.embeddeduse.com/2016/04/10/using-qt-5-6-and-later-under-lgpl/
On the other hand, starting from version 5 it was clear the intention of bringing (tend) Qt "to" commercial licensing (see the creation of a company and Microsoft's infiltration).
Anyway, if I understand correctly, these are the main rules to use Qt open source
«How to Comply with LGPLv3
When you use Qt under LGPLv3, you have three main obligations.
    * Your application must link the Qt libraries as shared libraries. Static linking is forbidden.
    * You must make the Qt sources – including your modifications to the Qt sources – publicly available. For example, you can make available the Qt sources on your website or on GitHub for download. You can keep the source code of your application closed.
    * You must enable users to build the Qt sources for the target device (e.g., an infotainment system in a car or a washing machine), deploy the Qt libraries on the target device and run the original application using the modified Qt libaries on the target device.»

Probably, it's time to have different HbQt branches to keep developers job more simple and clean; perhaps, having a (stopped) HbQt version (to cover Qt from 0.0 to 5.x) and a new HbQt version (to cover Qt from 5.x to ....). Obviously, it's a big job.

Regards
Luigi

[Francesco Perillo]

Hi,

from what I read and understood, GPL v3 can be used in closed source development but, as in previous Qt version, you can't statically link to it, but you must allow the users to exchange parts of the code.

GPL v3 also add an anti-tivoization part (search for tivoization on google). In short, TiVo was v2 compliant publishing all the v2 source code and you could compile the software but there were no signing keys available so the software could not be replaced on the linux-driven TiVo set-top-box.

--
You received this message because you are subscribed to the Google Groups "QtContribs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qtcontribs+...@googlegroups.com.
To post to this group, send email to qtcon...@googlegroups.com.
Visit this group at https://groups.google.com/group/qtcontribs.
For more options, visit https://groups.google.com/d/optout.

[Dušan D. Majkić]

There is Qt official page with simple comparsion table

http://www.qt.io/licensing-comparison/

"Possible to keep your application private with dynamic linking" is
checked for LGPLv3

so it shoud be fine to use Qt 5.7 and HBQT in "closed source" software
as long as it is linked with dynamic libs eg. qt dll (or .so or
.dylib) and qt licence is present in about box with link to qt source
code.

[Massimo Belgrano]

Hi Pritpal can you give some evolution for qtcontrib?  (qt.57)

What about your effort on a cloud based SaaS infrastructure on AWS with pure Harbour technologies, 

Are you using hbide and qtcontrib library?

--

You received this message because you are subscribed to the Google Groups "QtContribs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qtcontribs+...@googlegroups.com.
To post to this group, send email to qtcon...@googlegroups.com.
Visit this group at https://groups.google.com/group/qtcontribs.
For more options, visit https://groups.google.com/d/optout.

[Pritpal Bedi]

Hi Massimo

Hi Pritpal can you give some evolution for qtcontrib?  (qt.57)

I have compiled QtContribs successfully with Qt 5.7.

However it needs a change in one of the core harbour header and few more 

in QtContribs, especially in QZXing librray. All is almost done. The only 

constraint is "time".

 

What about your effort on a cloud based SaaS infrastructure on AWS with pure Harbour technologies, 

The entire setup is ready to be deployed in production.

Harbour technologies used in the project ( off course the with entire core ) are:

1.  GTNET ( Prezemk's yet to be offered commercial library )

2.  HBNETIO 

3.  GTTRM ( Server Side )

4.  GtWVG ( Client Side - Windows )

5.  QtContribs ( Client Side - Mobile - Android Devices )

6.  Web-Browser ( Server Side ) => ShellInABox ( Client Side )

7.  HBJRPC ( JSON compliant communication library from Prezemek ( scheduled to be offered commercially )

I will release the detailed Cloud Setup map sometime in future.

It is my commercial application Vouch which is about to be offered under SaaS namespace.

Note that from Harboureans point-of-view, testing this framework is only intended to 

demonstrate how Harbour is such a powerful language and how they can take use of 

this powerful, future-proof technology. It also demonstrate how accomplished is Przemek, my Guru.

If anybody is interested in testing it do send me an email at bedipritpal @ hotmail.com .

I will send the link to download and documentation page ( which currently does not have 

documentation ready for mobile access ).

 

Are you using hbide and qtcontrib library?

For mobile client interface.

Since I am heavily occupied with cloud project, I am finding it difficult to 

switch my attention to QtContribs. But I promise to pull some days off to this cause. 

[Luigi Ferraris]

Hi Pritpal,
I read all your answers... do you have time to spend on QtContrib and publish updates?
Many thanks in advance for your time and job.

Luigi Ferraris

[Dušan D. Majkić]

> 1. GTNET ( Prezemk's yet to be offered commercial library )

> ...

> 7. HBJRPC ( JSON compliant communication library from Prezemek
> ( scheduled to be offered commercially )

Sound interesting. Where can I get more info on these two?

[Pritpal Bedi]

Hi

Przemek, off course!

[Pritpal Bedi]

Hi Luigi

I read all your answers... do you have time to spend on QtContrib and publish updates?

Not at least for a couple of months.

Nevertheless I will try as soon as possible.