Re: [Development] Thread priority on Linux - Qt 6.9.1

Is the RealtimeKit you're referring to the product from Cloudflare? not the cloudflare product, the dbus service: https://github.com/heftig/rtkit https://venam.net/blog/unix/2025/03/24/rtkit.html -- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/develo

Re: [Development] Thread priority on Linux - Qt 6.9.1

If not, please consider this suggestion: add a method to QThread that allows setting the scheduling policy, or allows setting the scheduling policy and priority in a single call similar to pthread_setschedparam(). Sorry, the API in question is reserved for root. Since Qt applications are almost

Re: [Development] Resurrecting QtGamepad

- are there things we want to do to support a broader use case? thinking out loud: gamepads tend to be HID devices. there might be a use case for a more generic HID implementation in Qt, not only supporting gamepads but a wide range of devices that talk HID (possibly including custom hardware

Re: [Development] Proposal to raise the minimum CMake version needed to build and use Qt 6.9

one point to consider is that cmake does not have any run-time dependencies and it is extremely easy to install independently from the OS: the binaries provided by kitware are fully self-contained and can be installed in parallel to system-provided cmake. Installing binaries compiled by someone

Re: [Development] Proposal to raise the minimum CMake version needed to build and use Qt 6.9

We'd like to bump the minimum required CMake version for building and using Qt to CMake 3.26. The pending change is https://codereview.qt-project.org/c/qt/qtbase/+/603886 The rationale is easier maintenance of build system code, and allowing to provide better public cmake apis and behaviors (c

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

> 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 increase the complexity, and add to the overall maintenance of our > QA system. Ou

Re: [Development] Qt 5.9's new garbage collector documentation? + root_ptr

fwiw, to get this thread back to the main topic, i still fail to see how root_ptr deals with objects which are reachable from multiple roots, which have independent lifetime >>> >>> Please provide an example. >> >> i've posted some already > > I'm working on the parser right no

Re: [Development] Qt 5.9's new garbage collector documentation? + root_ptr

>> fwiw, to get this thread back to the main topic, i still fail to see how >> root_ptr deals with objects which are reachable from multiple roots, >> which have independent lifetime > > Please provide an example. i've posted some already ___ Developme

Re: [Development] Qt 5.9's new garbage collector documentation? + root_ptr

> Oh sorry they did invent Minesweeper and Basic, I give them that... https://en.wikipedia.org/wiki/Dartmouth_BASIC -- fwiw, to get this thread back to the main topic, i still fail to see how root_ptr deals with objects which are reachable from multiple roots, which have independent lifetime __

Re: [Development] Qt 5.9's new garbage collector documentation? + root_ptr

> On the other hand, I have good news as I think I have found a way to > simulate functions that return a function. how to you cope with structures like: function foo( outObject ) { var object = {} outObject.object = object outObject.result = function() { return object } return fu

Re: [Development] Qt 5.9's new garbage collector documentation? + root_ptr

> - the parameters of the function will remain unaffected if they are used as > r-values > - the parameters of the function will require a deep copy of the expression > if they are used as l-values https://en.wikipedia.org/wiki/Evaluation_strategy#Call_by_sharing function foo( arg ) { var i

Re: [Development] Qt 5.9's new garbage collector documentation? + root_ptr

> If there is one root_ptr per > Javascript function then all local variables are guaranteed to be > destroyed. And closures aren't too big of a deal either because child > objects can easily refer to their parent. > > But returning local variables might need some work on root_ptr such as > "unli

Re: [Development] New Qt 5.8 rc snapshot for testing

> All known blockers should be fixed in these packages and we are > targeting to release Qt 5.8.0 Tue 17^th January if nothing really > serious found during testing. So please inform me immediately if there > is some new blocker in the packages. QTBUG-56163 is the main blocker for me, which preven

Re: [Development] [Announce] Qt 5.8.0 RC released

>>> cd gui/ && ( test -e Makefile || >>> /Users/tim/dev/qt3rd/build-Qt-5.x-dev-macx-clang-static/qtbase/bin/qmake >>> -o Makefile /Users/tim/dev/qt3rd/qtbase/src/gui/gui.pro -qtconf >>> /Users/tim/dev/qt3rd/build-Qt-5.x-dev-macx-clang-static/qtbase/bin/qt.con >>> f -- -qt-zlib -qt-harfbuzz -no-glib

Re: [Development] [Announce] Qt 5.8.0 RC released

>> like with 5.8-beta, i'm still having issues when linking statically >> against a prebuilt static library of libpng (because libpng depends on >> zlib). compare: https://bugreports.qt.io/browse/QTBUG-56163 >> >> in short, it gives me: >>> ERROR: Feature 'system-png' was enabled, but the pre-condi

Re: [Development] [Announce] Qt 5.8.0 RC released

> We have released Qt 5.8.0 RC today, see > http://blog.qt.io/blog/2016/12/22/qt-5-8-0-release-candidate-available/ > Thanks to everyone involved. hi all, like with 5.8-beta, i'm still having issues when linking statically against a prebuilt static library of libpng (because libpng depends on zl

Re: [Development] Qt 5.9

hi all, >>> The currently sold CPU's are not really the measurement stick here. The >>> measurement stick is actually installed Win 32 systems. >> Yes, but what's the 32-bit Windows install base which is capable of running >> Qt? We only support Windows 7 and above now, so I can't imagine it's ver

Re: [Development] QtBase WIP branch request

>> We’re working on an update to the macOS/Cocoa platform plugin, >> and I would like to request a WIP branch where the changes can >> be finalized: >> >>wip/remac >> > you have Good Reasons (TM) for creating a branch according to > https://wiki.qt.io/Branch_Guidelines#Creating_a_new_feature_br

Re: [Development] [5.7.1] release schedule?

>> the 5.7.1 release was scheduled for sept/oct ... october is almost over, >> so i wonder what's the state of it? >> >> thanks a lot, >> tim > > Hi Tim, > > I don't know the exact release plan either, but I guess they want to get > 5.6.2 released first. The branch 5.7.1 already exists, so this w

[Development] [5.7.1] release schedule?

hi all, the 5.7.1 release was scheduled for sept/oct ... october is almost over, so i wonder what's the state of it? thanks a lot, tim ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] 5.7.0-rc compile error

> Are you trying out of the source builds ? that's my usual workflow as i need to compile static and dynamic libs from the same source folder ... > I opened a ticket yesterday for this, specifically Qt3D, but it can > compiles if you run from the root tree on the source. it also compiles fine w

[Development] 5.7.0-rc compile error

hi all, compiling 5.7.0-rc (sometimes) fails with the following error when building qt as static library: > error 15-Jun-2016 20:04:06make[4]: *** No rule to make target > `/Volumes/build/bamboo-build/THIRDP-QT9-BUILDMAC/build-Qt-5.7.0-rc-macx-clang-static/qt3d/lib/libQt53DQuick_debug.a', >

Re: [Development] Supported platforms for Qt 5.8

> Might be a bit premature, but is anyone opposed to dropping OS X 10.9 > and iOS 7.x in Qt 5.8? yes: it will prevent some users (including me) to update to qt-5.8, as our minimum osx requirement is still 10.9. ___ Development mailing list Development@q

Re: [Development] CMake, PRLs, static Qt and private Qt deps

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 > Before Qt 5.0 was released, the CMake helper files included a > useful feature that read .prl files in order to find and include > Qt dependencies (such as, say, libqtpcre, but also dynamic system > libraries, and whatever else) in CMake builds ag

Re: [Development] [5.7-beta] qtgamepad compile failure

>>> I've just downloaded qt-everywhere-opensource-src-5.7.0-beta.tar.xz and >>> confirmed that qtgamepad/include/QtGamepad/qtgamepadglobal.h is present >> >> ah, thanks for the pointer ... importing qt tarballs into git repos is >> full of surprises: qtgamepad/.gitignore ignores 'include' >> >> my

Re: [Development] [5.7-beta] qtgamepad compile failure

>>> I've just downloaded qt-everywhere-opensource-src-5.7.0-beta.tar.xz and >>> confirmed that qtgamepad/include/QtGamepad/qtgamepadglobal.h is present >> >> ah, thanks for the pointer ... importing qt tarballs into git repos is >> full of surprises: qtgamepad/.gitignore ignores 'include' >> >> my

Re: [Development] [5.7-beta] qtgamepad compile failure

> I've just downloaded qt-everywhere-opensource-src-5.7.0-beta.tar.xz and > confirmed that qtgamepad/include/QtGamepad/qtgamepadglobal.h is present ah, thanks for the pointer ... importing qt tarballs into git repos is full of surprises: qtgamepad/.gitignore ignores 'include' my usual workflow i

[Development] [5.7-beta] qtgamepad compile failure

compiling the qt-5.7-beta tarball with msvc2013/64bit/static libraries, out-of-tree build gives me: --- cl -c -FIQtGamepadDepends -YuQtGamepadDepends -Fp.pch\debug\Qt5Gamepadd_pch.pch -nologo -Zc:wchar_t -FS -Zi -MDd -D_HAS_EXCEPTIONS=0 -GR -W3 -w34100 -w34189 -w44996 /Fd..\..\lib\Qt5Gamepadd.pdb

Re: [Development] [5.7-beta] compile error with xcode-6.4

>> * legacy code using deprecated sdk functions might not compile a certain >> codebase (depending on the age of your codebase this maybe lead to >> significant effort) > > Is that because of bugs you talked about below, or is there another reason > why > this would happen? Why would it not comp

Re: [Development] [5.7-beta] compile error with xcode-6.4

>>> r.h:759:21: error: destination for this 'memmove' call is a pointer to >>> class containing a dynamic class> >>> 'QPixmap'; vtable pointer will be overwritten >>> [-Werror,-Wdynamic-class-memaccess]> >>> memmove(abegin, aend, (d->size - itemsToErase - >>>

[Development] [5.7-beta] compile error with xcode-6.4

compiling the 5.7-beta tarball with xcode-6.4 fails with: > In file included from /Users/tim/dev/qt3rd/qtbase/src/gui/image/qicon.cpp:1: > In file included from > /Users/tim/dev/qt3rd/qtbase/src/gui/kernel/qt_gui_pch.h:69: > In file included from /Users/tim/dev/qt3rd/qtbase/include/QtGui/qbitmap.

[Development] ci timeouts

hi all, it seems that i cannot integrate changes into 5.6 anymore: > http://testresults.qt.io/coin/integration/qt/qtbase/tasks/1456811813.thrift_bin seems that i'm always hitting a timeout somewhere ... is this a known issue? i was hoping that the following changes could make it into 5.6: https:

Re: [Development] New Qt 5.6.0 RC snapshot available, please test

> We have finally packages for testing, > > > Windows: http://download.qt.io/snapshots/qt/5.6/5.6.0-rc/335/ > > Linux: http://download.qt.io/snapshots/qt/5.6/5.6.0-rc/331/ > > Mac:http://download.qt.io/snapshots/qt/5.6/5.6.0-rc/271/ > > src:

Re: [Development] HEADS UP: OSX build requirements for 5.7

>> ... or newer toolchains can introduce regressions ... > > But we usually detect those and work around them. qt is a framework, toolchain bugs may pop up in user code ... ___ Development mailing list Development@qt-project.org http://lists.qt-proje

Re: [Development] HEADS UP: OSX build requirements for 5.7

>> we have seen funny toolchain bugs, with 10.10 sdk and 10.8 deployment >> target on 10.8, where std::exceptions could not be caught ... compiling >> against 10.8 sdk solved that issue. > > Regardless of whether that is a valid approach or not, the fact that people > are doing that poses a probl

Re: [Development] HEADS UP: OSX build requirements for 5.7

>> Does anyone see any issues with this going forward? > > We need to be sure Qt compiles with the latest Xcode available on each of the > OS X versions that Qt can be developed on. Since 10.8→10.11 updating is free, > the only extra test is 10.7. we have seen funny toolchain bugs, with 10.10 s

Re: [Development] Qt 5.6.0 beta. win32 vs11 32 bit fails with uic.exe showing dialog qt5core.dll cannot be found.

> The thing is that in Qt 5.5.1, uic.exe and qlalr.exe were also build > using qtcore dll, but there this was not a problem. > In wec build they are always build statically, i think that should be > made uniform. > > Now that I look closer i see the cause of the problem: > set PATH=D:\TFS\bld__G

Re: [Development] Qt 5.6.0 beta. win32 vs11 32 bit fails with uic.exe showing dialog qt5core.dll cannot be found.

> I found out that the % is due to using jom in 5.5.1 and nmake in 5.6.1. > I looked into the Makefiles and bot had the same term. When i use jom > for 5.6 i see (set > QT_PLUGIN_PATH=D:\TFS\bld__GLOBAL\Qt5.6.0\WIN32-VS11-32\qtbase\plugins) > & (set > PATH=D:\TFS\bld__GLOBAL\Qt5.6.0\WIN32-VS11-32\q

Re: [Development] High-DPI 5.6 beta update

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Your thoughts on projects that use ONLY SVG image resources and not PNG/JPEG? >>> >>> But the above: >>> >>> 1) already works >> >> kind of ... the above will rasterize the svg for the resolution >> of the Image which is then upscaled, t

Re: [Development] High-DPI 5.6 beta update

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 >> Image { id: gicon source: qrc:/img/test.svg anchors.fill: parent >> } >> >> Pro File: >> >> QT += svg >> >> Outside of the app, in the Android Manifext.xml and IOS, you need >> to provide pre-generated launcher PNG icons, but inside the app >>

Re: [Development] New qt5.6 beta snapshot available

> Namespaced builds are only tested on Linux IIRC, not os x. Similarly > static builds happen for ios, where the plugin loading code is > probably not used. ah, that explains why all namespaced build failures that i saw were on osx :) ___ Development ma

Re: [Development] New qt5.6 beta snapshot available

>>> These aren't yet final beta packages but please test these & report all >>> new blocker immediately >> >> no new blockers, but i still need to apply these two patches to be able >> to compile 5.6-beta on osx: >> >> https://codereview.qt-project.org/#/c/139577/ >> https://codereview.qt-project.o

Re: [Development] New qt5.6 beta snapshot available

> These aren't yet final beta packages but please test these & report all > new blocker immediately no new blockers, but i still need to apply these two patches to be able to compile 5.6-beta on osx: https://codereview.qt-project.org/#/c/139577/ https://codereview.qt-project.org/#/c/139981/ both

Re: [Development] Fwd: Change in qt/qtbase[5.6]: Make the C++11 atomic support the default, if available

On 17/10/15 01:27, Thiago Macieira wrote: > FYI > > Please report any issues you have with broken compilers that did not > implement > std::atomic properly. I'd like to include them in the release notes. > > These are already known to fail, so please don't report them: > - Xcode 5.0's clang com

Re: [Development] 4.8 does not compile on OS X 10.11 - https://bugreports.qt.io/browse/QTBUG-48079

> https://bugreports.qt.io/browse/QTBUG-48079 > > Looks like Apple began removing deprecated functions. > > Since 4.8 is now closed for changes that aren't security-related, that means > 4.8 will not compile on OS X 10.11. apple continuously evolves their API (read: break old code), but afaict

Re: [Development] Qt 5.5.1 snapshot available

hi! > We have finally Qt 5.5.1 snapshot available for your testing in > http://download.qt.io/snapshots/qt/5.5/5.5.1/ i'm wondering, would it be possible to provide source snapshots as well? this would help those people to 'quickly test' a snapshot, whose build infrastructure requires tarballs.

Re: [Development] Your actions needed, Qt5.5.0 RC & Final is nearing!

> We are quite close to Qt 5.5.0 RC & final releases. Plan is to put RC > out Thu 11.6.2015 & Final Tue 23.6.2015. To be able to keep the schedule > we need to make sure all real blockers are fixed in RC so that it will > be really RC & there won't be so much changes between RC & Final. So > follo

Re: [Development] iOS, libpcre16, QString::trimmed_helper()

I'm attempting to use libQt5Core with self compiled qt5.5 snapshot, which is a couple of weeks old. The link fails, complaining about missing libpcre16. I believe that is not standard on iOS, at least it does not come up when looking for "Other Libs" pcre in XCode. Ther

Re: [Development] iOS, libpcre16, QString::trimmed_helper()

>> I'm attempting to use libQt5Core with self compiled qt5.5 snapshot, >> which is a couple of weeks old. The link fails, complaining about >> missing libpcre16. >> I believe that is not standard on iOS, at least it does not come up when >> looking for "Other Libs" pcre in XCode. There does see

Re: [Development] The dark side of QtMultimedia

>>> Yes, this could also simply be our qtmultimedia unit tests. Run the >>> tests >>> on your target platforms and if they pass it should be reasonably safe >>> to >>> assume that things are working. Of course we’re not there currently, our >>> coverage for QtMM is not good enough afaict. >> >> QtM

Re: [Development] Event loop of Qt window in DLL injected into another process

>> Hello, I have a problem with event loop. I am creating DLL which I am >> injecting into MFCapplication – my dll spawns a qt window. it works fine, >> except ‘input’ to spawned window is blocked: for ex. i have edit box, i am >> typing into it and nothing happens – unless, I resize / minimalzie w

[Development] [5.3-rc] framework differences between macx-clang-32 and macx-clang

hi all, not sure if this is a bug or a feature, or a problem or not, but it occurred to me that the Info.plist files differ between 32bit and 64bit frameworks: > --- osx-clang-32/lib/QtMultimediaQuick_p.framework/Contents/Info.plist > 2014-05-10 18:29:13.0 +0200 > +++ osx-clang-64

Re: [Development] Qt 5.3 beta release coming soon

but 5.3 hasn't compass (for ios and android) and not webkit for >>> android? N. >>> >>> ... and no Qt3D!? >>> >> >> >> And still no skynet like AI that predict the future? >> > These questions about the features may seem silly to some, but some of > them are critical for

Re: [Development] Qt 5.3 Beta1

> Qt 5.3 Alpha is now out and plan is to release Beta1 during the next few > weeks. That’s why it is really important to recognize the issues which > must be fixed before we can put beta1 out. There is already some issues > linked in the beta1 metabug, see > https://bugreports.qt-project.org/browse

Re: [Development] Qt's Leak-on-exit policy

>> In QtQuick, QSGRenderLoop::instance() can create a QSGWindowsRenderLoop >> using new that it never destroys. The memory is always pointed to by a >> static member pointer, so it's never "lost" exactly, but the memory is >> never freed by Qt (but hopefully will be by any decent OS). Is this a bug

Re: [Development] qt5.2.0: javascriptcore compile fix

>> hi, >> >> in order to compile qt-5.2.0-rc1 as static library with c++11 on osx, i >> need to apply the attached patch. >> the issue had been reported in a comment in [1], but i guess the issue >> was missed, because the bug was closed before. >> >> iac, attached patch fixes the issue, would be g

[Development] qt5.2.0: javascriptcore compile fix

hi, in order to compile qt-5.2.0-rc1 as static library with c++11 on osx, i need to apply the attached patch. the issue had been reported in a comment in [1], but i guess the issue was missed, because the bug was closed before. iac, attached patch fixes the issue, would be great if it can be incl