[Development] CI (5.5 branch) seems broken

Hello, I'm trying to submit https://codereview.qt-project.org/#/c/120725/ for a while and it keeps failing in some strange unrelated place. Cheers, BogDan. ___ Development mailing list Development@qt-project.org

Re: [Development] How to add OpenSSL support on Qt Android?

Hi, That page is only for adding OpenSSL support to Qt SDK. If you're building Qt yourself, then you need to add "-openssl -I /path/to/openssl/headres" to configure params. Yours, BogDan. On Wednesday 15 June 2016 13:28:39 Fabrice Salvaire wrote: > Dear All, > > I tried to follow

Re: [Development] What kind of airplane we want to build?

On Friday 22 January 2016 10:55:34 Cristian Adam wrote: > On Fri, Jan 22, 2016 at 11:59 AM, Marc Mutz wrote: > > I'm not sure about what outcome to expect, and I don't remember any > > numbers > > posted by anyone else, either. > > From the David Stone's Writing Robust Code >

Re: [Development] What kind of airplane we want to build?

Hi, Personally I'd like to add to the nice to have list: the exceptions. Yeah, I know that there are some people that don't like them, but for me the exceptions are like the life vest under you seat, it is very good to have them, of course it's not that good to be in the situation to need them

Re: [Development] Proposal to include QtGamepad as an add-on module

+1 BogDan. On Monday 25 January 2016 15:37:45 Agocs Laszlo wrote: > Hello, > > The Qt Gamepad module has been living in a qt-labs repo (*) for some time. > I'd like to propose to upgrade it to an add-on module and include it as a > Tech Preview in Qt 5.7. This would also benefit other modules,

Re: [Development] What kind of airplane we want to build?

On Friday 22 January 2016 12:32:25 Bogdan Vatra wrote: > On Friday 22 January 2016 10:55:34 Cristian Adam wrote: > > On Fri, Jan 22, 2016 at 11:59 AM, Marc Mutz <marc.m...@kdab.com> wrote: > > > I'm not sure about what outcome to expect, and I don't remember any > &g

Re: [Development] some questions about QtGamePad

Hi, From a gamepad perspective it's almost complete. Yes I know that there are gamepads out there with more buttons, QtGamepad it's a technical preview, so we can change it. IMHO we just need to add a few more generic buttons/axes and that's it. I also agree with Mike that Qt needs some

Re: [Development] Supported platforms for Qt 5.8

Hi, On Friday 19 February 2016 21:01:02 Knoll Lars wrote: > Hi, > > Now that 5.7 is branched, I'd like to propose that we update our list of > supported compilers and platforms for Qt 5.8. After some discussions with > different people, here's an initial proposal from my side: > [...] > > *

Re: [Development] 5.7 feature freeze

On Friday 26 February 2016 19:07:53 Nurmi J-P wrote: > Hi Lars, > > > On 27. jan. 2016, at 09.30, Knoll Lars > > wrote: > > > > If anybody else has a feature he believes absolutely has to make it to > > 5.7, get it done until Monday or talk to me :) > I would like

Re: [Development] Nominating Volker Krause for Approver status

+1 for my side! Cheers, BogDan. On Wednesday 30 March 2016 09:18:36 Knoll Lars wrote: > He isn’t yet? In that case, a big +1 from me :) > > Cheers, > Lars > > From: Development >

Re: [Development] Qt + GCC 6 no joy ?

On Friday 20 May 2016 07:40:19 Thiago Macieira wrote: > Em sexta-feira, 20 de maio de 2016, às 08:08:46 PDT, Denis Shienkov escreveu: > > Hi guys, > > > > you are talking about: > > > > * https://bugreports.qt.io/browse/QTCREATORBUG-16277 > > > > * https://bugreports.qt.io/browse/QBS-974 > >

[Development] Qt + GCC 6 no joy ?

