[Interest] Glib vulnerability on QT 5.6.3 dependency

[Ramakanth Kesireddy]

Hi,

Am using Qt 5.6.3 widgets on embedded Linux through yocto recipes which
depends on libglib-2.0. The modules being used by our single threaded
application are core,gui,widgets and printsupport.

Our usecases incase of QT involve c++ widgets with stylesheet with
QStackedlayout and signals/slots and QTimers.

A vulnerability is found with the glib version 2.52.3 as
https://nvd.nist.gov/vuln/detail/CVE-2019-12450.

Is it recommended to upgrade the glib version to 2.8.3 or look for any
patch with the existing version or ignore the CVE?

Please let me know your feedback in this regard.

Thanks and Regards,
Ramakanth
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Qt 5.15 pull out of open source?!

[David M. Cotter]

I, too, would like some clarification.
thanks

-dave

> On Jan 6, 2021, at 7:03 PM, Jérôme Godbout  wrote:
> 
> Hi, 
> is this any true?
> https://www.phoronix.com/scan.php?page=news_item=Qt-5.15-LTS-Commercial-Phase
>  
> 
> 
> Does Qt really thing 6.0 can fill the bills of open source for all apps? so 
> many modules are missing from 6.0?! all Bluetooth app using open source will 
> do what exactly?!?
> 
> I surely hope this is a bad comprehension of the actual reality.
> 
> Damn, if so, I think many project should move away from Qt.
> 
> Such a nice framework, such a bad licensing and commercial behaviour...
> 
> I feel sad right now.

___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Qt6 - Making Qt installer package for Windows, Linux and OS X

[Be]

Much of this is CMake's fault rather than Qt's. Getting CMake to make a
macOS package was an incredibly frustrating experience that took me 1.5
weeks. I reported the issues upstream to CMake:

https://gitlab.kitware.com/cmake/cmake/-/issues/21568

On 1/6/21 8:16 AM, Till Oliver Knoll wrote:

Am 09.12.20 um 11:14 schrieb Alexandru Croitor:

Going forward, i'd expect improvements on "consumption of Qt with CMake" part 
as well.

I can definitively confirm that creating your own Qt applications using
CMake yourself is not quite the same "out of the box"-experience as with
qmake (at least as far as "template projects setup with Qt Creator" are
concerned). Also refer to my other thread here ("Rebuilding cmake
project (in Qt Creator) fails - build directories write-protected?")

CMake support is just not quite there yet ;)

Cheers, Oliver

___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

[Interest] Qt 5.15 pull out of open source?!

[Jérôme Godbout]

Hi,
is this any true?
https://www.phoronix.com/scan.php?page=news_item=Qt-5.15-LTS-Commercial-Phase

Does Qt really thing 6.0 can fill the bills of open source for all apps? so 
many modules are missing from 6.0?! all Bluetooth app using open source will do 
what exactly?!?

I surely hope this is a bad comprehension of the actual reality.

Damn, if so, I think many project should move away from Qt.

Such a nice framework, such a bad licensing and commercial behaviour...

I feel sad right now.
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Rebuilding cmake project (in Qt Creator) fails - build directories write-protected?

[Till Oliver Knoll]

