Am Mittwoch, 3. August 2022, 16:35:16 CEST schrieb Thiago Macieira:
> POWER and S/390 are very IBM-specific. They're still active, but I don't
> think we have much relevance in that market. And Sparc has ceased being
> active. For those three I don't think we can hope to expect any kind of
> perfor
Am Donnerstag, 25. November 2021, 17:03:37 CET schrieb Thiago Macieira:
> On Tuesday, 23 November 2021 00:40:14 MST Joerg Bornemann wrote:
> > The patches that do the move are here:
> > https://codereview.qt-project.org/c/qt/qtbase/+/382055
> > https://codereview.qt-project.org/c/qt/qttools/+/38209
Am Mittwoch, 10. November 2021, 16:26:43 CET schrieb Thiago Macieira:
> On Wednesday, 10 November 2021 03:29:15 PST Marius Kittler wrote:
> > Am Dienstag, 9. November 2021, 19:59:29 CET schrieb Thiago Macieira:
> > > On Friday, 5 November 2021 08:28:20 PST Scott Bloom wrote:
&g
Am Montag, 15. November 2021, 16:46:31 CET schrieben Sie:
> On Monday, 15 November 2021 05:52:46 PST Joerg Bornemann wrote:
> > There's already a target called host_tools to build the necessary tools.
> > An install target/component for it is missing though, see QTBUG-91243.
>
> Which tools does i
Am Dienstag, 9. November 2021, 19:59:29 CET schrieb Thiago Macieira:
> On Friday, 5 November 2021 08:28:20 PST Scott Bloom wrote:
> > Why wouldn’t they simply have two versions of Qt ( or more) the one they
> > are targeting for desktop, and the previous one they are targeting for
> > android/"remo
Am Dienstag, 14. September 2021, 09:51:21 CEST schrieb Joerg Bornemann:
> The maintenance burden is next level. This would mean to keep all
> internal API that's used in lib/cmake compatible. Apparently forward and
> backward if I read your requirements correctly.
>
I'm afraid that's the next cha
Am Freitag, 10. September 2021, 16:58:55 CEST schrieb Thiago Macieira:
> Qt 6 supports using the moc from a different build of Qt, to help with the
> bootstrapping issue and also so you don't always run a debug-mode moc in
> your debug builds of Qt.
>
> Is that moc required to be from the same Qt
Hi,
It looks like your experience with the new build system is the very opposite
of my experience. I've found it to work much more flawlessly, especially with
regards to cross-compilation targeting mingw-w64 and Android (haven't tested
the Android build much, though).
---
> first and foremost
Am Dienstag, 27. Oktober 2020, 19:48:43 CET schrieben Sie:
> The library now has the Qt6 prefix in its name, so it should not be an
> issue. Or are you thinking of something else?
No, I wasn't thinking about something else. I've now built beta2 for Windows
and the library is indeed called `libQt6
Am Dienstag, 27. Oktober 2020, 17:34:44 CET schrieb Thiago Macieira:
> Have we fixed it?
>
> I do not plan on updating qtchooser for Qt 6. Qt 6 should not install any
> binary with the same name as Qt 5 did.
For the GNU/Linux target is seems to work when setting a few CMake variables:
https://gi
Hi,
Am Dienstag, 9. Juni 2020, 12:07:02 CEST schrieb Bogdan Vatra via Development:
> I'm using qmake for Qt6 when I'm doing Android work, also for this reason.
> I don't want to build Qt twice just to use a "cool and superior" build system.
>
> Just out of curiosity, can some pretty please remind
Am Donnerstag, 19. September 2019, 11:08:51 CEST schrieb Jay Gupta:
> Hello , i have a feature request for Qt 6. Currently there is no/not good
> enough notification support for Qt for android.
>
> It was quite difficult to implement push notification for my app in past.
>
> If it's possible i wo
12 matches
Mail list logo