Hi, Did anyone tried Qt (5.7) with GCC 6 ? I compiled Qt and QtCreator (using debian's gcc 6) but it crashes in v4 when I start QtCreator :(. It's a know issue or just me? Cheers, BogDan. ___ Development mailing list Development@qt-project.org

Re: [Development] Qt + GCC 6 no joy ?

Yep, looks very "familiar"! On Wednesday 18 May 2016 10:08:31 Liang Qi wrote: > https://bugreports.qt.io/browse/QTBUG-53373 ? > > On 18 May 2016 at 10:01, Bogdan Vatra <bogdan.va...@kdab.com> wrote: > > Hi, > > > > Did anyone tried Qt (5.7) with GCC

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

On Monday 09 May 2016 11:48:05 Marc Mutz wrote: > On Sunday 08 May 2016 01:12:16 Thiago Macieira wrote: > > On sábado, 7 de maio de 2016 22:05:32 PDT Nikita Krupenko wrote: > > > Re-sending to ml. > > > > > > > /mnt/store/Development/qt5/qtgamepad/src/plugins/gamepads/evdev/qevdev > > > > g > > >

Re: [Development] QML: Why C++11 scoped enums are not scoped in QML?

On miercuri, 27 iulie 2016 10:35:01 EEST André Somers wrote: > Op 27/07/2016 om 09:53 schreef BogDan Vatra: > >> That said, it would be a behavior change not to allow anymore the > >> previous > >> (unscoped) syntax to work with QML > > > > The unscope

Re: [Development] QML: Why C++11 scoped enums are not scoped in QML?

On marți, 26 iulie 2016 20:08:52 EEST Olivier Goffart wrote: > On Dienstag, 26. Juli 2016 08:33:31 CEST Thiago Macieira wrote: > > Em terça-feira, 26 de julho de 2016, às 17:50:38 PDT, BogDan Vatra escreveu: > > > Hi, > > > > > > Is there any reason why C++1

Re: [Development] QML: Why C++11 scoped enums are not scoped in QML?

On miercuri, 27 iulie 2016 09:08:32 EEST Thiago Macieira wrote: > On quarta-feira, 27 de julho de 2016 11:47:03 PDT BogDan Vatra wrote: > > On miercuri, 27 iulie 2016 10:35:01 EEST André Somers wrote: > > > Op 27/07/2016 om 09:53 schreef BogDan Vatra: > > > Would

Re: [Development] [QML]: Register global enums/flags to QML ?

On joi, 28 iulie 2016 09:22:37 EEST Olivier Goffart wrote: > On Dienstag, 26. Juli 2016 18:18:48 CEST BogDan Vatra wrote: > > Hello, > > > > I'd like to be able to register some "global" enums/flags to QML. I > > checked > > a little bit how Q

Re: [Development] QML: Why C++11 scoped enums are not scoped in QML?

On joi, 28 iulie 2016 09:52:56 EEST Dominik Holland wrote: > Am 28.07.16 um 09:41 schrieb Olivier Goffart: > > On Donnerstag, 28. Juli 2016 10:32:54 CEST BogDan Vatra wrote: > >> On miercuri, 27 iulie 2016 09:08:32 EEST Thiago Macieira wrote: > >>> On quarta-feira, 27

Re: [Development] [QML]: Why can't create Q_GADGETs from QML ?

.0 as Foo > > > var g = new Foo.ThatName(); > > > It's a bit of work to do, but I don't see a problem in principle. > > > Simon > > > From: Development <development-bounces+simon.hausmann=qt...@qt-project.org> >

Re: [Development] QML: Why C++11 scoped enums are not scoped in QML ?

oped > enums did not exist. I think it would be fine > > to add this feature to the JavaScript bindings for C++ classes. > > > Simon > > > From: Development <development-bounces+simon.hausmann=qt...@qt-project.org> > on behalf

[Development] [QML]: Why can't create Q_GADGETs from QML ?

Hi, Is there any reason why I can only use Q_GADGETs objects in QML, but not to create them? It will be nice if we can register Q_GADGETs as qml creatable types too. Cheers, BogDan. ___ Development mailing list Development@qt-project.org

[Development] [QML]: Register global enums/flags to QML ?

Hello, I'd like to be able to register some "global" enums/flags to QML. I checked a little bit how Qt does with all the enums from Qt namespace (qnamespace.h) and I end-up in qqmlbuiltinfunctions which does all the "magic" which can't be used by normal developers/libs. Because I think having

[Development] QML: Why C++11 scoped enums are not scoped in QML ?

Hi, Is there any reason why C++11 scoped enums are not scoped in QML ? If I have something like the following code in C++ class MyClass : public QObject { Q_OBJECT public: enum class MyEnum : uint16_t { Val1, Val2, } Q_ENUM(MyEnum) ); // register the class I'd like to use it in QML

Re: [Development] QML: Why C++11 scoped enums are not scoped in QML?

On marți, 26 iulie 2016 08:33:31 EEST Thiago Macieira wrote: > Em terça-feira, 26 de julho de 2016, às 17:50:38 PDT, BogDan Vatra escreveu: > > Hi, > > > > Is there any reason why C++11 scoped enums are not scoped in QML ? > > There's no trait to tell apart a scope

Re: [Development] Nominate Mike Krus as approver

On luni, 6 februarie 2017 12:26:03 EET Sean Harmer wrote: > Hi, > > I'd like to nominate Mike Krus as an approver. Mike contributed support for > Qt on tvOS along with the refactoring that went in as part of this. Mike > has done a lot of work within Qt 3D too. > > Disclaimer: Mike is a

Re: [Development] Notes on "Qt Build Systems" @ QtCon 2016

On marți, 6 septembrie 2016 17:35:03 EEST Cristian Adam wrote: > On Tue, Sep 6, 2016 at 5:14 PM, Kevin Kofler wrote: > > I guess somebody could even get CMake to write Qbs files, it would just be > > one more generator. :-) > > This was done already >

Re: [Development] Notes on "Qt Build Systems" @ QtCon 2016

On joi, 8 septembrie 2016 20:22:25 EEST Jake Petroules wrote: > I just found a perfect example of how hard building a JAR file is in qmake > for example, compared to qbs: IMHO will be even easier if instead: qbs-javac-scan.qbs: [...] files: [ "io/qt/qbs/**/*.java" ] [...] You'll

Re: [Development] QDataStream: blackbox or document all versions?

Hi, What about Option 3 :) ? Use another binary format for serialization: flatbuffers [1] which is super fast, has a stable binary format and can be used by lots of other languages [2]. Cheers, BogDan. P.S. On my personal fork [3] I even added Qt support, and it can be used from QML as well

Re: [Development] A new approach for Qt main()

On vineri, 9 decembrie 2016 12:58:46 EET Eskil Abrahamsen Blomfeldt wrote: > Den 09.12.2016 12:40, skrev Tor Arne Vestbø: > > On 09/12/2016 11:44, Lars Knoll wrote: > >> Well, the problem is that the main() entry point is causing huge amounts > >> of issues on at least Android and iOS. > > > > I

Re: [Development] Qt 5.10 schedule proposal

It's just me or did you forgot to add 5.8.1? Cheers, BogDan. On joi, 13 aprilie 2017 11:48:06 EEST Jani Heikkinen wrote: > After short internal discussion here is my proposal for those patch level > releases: > > - Branch '5.6.3' from '5.6' at the end of May/beginning of June, 5.6.3 >

Re: [Development] Qt 5.10 schedule proposal

On joi, 13 aprilie 2017 12:34:27 EEST Tuukka Turunen wrote: > On 13/04/2017, 15.30, "Development on behalf of Konstantin Tokarev" > <development-bounces+tuukka.turunen=qt...@qt-project.org on behalf of > annu...@yandex.ru> wrote: > > > 13.04.2017

Re: [Development] Proposal for Qt 5.10 platforms and configurations changes

For Android I'd like to support 64 bit platforms (arm and x86) BogDan. On April 27, 2017 12:29:08 PM GMT+03:00, Heikki Halmet wrote: >Hi, > > > >Below we have proposal for changes in supported platforms and >configurations from Qt 5.9 to 5.10. > >Please comment if the

Re: [Development] Proposal for Qt 5.10 platforms and configurations changes

Hi Jake, On joi, 27 aprilie 2017 15:00:58 EEST Jake Petroules wrote: > > On Apr 27, 2017, at 7:40 AM, BogDan Vatra <bogdan.va...@kdab.com> wrote: > > > > For Android I'd like to support 64 bit platforms (arm and x86) > > > They are already s

Re: [Development] Future of QBS

On luni, 16 octombrie 2017 17:38:53 EEST Christian Gagneraud wrote: > On 16 October 2017 at 15:42, Kevin Kofler wrote: > > Christian Gagneraud wrote: > >> I would resume this post as "I love CMake, CMake is the only way. > >> You're all wrong." > >> This post doesn't

Re: [Development] Nominating Kevin Funk for Maintainer qtbase/Build Systems/CMake

On vineri, 13 octombrie 2017 21:30:59 EET André Pönitz wrote: > Hi all. > > I would like to nominate Kevin Funk for Maintainer of the > Build Systems/CMake area. > > Kevin is effectively doing the job today. > +1 from me! Cheers, BogDan. ___

Re: [Development] Time to switch to android-clang

On marți, 19 decembrie 2017 11:25:17 EET Sergio Martins wrote: [...] > > The problem of clang generating bigger binaries was much improved with > -Oz, now size increase is only 10%. > Which, on ARM, usually means the bins are slower ;-) [...] Anyway, a +0.5 also from my side. Cheers, BogDan.