Am 06.01.21 um 10:45 schrieb Kai Köhne:
>> From: Interest  On Behalf Of Till Oliver 
>> Knoll
>> Subject: Re: [Interest] Rebuilding cmake project (in Qt Creator) fails - 
>> build directories write-protected?
>>
>> Am 31.12.20 um 16:02 schrieb Till Oliver Knoll:
>> Am 31.12.20 um 15:29 schrieb James DeLisle:
>> There are some on-going peculiarities with CMake and translation files, as 
>> evidenced here:
>> https://bugreports.qt.io/browse/QTBUG-76410
>> Thanks for your reply! In fact, the problem is not only related to 
>> translation files (but it occurs there first during a build). 
>> In fact, I "commented out" the generation of translation (*.ts) files and 
>> the problem also occured later on during a "rebuild"
>> (at least with my actual project).
>>
>> Or in other words: the generated CMakeLists.txt (generated by Qt Creator 
>> 4.14.0) simply does not work, neither on Windows > nor on macOS (at least 
>> not on Mojave".
>> There is no other cmake in the PATH (I specifically uninstalled an older 
>> version with "brew uninstall cmake". In fact, there is no > cmake at all in 
>> the PATH right now (I am exclusively building from within Qt Creator for the 
>> time being).
> I can reproduce the problem, but only with CMake 3.19.0.  I cannot reproduce 
> with CMake 3.18.4 nor CMake 3.19.2.

Oh, that's actually good news then :) Thanks for letting me know!

> Feel free to open a bug about this, so it's properly tracked.
>
Will do. However macOS support is currently not that urgent (my app
targets "Flight Simulator 2020" with "SimConnect" which runs on Windows
10 only - so until I have refactored my "connection code" into a proper
plugin I won't be able to compile on macOS anyway ;)), and I can live
with the reported "Windows tweaks" for now (namely "clearing the CMake
configuration/build files before doing a "rebuild all").

And in the meantime I will also get more familiar with CMake, too ;)

Thanks, Oliver

___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Qt6 - Making Qt installer package for Windows, Linux and OS X

[Till Oliver Knoll]

Am 09.12.20 um 11:14 schrieb Alexandru Croitor:
> Going forward, i'd expect improvements on "consumption of Qt with CMake" part 
> as well.

I can definitively confirm that creating your own Qt applications using
CMake yourself is not quite the same "out of the box"-experience as with
qmake (at least as far as "template projects setup with Qt Creator" are
concerned). Also refer to my other thread here ("Rebuilding cmake
project (in Qt Creator) fails - build directories write-protected?")

CMake support is just not quite there yet ;)

Cheers, Oliver

___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] qml: opengl failure

[ich]

Am January 6, 2021 5:54:02 AM UTC schrieb Alexander Dyagilev 
:
>Hello,
>
>I've tried to use this code:
>
>if(!qEnvironmentVariableIsSet("QT_OPENGL"))
>
>{
>
>//OnWindows,useANGLEsowedon'thavetoloadOpenGL
>
>//user-modedriversintoourapp.OGLdrivers(especiallyIntel)
>
>//seemtocrashtheappfarmoreoftenthanDirectX.
>
>qputenv("QT_OPENGL","angle");
>
>}
>
>It works fine in Windows 10. But in Windows 7 I'm getting the following
>
>message:
>
>libEGL.dll, libGLESV2.dll, d3dcompiler_47.dll does exist inside of our 
>app's directory.
>
>Why is this happening?

Hi,

i've no idea about the explicit issue, but to check the top most errors:
You have all this libs, including dependencies?
Have you checked them e.g. dependency walker, for loading issues?

Alex
-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Qt 6.0.0 released

[Till Oliver Knoll]

Am 09.12.20 um 16:04 schrieb ekke:
>
> I'm happy with the new Small Business License for my mobile app
> development. https://www.qt.io/qt-for-small-business
>
Well, here's the new catch (compared to Qt 5 perpetual licenses): if you
stop paying your license fees you now must pull your app(s) developed
with Qt 6 from all app stores (existing users may continue to use your
app, sure), or in other words: you can only sell your Qt 6 based apps
for as long as you keep paying the yearly Qt license fees. That also
impacts giving support for your existing apps: you can only do so for as
long as you have a valid (paid) Qt 6 license.

That might not be a big deal for those small businesses that keep
developing (new) Qt applications, but it may be an additional burden for
others.

Now I am not even critisising this decision: after all, everyone needs
to make (keep making) money. I was just trying to explain why some are
put off a bit by this license policy change decision.

Cheers, Oliver


___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Rebuilding cmake project (in Qt Creator) fails - build directories write-protected?

[Kai Köhne]

> From: Interest  On Behalf Of Till Oliver 
> Knoll
> Subject: Re: [Interest] Rebuilding cmake project (in Qt Creator) fails - 
> build directories write-protected?
>
> Am 31.12.20 um 16:02 schrieb Till Oliver Knoll:
> Am 31.12.20 um 15:29 schrieb James DeLisle:
> There are some on-going peculiarities with CMake and translation files, as 
> evidenced here:
> https://bugreports.qt.io/browse/QTBUG-76410
> Thanks for your reply! In fact, the problem is not only related to 
> translation files (but it occurs there first during a build). 
> In fact, I "commented out" the generation of translation (*.ts) files and the 
> problem also occured later on during a "rebuild"
> (at least with my actual project).
>
> Or in other words: the generated CMakeLists.txt (generated by Qt Creator 
> 4.14.0) simply does not work, neither on Windows > nor on macOS (at least not 
> on Mojave".
> There is no other cmake in the PATH (I specifically uninstalled an older 
> version with "brew uninstall cmake". In fact, there is no > cmake at all in 
> the PATH right now (I am exclusively building from within Qt Creator for the 
> time being).

I can reproduce the problem, but only with CMake 3.19.0.  I cannot reproduce 
with CMake 3.18.4 nor CMake 3.19.2.

I guess we need to update the CMake version in the SDK ASAP, and probably 
better test before doing the next update :/

Feel free to open a bug about this, so it's properly tracked.

Regards

Kai
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest