[Development] Add QTBUG title to new release changelog

Good morning, I was curious to see what changed in Qt 6.0.2 release and found a list of fixed QTBUGS: [qtbase] 443ce5d073 Fixes: QTBUG-89578 b61275ee72 Fixes: QTBUG-90042 e255716291 Fixes: QTBUG-74088 The QTBUG number itself does not tell me much, hence it is very hard to predict if anything

Re: [Development] Qt6 repo

Alex Blasche schrieb am Mi. 13. Jan. 2021 um 11:58: > > -Original Message- > > From: Development On Behalf Of > > Nibedit Dey > > Is there any plan to move the qt6 source code to a different repo (qt6)? > > Currently, the branch lies inside the qt5 repo. > > Is there going to be a Qt6

Re: [Development] Commercial-only LTS phase starts: Closing the 5.15 branch(es) on 5th January

Am Mo., 4. Jan. 2021 um 15:57 Uhr schrieb Tuukka Turunen < tuukka.turu...@qt.io>: > > > Hi Roland, > > > > Just so that there is no misunderstanding Qt 5.15.2 release stays > available for all users, it is just the upcoming LTS phase patch releases > that will be commercial only. In essence for

Re: [Development] Commercial-only LTS phase starts: Closing the 5.15 branch(es) on 5th January

Am Mo., 4. Jan. 2021 um 14:38 Uhr schrieb Benjamin TERRIER < b.terr...@gmail.com>: > > > On Mon, 4 Jan 2021 at 14:14, Oswald Buddenhagen > wrote: > >> On Mon, Jan 04, 2021 at 10:55:03AM +, Tuukka Turunen wrote: >> >With Qt 6.0.0 released and the first patch release (Qt 6.0.1) coming >>

Re: [Development] Qt 5.14 MinGW debug build doesn't add debug suffix

Am Fr., 10. Jan. 2020 um 09:40 Uhr schrieb Roland Winklmeier < roland.m.winklme...@gmail.com>: > Am Mi., 8. Jan. 2020 um 20:09 Uhr schrieb Thiago Macieira < > thiago.macie...@intel.com>: > >> On Wednesday, 8 January 2020 10:10:06 PST Sérgio Martins via Developme

Re: [Development] Qt 5.14 MinGW debug build doesn't add debug suffix

Am Mi., 8. Jan. 2020 um 20:09 Uhr schrieb Thiago Macieira < thiago.macie...@intel.com>: > On Wednesday, 8 January 2020 10:10:06 PST Sérgio Martins via Development > wrote: > > Wondering if there's a reason why the suffix is needed in the first > > place... > > I thought only MSVC had problems

Re: [Development] Qt 5.14 MinGW debug build doesn't add debug suffix

Am Di., 7. Jan. 2020 um 13:52 Uhr schrieb Roland Winklmeier < roland.m.winklme...@gmail.com>: > Hey everyone, > > First, happy new year! > > Second, I switched my nightly build to 5.14 branch and was building debug > binaries as usual. Configure arguments: > > confi

[Development] Qt 5.14 MinGW debug build doesn't add debug suffix

Hey everyone, First, happy new year! Second, I switched my nightly build to 5.14 branch and was building debug binaries as usual. Configure arguments: configureArguments=-developer-build -debug -opensource -nomake examples -nomake tests -confirm-license -opengl desktop -dbus -openssl -I

Re: [Development] Requiring minimum GCC 7/MinGW (was: Dropping MinGW support in Qt 6 (Was: HEADS-UP: QStringLiteral))

Am Do., 22. Aug. 2019 um 22:47 Uhr schrieb Thiago Macieira < thiago.macie...@intel.com>: > On Thursday, 22 August 2019 12:05:39 PDT Danila Malyutin wrote: > > Isn't it already the case: > https://doc.qt.io/qt-5/supported-platforms.html > > ? > > Looks like it. > > I'll dust-off the

Re: [Development] Intention of dropping UWP 2015 x86 builds in favour of MinGW 32-bit packages

Am Mi., 6. Feb. 2019 um 13:01 Uhr schrieb Jesus Fernandez < jesus.fernan...@qt.io>: > > The original mail said nothing about 5.12.2. And I would remove support > for both compilers in 5.13. Any 32 bits is an outdated platform. > > > 32 bit is not only about platform. 32 bit applications still run

[Development] VulkanSDK path added to includes since 5.12.1

Hey everyone, I noticed that since the upgrade to 5.12.1 the following include option is added to my projects compiler flags: "-IC:\VulkanSDK\1.0.51.0\include" It seems to origin from "modules/qt_lib_gui_private.pri:QMAKE_INCDIR_VULKAN". It does not do any harm to my build, but I wonder if that