Re: [Development] Qt branches & proposal how to continue with those

Hi, As long as we don't have enough time fix all the problems in a non LTS release, I think releasing at least one patch version is not that bad ... Yours, BogDan. În ziua de luni, 29 ianuarie 2018, la 10:15:51 EET, Simon Hausmann a scris: > Hi, > > > I feel that we are generally guiding

Re: [Development] Proposing David Faure as maintainer of Qt Models

+1 from me. Cheers, BogDan. În ziua de luni, 12 martie 2018, la 19:10:35 EET, Sérgio Martins a scris: > Hi, > > > Although the wiki says Qt Models don't have a maintainer I'd say David > Faure has been an unofficial maintainer. > David is one of the top contributors to model related code and

Re: [Development] Fornux C++ Superset

Hi, În ziua de marți, 24 aprilie 2018, la 04:08:19 EEST, Phil Bouchard a scris: > Greetings, > > Because Qt is very powerful, I would like to clarify the importance of > the following problems despite my previous informal attempts: > - The recent Qt 5.10.1 still randomly crashes for apps written

Re: [Development] QtCS 2018 - Serialisation session notes

Hi, > > === Protobuf === > > * Need volunteers to write a Proof of Concept > ** plugin to protoc? IMHO flatbuffers (https://google.github.io/flatbuffers/) has quite a few advantages over protocol buffers (one that I really like is that the only dependency your app has is a single .h file,

Re: [Development] Android binary size with Clang

În ziua de joi, 21 iunie 2018, la 11:38:29 EEST, Sérgio Martins via Development a scris: > On 2018-06-21 04:40, Thiago Macieira wrote: > > Hello > > > > Yesterday during the PDXCPP Meet Up, I was asked if we had come up with > > a good > > solution to the increase in size of native binaries on

Re: [Development] Qt 6 buildsystem support requirements

În ziua de joi, 2 august 2018, la 18:06:02 EEST, Thiago Macieira a scris: > On Wednesday, 1 August 2018 23:13:13 PDT BogDan Vatra via Development wrote: > > > Now that is nice, as we know that the moc, uic, rcc outputs are > > > platform- > > > independent. That shou

Re: [Development] Raising the minimum Android NDK version

AFIK qt 5.12 will use ndk r16 or better. On July 29, 2018 6:16:30 PM GMT+03:00, Thiago Macieira wrote: >On Monday, 16 July 2018 08:50:05 PDT Thiago Macieira wrote: >> On Monday, 16 July 2018 00:08:44 PDT Bogdan Vatra via Development >wrote: >> > The clang support was adde

Re: [Development] Raising the minimum Android NDK version

For 5.11 we used 10e and I'm afraid we can't afford to change it without proper testing. Cheers, BogDan. On July 29, 2018 10:11:53 PM GMT+03:00, Thiago Macieira wrote: >On Sunday, 29 July 2018 11:15:38 PDT BogDan Vatra via Development >wrote: >> AFIK qt 5.12 will use ndk r

Re: [Development] Qt 6 buildsystem support requirements

Hi, Did you knew that qbs can build all but windows targets at once from your Linux machine? Using mingw you can cross compile Qt for windows, but you probably want to run tests and to check if the code compiles with msvc. This feature might not seem pretty useful for linux, but is very

Re: [Development] Qt 6 buildsystem support requirements

y, 1 August 2018 11:58:02 PDT BogDan Vatra via Development >wrote: >> Hi, >> >> Did you knew that qbs can build all but windows targets at once >from your >> Linux machine? > >That's not news. qmake can do that, provided you have the toolchains. >You &g

Re: [Development] Qt 6 buildsystem support requirements

Hi, În ziua de joi, 2 august 2018, la 01:31:10 EEST, Thiago Macieira a scris: > On Wednesday, 1 August 2018 12:46:04 PDT BogDan Vatra via Development wrote: > > Hi, > > > > qmake can't compile them all *at once* e.g. $ qmake && make will compile > >

Re: [Development] Qt 6 buildsystem support requirements

Hi În ziua de joi, 2 august 2018, la 09:33:10 EEST, Joerg Bornemann a scris: > On 08/02/2018 08:18 AM, Simon Hausmann wrote: > > Given that the output of the moc changes depending on what platform and > > compiler dependent pre-processor macros are supplied, I would say that > > the output is not

Re: [Development] Qt 6 buildsystem support requirements

În ziua de joi, 2 august 2018, la 09:49:48 EEST, Lars Knoll a scris: > > On 2 Aug 2018, at 08:13, BogDan Vatra via Development > > wrote: […] > > > > It will be nice if this feature is mandatory for Qt 6, so let's add it to > > > > > > your requ

Re: [Development] Qt 6 buildsystem support requirements

În ziua de joi, 2 august 2018, la 11:02:30 EEST, Lars Knoll a scris: > > On 2 Aug 2018, at 09:52, BogDan Vatra wrote: > > > > În ziua de joi, 2 august 2018, la 09:49:48 EEST, Lars Knoll a scris: > > > >>> On 2 Aug 2018, at 08:13, BogDa

Re: [Development] Raising the minimum Android NDK version

În ziua de vineri, 13 iulie 2018, la 23:50:36 EEST, Thiago Macieira a scris: > On Wednesday, 11 July 2018 23:32:16 PDT Thiago Macieira wrote: > > On Wednesday, 11 July 2018 23:00:50 PDT Liang Qi wrote: > > > https://bugreports.qt.io/browse/QTQAINFRA-1681 > > >

Re: [Development] Qt 6 buildsystem support requirements

Hi, În ziua de duminică, 22 iulie 2018, la 12:11:44 EEST, Tobias Hunger a scris: > On Sat, Jul 21, 2018, 07:38 Bogdan Vatra via Development < > > development@qt-project.org> wrote: > > You really hate QBS don't you ? :) > > Do you have so few arguments for qbs that you

Re: [Development] Qt 6 buildsystem support requirements

Hi, În ziua de duminică, 22 iulie 2018, la 12:18:06 EEST, Tobias Hunger a scris: > On Sat, Jul 21, 2018, 14:49 Jean-Michaël Celerier < > > jeanmichael.celer...@gmail.com> wrote: > > +1, I was flabbergasted when the big objection against CMake in Qt 6 > > boiled down to "it does not supports all

Re: [Development] How would Android switching to Vulkan would impact Qt for Android?

Hi, În ziua de sâmbătă, 21 iulie 2018, la 11:06:30 EEST, Vincas a scris: > Story: > > https://www.xda-developers.com/google-android-q-vulkan-graphics-render-ui/ > > I wonder how it could affect QML apps built for Android? It doesn't mean that OpenGL support will be removed, so there should be

Re: [Development] Qt 6 buildsystem support requirements

Hi, În ziua de sâmbătă, 21 iulie 2018, la 05:35:48 EEST, Thiago Macieira a scris: > Hello > > Having spent far too much time trying to figure out why crappy buildsystems [...] > > 1) Ease of obtention > > a) Must be packaged by all major package managers where Qt 6 is expected to > be