[Development] How to create a Qt5 offline installer myself

Dear Qt Devs, I think I asked this question in the past, but I never got a reasonable answer. The question is actually quite simple: How can I create a Qt5 offline installer for example for 5.11.1 MinGW 5.3.0 32 bit? I'm aware of the qt/qtsdk repository and its scripts. There is also some high

Re: [Development] Prebuilt 32-bit versjon for MSVC 2017

2018-02-21 13:44 GMT+01:00 Harald Kjølberg : > > Hi, > > Currently Qt ships with 32-bit binaries for MSVC 2015, but not for MSVC > 2017. The Qt Company have received requests for adding prebuilt 32-bit > binaries also for MSVC 2017. By adding more prebuilt binaries, we

Re: [Development] Stop delivering 32 bit MinGW binaries from 5.12 ->

2017-12-21 11:37 GMT+01:00 Jani Heikkinen : > With Qt 5.11 it seems we can finally drop MSVC2013 so we could > "temporarily" add MinGW 64 bit pre-build binaries in our packages in > addition to 32 bit ones and remove 32 bit MinGW pre-built binaries from > 5.12 onwards.

Re: [Development] Qt 5.10 beta 3 released

2017-11-01 11:59 GMT+01:00 Jani Heikkinen : > > Qt 5.10 beta3 is out. Instructions how to get the release are here: > https://wiki.qt.io/How_to_get_snapshot_via_online_installer. > Hi Jani, first of all thanks a lot for this new way of shipping beta versions. It is so

Re: [Development] Behavior change for QMake install targets since 5.9

Hi Simon, Preamble: The problem I was trying to solve with wildcards was to install a shared library target into two different directories. The first directory is installed with a simple 'INSTALLS += target' line. The other path is installed manually by a second INSTALLS definition and the files

[Development] Behavior change for QMake install targets since 5.9

Dear Qt developers, since 5.9 some of my projects install targets are failing. Investigation has shown that the generated Makefiles reference now a different INSTALL executable. Before it was 'install' from GNU coreutils and now it is calling 'qmake -install qinstall'. Apart from the fact that I

Re: [Development] [Announce] Qt 5.9 Beta released

Am 07.04.2017 um 12:33 schrieb List for announcements regarding Qt releases and development: > Hi, > > I am happy to inform Qt 5.9 Beta is released today, see > http://blog.qt.io/blog/2017/04/07/qt-5-9-beta-released/. > As informed earlier beta binaries are available only via qt online installer

[Development] Warning about unknown escape sequences in qtremoteobjects

Dear Qt developers, when building Qt 5.9.0 from git (by coincidence it was the same commit as 5.9.0 Alpha), I got many of the following warnings in qtremoteobjects: In file included from main.cpp:43:0: repparser.h:2:10: warning: unknown escape sequence: '\.' #line 57

Re: [Development] Focusing bug fixes to 5.9 branch and patch releases during H1/17

Hi Tuukka, 2017-02-16 17:13 GMT+01:00 Tuukka Turunen : > As multiple people and teams have planned their development according to > initially agreed feature freeze time of Qt 5.9, it would be very > inefficient to reopen 5.9 now or postpone getting the release out. > I

Re: [Development] Focusing bug fixes to 5.9 branch and patch releases during H1/17

2017-02-15 12:52 GMT+01:00 Shawn Rutledge : > > > On 15 Feb 2017, at 11:11, Marc Mutz wrote: > > > > On Wednesday 15 February 2017 10:36:33 Sean Harmer wrote: > >> First of all, apologies for not being able to make the release meeting > >> yesterday. I

Re: [Development] Qt 5.9

> On 28 Nov 2016, at 16:40, Alexander Blasche wrote: > > Ok, let's summarize and restate the package list for Qt 5.9 based on the > comments provided on this mail thread. The list describes the delta to Qt 5.8 > packages: > > * MinGW remains 5.3 using 32 bit Since

[Development] Symbol strip warnings when installing release products on Mac OS X since 5.6.1

Dear list, I have upgraded my Mac OS X CI node to Qt 5.6.1. Since then I see several warnings at the build step 'make install' similar to: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/strip: symbols referenced by indirect symbol table entries that can't

Re: [Development] Does Qt 5.6 still depend on ICU?