Re: [Development] Qt 6 buildsystem support requirements

Hi, În ziua de sâmbătă, 21 iulie 2018, la 09:40:47 EEST, Allan Sandfeld Jensen a scris: > On Samstag, 21. Juli 2018 07:38:10 CEST Bogdan Vatra via Development wrote: > > Hi, > > > > În ziua de sâmbătă, 21 iulie 2018, la 05:35:48 EEST, Thiago Macieira a > > scris: >

Re: [Development] Build system for Qt 6

Hi, GN is the closest build system to QBS, the only problem it has it's controled by Google and these guys are sometime had to work with. Cheers, BogDan. În ziua de joi, 1 noiembrie 2018, la 10:30:01 EET, Nikolai Kosjar a scris: > On 10/29/18 1:17 PM, Lars Knoll wrote: > > Given that we are

Re: [Development] Build system for Qt 6

Hi, Yes, "hard to work with" :). Cheers, BogDan. În ziua de joi, 1 noiembrie 2018, la 11:24:29 EET, Vlad Stelmahovsky a scris: > you mean "hard to work with"? > > On 11/1/18 9:34 AM, Bogdan Vatra via Development wrote: > > Hi, > > > >GN is th

Re: [Development] Build system for Qt 6

Hi, În ziua de marți, 30 octombrie 2018, la 19:11:20 EET, Oswald Buddenhagen a scris: > On Tue, Oct 30, 2018 at 01:16:43PM +0200, Bogdan Vatra wrote: > > c.2) back then, none of the existing build system could deliver enough > > information to IDEs to enable prefect code

Re: [Development] Build system for Qt 6

Hi, DISCLAIMER: I was one of the biggest QBS supporters! QBS was a dream too good to be true, its main goals were: a) a simple sintax which anyone can use b) no extrenal dependeincies to configure/build & deploy your apps c) designed with tooling in mind: c.1) imagine a world where you can

Re: [Development] Build system for Qt 6

Yup, it's a sad day for people who liked QBS. Personally I'll check GN, which has a nice syntax, not as nice as QBS but ... :) . În ziua de luni, 29 octombrie 2018, la 18:32:11 EET, Ray Donnelly a scris: > Agreed, a brilliant bit of technology, such a shame to see it deprecated. > > On Mon, Oct

Re: [Development] Build system for Qt 6

Hi, În ziua de luni, 12 noiembrie 2018, la 15:06:00 EET, Joerg Bornemann a scris: > On 10/30/18 12:16 PM, Bogdan Vatra via Development wrote: > > Late to the game, but I feel the urge to comment on some things. > > > > c.2) Incomplete! A while ago, I created a QBS

Re: [Development] Qt 5.12 branch is broken for Android

Hi, [...] > > Now configure mixes host libs with the target (android) ones, which IMHO > > is > > very wrong when cross-compiling :). > > Can some qmake master take a look and fix the problem? > > if you're sure you have the latest revision and a completely clean build > tree (including no stray

[Development] Qt 5.12 branch is broken for Android

Hi, I'm trying to compile Qt for Android and 5.12 branch received quite a lot configure changes which broke Android builds (though I thought that 5.12 branch is for bug fixes only). Now configure mixes host libs with the target (android) ones, which IMHO is very wrong when cross-compiling

Re: [Development] Nominating Brett Stottlemeyer for Approver status

+1 În ziua de luni, 18 martie 2019, la 10:05:22 EET, Ville Voutilainen a scris: > Brett is the maintainer of Qt Remote Objects. Thus he should be > documented as a maintainer, and should also be an approver. Brett has > been effectively maintaining QRO since 2014, so it seems like a slam >

Re: [Development] A deployment tool for Linux

Hi, Personally I think it's a great idea. I used linuxdeployqt myself and it worked. The only problem I saw it was the speed, it takes quite a lot to complete (e.g. it took a few minutes, while androiddelopqt takes less than 10 seconds). But witl some love I'm pretty sure it can be improved

Re: [Development] Qt online SDK security problems

o a newer version. > This is (IIRC) why the installer switched to this approach. > > I can see your point as well, especially when your project is flexible > enough to update dependencies. But that is not the case for many projects > out there. > BR, > Maurice > > > > &g

[Development] Qt online SDK security problems