On 05/08/2016 01:10 AM, Thiago Macieira wrote: > On sábado, 7 de maio de 2016 23:25:16 PDT Roland Winklmeier wrote: >> From wiki pages (https://wiki.qt.io/Qt_5.6_Tools_and_Versions and >> https://wiki.qt.io/Building_Qt_5_from_Git), I understood that, ICU is >> only required

[Development] Does Qt 5.6 still depend on ICU?

Dear Qt Devs, I'm currently preparing installers for a cross platform application (Win, Linux, OSX). I have investigated, which dependencies apart from the Qt5 libraries themselves are need to be shipped as well. But I'm a bit confused about the role of ICU. >From wiki pages

Re: [Development] How can Qt 5.6.0 MinGW pass in CI with QTBUG-49971 open?

2016-03-03 16:51 GMT+01:00 Thiago Macieira <thiago.macie...@intel.com>: > On quinta-feira, 3 de março de 2016 10:51:40 PST Roland Winklmeier wrote: > > No matter if I download the source from download.qt.io or clone from git > > and run the normal build as configured in CI,

Re: [Development] How can Qt 5.6.0 MinGW pass in CI with QTBUG-49971 open?

2016-03-03 9:14 GMT+01:00 Thiago Macieira <thiago.macie...@intel.com>: > On quinta-feira, 3 de março de 2016 00:06:41 PST Thiago Macieira wrote: > > On quinta-feira, 3 de março de 2016 08:56:35 PST Roland Winklmeier wrote: > > > So how is it possible that this error does

[Development] How can Qt 5.6.0 MinGW pass in CI with QTBUG-49971 open?

Dear list, I'm trying to understand a strange situation and hope you can enlighten me. In December I have raised QTBUG-49971 (a FTBFS bug) since it was not possible to build MinGW 4.9 with the alpha sources and also from git since then. The issue is obvious: Commit

[Development] QMetaTypeIdvoid::Defined illegal in Qt 5.5 beta

Hi all, I was testing the Qt 5.5 beta binaries with my application and quickly run into the following issue: Short version: The expression QMetaTypeIdvoid::Defined seems to be no longer allowed in 5.5. It is fine until 5.4.2 (or more precise until 3cf8e426f49ee6adb1090865854506aa92316ce3). Is

Re: [Development] QMetaTypeIdvoid::Defined illegal in Qt 5.5 beta

Hi Olivier, On 05/16/2015 12:34 PM, Olivier Goffart wrote: This was not intentional. I made a fix here: https://codereview.qt-project.org/112436 I was about to suggest the same and then saw your email. I was able to patch my local installation and it works perfectly. Thanks for the quick

Re: [Development] QtRemoteObjects - POD types derive from QObject

Hi Brett, thanks for your quick answer. We have a patch for the initial version of documentation in progress. Should be out in the next week or two. That sounds brilliant. I'm looking forward to it. This contradicts the QObject policy to be entities and not copyable. I was even more

[Development] QtRemoteObjects - POD types derive from QObject

Dear list, a while ago the QtRemoteObjects project was started in the playground area. I had followed the discussions closely, because I'm running a project which has a perfect use case for QtRemoteObjects. I haven't had much time to look into the details yet, but now I did. In the absence of

[Development] qmake command line assignments are not considered by config.tests

Dear Qt devs, I addressed the question below first to the interest list. But since nobody replied, I did some investigations and found out this behavior is caused by the macro qtCompileTest defined in qtbase/mkspecs/features/configure.prf. I also found a codereview similar to what I had planned

Re: [Development] qmake command line assignments are not considered by config.tests

2014-10-30 15:26 GMT+01:00 Roland Winklmeier roland.m.winklme...@gmail.com : Dear Qt devs, I addressed the question below first to the interest list. But since nobody replied, I did some investigations and found out this behavior is caused by the macro qtCompileTest defined in qtbase

Re: [Development] Why is QSignalSpy using Qt::DirectConnection?

As promissed I had a look into QTestEventLoop. QSignalSpy::wait() isn't thread-safe because it's using QTestEventLoop instead of a regular QEventLoop. That former does use a timer and, unlike the latter, you can't stop the loop from outside the loop's own thread. Just to be sure: The

[Development] Why is QSignalSpy using Qt::DirectConnection?

Dear list, quick question: I spotted the class QSignalSpy while writing unit tests for one of my projects. There was nothing written in the documentation, that it is not thread safe and had assumed it is. So I connected signals from a QObject running in a different thread and got several warnings

Re: [Development] Why is QSignalSpy using Qt::DirectConnection?

QSignalSpy::wait() isn't thread-safe because it's using QTestEventLoop instead of a regular QEventLoop. That former does use a timer and, unlike the latter, you can't stop the loop from outside the loop's own thread. That was indeed the origin of the warnings. They appeared after

Re: [Development] QtDBus Improvements

On 09/30/2014 01:49 PM, Thiago Macieira wrote: On Tuesday 30 September 2014 12:22:26 Daniele E. Domenichelli wrote: So, are these improvements still in the plan for QtDBus? Has anyone else been working on them? Where can I start? Hi Daniele Yes, those are still the targets and so far no

Re: [Development] QtMultimedia and Musepack

Am 22.08.2014 14:04, schrieb Cornelius Hald: I recently ported application from Qt4 to Qt5 and I rewrote a bit the audioplayer in it. Now it is using QtMultimedia instead of Phonon. There is an unresolved dependency issue with the combination Qt5 - GStreamer: Qt5 uses GStreamer on Linux,

[Development] QtDBus roadmap

Hi there, this quote originated from Request for a sandbox area: Replicant, but I did not want to hijack this discussion for something different. On 05/31/2014 01:33 AM, Thiago Macieira wrote: One of the goals for QtDBus is to replace the need to have libdbus-1 installed. We discussed this at

Re: [Development] QtQml value types

2014-04-24 22:42 GMT+02:00 Dominik Holland dominik.holl...@pelagicore.com: I like that idea, but couldn't we do something like this ? qRegisterWrapperMyWrapper(qMetaTypeIdYourType()) MyWrapper is a QObject based class which can whatever you want and gets YourType as reference or per value.

Re: [Development] Question about Qt's future

2014-04-27 13:31 GMT+02:00 Peter Kümmel syntheti...@gmx.net: On 21.04.2014 13:39, Roland Winklmeier wrote: - Memory consumption: Even a mini example took about 70 MB of memory, QtWidgets need a lot less. This is not a complain, I know the JS runtime needs its initial memory. It was just

[Development] QtQml value types

Hi list, we discussed the topic whether non-QObject types can be used in QML or not several times. The last time is only a few days ago as part of the Qt future discussions. So I had some thoughts what needs to happen to solve this issue. I can remember someone told me there are plans to add

Re: [Development] Question about Qt's future

If I want to access this methods from QML I would have to derive them from QObject and register it in the QML context. Not necessarily, depends on what you want to do. However, it is true that it would be nice to have something similar to QtScript's binding facilities.

Re: [Development] New Features in Qt-5.3

2014-02-27 18:20 GMT+01:00 Thiago Macieira thiago.macie...@intel.com: Em qui 27 fev 2014, às 12:32:36, Roland Winklmeier escreveu: Because we haven't received requests for this. We have for OS X, going as far back as Qt 4.3. Sorry for this stupid question, but how must a request look like

Re: [Development] QtDBus in official Windows and OSX installers

Am 06.02.2014 18:02, schrieb Thiago Macieira: Em qui 06 fev 2014, às 17:28:40, Roland Winklmeier escreveu: But my main question is, is there a chance QtDBus is shipped officially and what needs to be done for that. I guess one point is to run the dbus unit tests, but what else needs to be done

Re: [Development] Trigger Qt event loop from external message loop

, Roland Winklmeier roland.m.winklme...@gmail.com wrote: Thanks very much Olivier and Thiago! That works brilliant. No idea why I forgot that QThread must not be used. But its of course obvious. I made a quick setup with native threads (std::thread is unfortunately not supported

Re: [Development] Trigger Qt event loop from external message loop

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 14.12.2013 02:16, schrieb Thiago Macieira: On sábado, 14 de dezembro de 2013 00:45:20, Roland Winklmeier wrote: Since I cannot run Qt's event loop with QApplication::exec() - I dont want the plugin to block the parent application - I try

Re: [Development] Trigger Qt event loop from external message loop

19:23, schrieb Thiago Macieira: On sábado, 14 de dezembro de 2013 12:42:32, Roland Winklmeier wrote: n qthread_win.cpp QThreadPrivate::start - void QThreadPrivate::createEventDispatcher(QThreadData *data) { QEventDispatcherWin32 *theEventDispatcher = new QEventDispatcherWin32; data

[Development] Trigger Qt event loop from external message loop

Hi there, I'm working on an application using Qt5 for its window framework. The requirement for this application is to run standalone and as a plugin for a native application. While the case standalone application is easy, I'm struggling a bit with the plugin part. I have the following in mind:

[Development] Add API method to QDBusServer allowing anonymous authentication

Hi there, first of all I want to say hello. I was using Qt since quite a while now, but never did any developing for Qt itself. For my next project I identified some things I would need to add to the offical Qt libraries. Since I don't want to role out my customised ones, but stick with the