Hi, Long time ago the Qt online SDK used to help the users to use the latest and the safest Qt version all the time. Sadly that was changed, IMHO without too much thinking, and now a lot of users (I'm one of them) are stucked with outdated versions. A few days ago I installed 5.12.2 and

Re: [Development] Qt online SDK security problems

În ziua de joi, 18 aprilie 2019, la 13:54:15 EEST, André Pönitz a scris: > On Thu, Apr 18, 2019 at 10:24:24AM +0300, BogDan Vatra via Development > > wrote: > > Hi, > > > > Long time ago the Qt online SDK used to help the users to use the > > latest and t

Re: [Development] Qt 5 types under consideration for deprecation / removal in Qt 6

Hi, În ziua de vineri, 31 mai 2019, la 08:36:31 EEST, Thiago Macieira a scris: > On Thursday, 30 May 2019 15:51:26 PDT Konstantin Tokarev wrote: > > BTW, are you also planning to drop support for using PCH with GCC-like > > compilers when building Qt? It's a thing that is trivial to do with make

Re: [Development] Qt 5 types under consideration for deprecation / removal in Qt 6

În ziua de vineri, 31 mai 2019, la 19:03:46 EEST, Thiago Macieira a scris: > On Thursday, 30 May 2019 22:45:02 PDT Bogdan Vatra via Development wrote: > > Hi, > > > > În ziua de vineri, 31 mai 2019, la 08:36:31 EEST, Thiago Macieira a scris: > > > On Thursday, 30 Ma

Re: [Development] Proposing CMake as build tool for Qt 6

În ziua de joi, 6 iunie 2019, la 14:45:14 EEST, Simon Hausmann a scris: > Hi, > > In the past months we, some developers from the Qt Company and KDAB, > have made good progress on the port of Qt to use CMake as build tool. > Since the initial prototype, the port has advanced very well and its >

Re: [Development] Proposing CMake as build tool for Qt 6

with some WIP non-merged patches in qtbase, I was able to > build parts of qtbase with CMake, targeting armv8 iOS. > So there's still some work to be done, but in principle it should be > doable. > > > On 6. Jun 2019, at 15:13, Bogdan Vatra via Development > > wrote:

Re: [Development] Proposing CMake as build tool for Qt 6

l that they > don't represent show-stoppers from a decision making point of view. I'm > confident that if others in the C++ community are able to build apps for > iOS with CMake, then we will also be able to build Qt for it. > > Simon > > > Fr

Re: [Development] Proposing CMake as build tool for Qt 6

Hi, There is one more missing feature to add to your list: build & debug builds for msvc in one go (same as qmake does now, a single "make" command will build both targets). Also I wonder when do you plan to release Qt6? Because according to Thiago's "what a buildsystem must to have list"

Re: [Development] Proposing CMake as build tool for Qt 6

Hi, În ziua de joi, 13 iunie 2019, la 18:22:14 EEST, Thiago Macieira a scris: > On Thursday, 13 June 2019 01:06:06 PDT Bogdan Vatra via Development wrote: > > Hi, > > > > There is one more missing feature to add to your list: build & debug > > > > builds f

Re: [Development] Proposing CMake as build tool for Qt 6

În ziua de sâmbătă, 15 iunie 2019, la 19:32:52 EEST, Thiago Macieira a scris: > On Friday, 14 June 2019 23:45:47 PDT Bogdan Vatra via Development wrote: [...] > > > So, as long as we need to provide libs, (qml) plugins for debug & release > > I think building them in

[Development] Proposing a wiki page for Qt6 buildsystem requirements

Hi, I'd like to propose a new wiki page (https://wiki.qt.io/Qt6/Requirements ?) where, at least all platform maintainers, will add all the features they need for that platform. As the Android maintainer I'm not happy with current qmake support, not to mention cmake support which in this

Re: [Development] Proposing CMake as build tool for Qt 6

Hi, > > Though I can't help but wonder what is the magical ingredient in build > systems that has the power to generate such vigorous debates over the > internet. > Because the buildsystem makes the difference between wasting so many hours on writing build system scripts or using that time

Re: [Development] Proposing CMake as build tool for Qt 6

[...] > > > > [...] > > > > Are you seriously thinking that Qt is going to use scripts from some > > random > > github projects ?!?!? > > There is a choice: with cmake you either spend hours yourself developing > stuff, or reuse results of those who went through that hell before you :) Or use

Re: [Development] Proposing CMake as build tool for Qt 6

Hi, [...] > > > qnx > > you mean like software companies using Qt do, today ? > https://github.com/mapbox/mapbox-gl-native/blob/master/platform/qt/qnx.cmake > > vxworx > > VxWorks ships with CMake so there must be at least some amount of support. ( >

[Development] Is CI broken ?

Hi, I'm trying to stage a patch( https://codereview.qt-project.org/c/qt/qtbase/ +/266489 ), but I'm getting the same error each time. Is anyone working on it? Cheers, BogDan. ___ Development mailing list Development@qt-project.org

Re: [Development] Supported compilers for Qt 6

On 2019-08-12 22:34, Thiago Macieira wrote: On Monday, 12 August 2019 08:11:38 PDT Thiago Macieira wrote: distributions and Android SDKs use. Any word on what Clang the Android SDK we'll require uses? NDK r19 and NDK r20 are shipped with clang 8.0, which according to

Re: [Development] HEADS-UP: QStringLiteral

Hi, Isn't silly to have so many wrappers around a such a simple thing as strings? All the major frameworks out there (i.e. Java, C#) they have a single String which does all the magic. In Qt we have: QString, lost of QString::fromXXX, QLatin1String, QStringLiteral, QStringView, QByteArray

Re: [Development] HEADS-UP: Branching '5.14' from 'dev' complete, Qt 5.14 Feature Freeze in effect & '5.15' created

Hi, I can't edit https://wiki.qt.io/New_Features_in_Qt_5.14 ;-(. Cheers, BogDan. În ziua de marți, 27 august 2019, la 10:00:46 EEST, Jani Heikkinen a scris: > Hi all, > > Final downmerge from dev to '5.14' is now done. All other modules are ready > and merges in but qtbase merge >

Re: [Development] Proposal for an efficient and robust (de)serialization mechanism working with Qt-supported data

Hi, It will be great if we can find a way to use it any (de)serialization mechanism (e.g. proto buff, flat buffers, etc.) not only with only one (qt specific). Cheers, BogDan. În ziua de vineri, 30 august 2019, la 16:42:54 EEST, Simon Hausmann a scris: > Hi Arnaud, > > I think that perhaps

Re: [Development] HEADS-UP: QStringLiteral

Hi, În ziua de miercuri, 21 august 2019, la 00:12:59 EEST, Thiago Macieira a scris: > On Tuesday, 20 August 2019 08:56:06 PDT Bogdan Vatra via Development wrote: > > Isn't silly to have so many wrappers around a such a simple thing as > > > > strings? > >

Re: [Development] HEADS-UP: QStringLiteral

Hi, În ziua de miercuri, 21 august 2019, la 13:53:02 EEST, Giuseppe D'Angelo via Development a scris: > Hi, > > On 21/08/2019 11:50, Bogdan Vatra via Development wrote: > >Personally I'm not going to waste my time learning 10 sting wrappers > >and > > > &g

Re: [Development] HEADS-UP: QStringLiteral

Hi, > Returning to your original post: > >>> All the major frameworks out there (i.e. Java, C#) they have a > >>> single String which does all the magic. > > Yes, and those systems are all built with the assumption that client > code doesn't care if every single time anything happens to a string

Re: [Development] Gerrit update

Hi, Since yesterday I can't submit any of my patches. The submit "button" is gay, e.g. https://codereview.qt-project.org/c/qt/qtbase/+/273675 Am I doing something wrong? Cheers, BogDan. În ziua de luni, 30 septembrie 2019, la 09:40:36 EEST, Heikki Halmet a scris: > Hi, > > Coin fixed and

Re: [Development] Qt Contributors' Summit 2019 - Registration open!

Hi, Considering that QtCS and QtWS are both in Berlin and both in Nov, is there any reason why QtCS date was not choose immediately after QtWS (7-9)? Cheers, BogDan. În ziua de miercuri, 18 septembrie 2019, la 17:42:18 EEST, Kai Köhne a scris: > Hi, > > Registration to the Qt Contributors

Re: [Development] Nominating Cristian Adam as approver

+1 Cheers, BogDan. În ziua de sâmbătă, 9 noiembrie 2019, la 21:07:42 EET, Tobias Hunger a scris: > +1 > > Best Regards, > Tobias ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development

[Development] CI is quite unstable on windows

Hi, I'm trying to integrate https://codereview.qt-project.org/c/qt/qtbase/+/ 278646 but it always fails on windows in the very same place. Can an windows expert to check these tests and if they can't be fixed/reliable, then blacklist them on windows? Thanks. Cheers, BogDan.

[Development] Make Qt6 JNI API safer to use

Hi, I started to review and move androidextras to qtbase (qtbase/src/corelib/ platform/android). Here we have a problem with our Qt JNI API. The problem is that in Java exceptions are (ab)used everywhere. Even if we have a way to check for exceptions after each call in Qt, it's not used (not

Re: [Development] Make Qt6 JNI API safer to use

În ziua de joi, 5 martie 2020, la 17:21:11 EET, Thiago Macieira a scris: > On Thursday, 5 March 2020 07:14:44 PST Vitaly Fanaskov wrote: > > I think something like std::expected is a nice thing to have. > > > > There is some experimental implementation of std::expected: > >

Re: [Development] Make Qt6 JNI API safer to use

Hi, În ziua de joi, 5 martie 2020, la 17:14:44 EET, Vitaly Fanaskov a scris: > I think something like std::expected is a nice thing to have. > > There is some experimental implementation of std::expected: > https://github.com/TartanLlama/expected. > That implementation is my favorite, I really

Re: [Development] Changes to Qt offering

În ziua de marți, 28 ianuarie 2020, la 08:37:47 EET, Benjamin TERRIER a scris: > Le mar. 28 janv. 2020 à 03:22, Thiago Macieira > > a écrit : > > On segunda-feira, 27 de janeiro de 2020 14:47:46 PST NIkolai Marchenko > > > > wrote: > > > Assuming we have a VM that is restricted to connecting to

Re: [Development] Changes to Qt offering

Hi Lars, În ziua de luni, 27 ianuarie 2020, la 16:34:44 EET, Lars Knoll a scris: > Hi all, [...] > > One is a change in policy regarding the LTS releases, where the LTS part of > a release is in the future going to be restricted to commercial customers. > All bug fixes will (as agreed on the Qt

Re: [Development] The future of smart pointers in Qt API

Hi, It seem the community it's still pissed off on TQC, so I'm going to break the ice here :). I'll personally go with std::* (not only for smart ptrs but for everything else (e.g. containers), except QString of course). QPointer still needs to stay as there is nothing in std:: which we

  1   2   >