Re: [Development] Qt Network Maintainership Changes

Em terça-feira, 6 de setembro de 2016, às 20:05:26 PDT, Richard Moore escreveu: > As some of you may know, I'm planning to step down as maintainer of Qt > Network. This is because now that the Qt company has people in a position > to work on the network stack full time I think it makes much more s

Re: [Development] Notes on QtCore session @ QCS2016

Em terça-feira, 6 de setembro de 2016, às 17:10:19 PDT, Kevin Kofler escreveu: > Thiago Macieira wrote: > > It was a *choice* not to depend on the C++ Standard Library ABI for > > features outside of the language support. The choice was made during Qt > > 5.0 development, in response to the -no-st

Re: [Development] A faster qUtf8Printable for static trace points?

On Dienstag, 6. September 2016 11:52:15 CEST Thiago Macieira wrote: > Em terça-feira, 6 de setembro de 2016, às 20:48:39 PDT, Milian Wolff escreveu: > > > That change is interesting and we could accept it, but I still wouldn't > > > want it used in tracepoints. You avoid the allocation, but you're

[Development] Qt Network Maintainership Changes

Hi All, As some of you may know, I'm planning to step down as maintainer of Qt Network. This is because now that the Qt company has people in a position to work on the network stack full time I think it makes much more sense for them to be the maintainer - it doesn't mean I'll be moving away from

Re: [Development] A faster qUtf8Printable for static trace points?

Em terça-feira, 6 de setembro de 2016, às 20:48:39 PDT, Milian Wolff escreveu: > > That change is interesting and we could accept it, but I still wouldn't > > want it used in tracepoints. You avoid the allocation, but you're still > > converting to UTF-8. Your benchmark doesn't show it because your

Re: [Development] A faster qUtf8Printable for static trace points?

On Dienstag, 6. September 2016 06:59:40 CEST Thiago Macieira wrote: > Em segunda-feira, 5 de setembro de 2016, às 21:20:12 PDT, Milian Wolff > > escreveu: > > Hey Thiago, others. > > Hey Milian > > Is this what you were looking for me for on Sunday afternoon? Yes :) > > bool QLibraryPrivate::l

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

On 06-Sep-16 19:59, André Pönitz wrote: On Tue, Sep 06, 2016 at 05:35:03PM +0200, 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

Cristian Adam wrote: > This was done already > , > but it was removed from CMake due to bad feedback from > Qt Creator people. Interesting, but why was that done on top of existing makefile generators? I'd expe

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

Jake Petroules wrote: > Again, useless, because Qbs is more powerful and at a much higher level of > abstraction, so a generator would only be useful in the reverse direction. Of course, the generator would not use all the features of Qbs, just the minimum subset that is needed to do the work. >

Re: [Development] Notes on QtCore session @ QCS2016

Giuseppe D'Angelo wrote: > So please do not derail this sub-topic. The subject at hand here is > using Standard Library datatypes in our public API. And I was just pointing out that doing so also waters the API consistency, in addition to the ABI issues. > 1) BECAUSE. THEY. ARE. NOT. BETTER. In

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

On Tue, Sep 06, 2016 at 05:35:03PM +0200, 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

Sent from my iPhone > On 06 Sep 2016, at 17:35, 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, but it was removed from CMake

Re: [Development] Notes on QtCore session @ QCS2016

On Tuesday 06 September 2016 18:01:18 Marc Mutz wrote: > Noo don't feed the Troll...! :) (with apologies to the original Trolltech people!) -- Marc Mutz | Senior Software Engineer KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company Tel: +49-30-521325470 KDAB - Qt, C++ and OpenGL Experts

Re: [Development] Notes on QtCore session @ QCS2016

Noo don't feed the Troll...! :) -- Marc Mutz | Senior Software Engineer KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company Tel: +49-30-521325470 KDAB - Qt, C++ and OpenGL Experts ___ Development mailing list Development@qt-project.org http://lis

Re: [Development] Notes on QtCore session @ QCS2016

Il 06/09/2016 17:10, Kevin Kofler ha scritto: > I think it was a mistake to remove -no-stl to begin with, and that Qt API > should not be littered with ugly std:: APIs, not just for ABI reasons, but > also for API (consistency) reasons. Having APIs which follows the naming in the Standard Libra

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

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 , but it was removed from

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

06.09.2016, 18:24, "Jake Petroules" : >> On Sep 6, 2016, at 5:14 PM, Kevin Kofler wrote: >> >> Ch'Gans wrote: >>> I never wanted to use CMake b/c for me it look like a gross hack >>> (Reminds me of GNU M4). >> >> The CMake language is much easier to use than m4, and also there is just one >> lay

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

On Sep 6, 2016, at 5:14 PM, Kevin Kofler mailto:kevin.kof...@chello.at>> wrote: Ch'Gans wrote: I never wanted to use CMake b/c for me it look like a gross hack (Reminds me of GNU M4). The CMake language is much easier to use than m4, and also there is just one layer rather than having autoconf

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

Ch'Gans wrote: > I never wanted to use CMake b/c for me it look like a gross hack > (Reminds me of GNU M4). The CMake language is much easier to use than m4, and also there is just one layer rather than having autoconf on top of m4, with shell script snippets mixed in. There is a reason CMake i

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

Ch'Gans wrote: > If I followed this reasoning, I would still be writing my programs in > Motorola assembler... pea msg(%pc) jbsr puts addq.l #4,%a7 rts msg: .asciz "And this would be wrong, why? ;-)" or if you prefer the more traditional syntax: pea msg(PC) jsr puts addq.l #4,a7 rts msg: d

Re: [Development] Notes on QtCore session @ QCS2016

Thiago Macieira wrote: > It was a *choice* not to depend on the C++ Standard Library ABI for > features outside of the language support. The choice was made during Qt > 5.0 development, in response to the -no-stl option being removed. It was > originally done so that applications and libraries on

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

On Sep 6, 2016, at 4:34 PM, Thiago Macieira mailto:thiago.macie...@intel.com>> wrote: Em terça-feira, 6 de setembro de 2016, às 16:29:38 PDT, Ulf Hermann escreveu: Do we have a policy about inappropriate content posted to mailing lists and similar communication channels? No, but there was a sid

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

Em terça-feira, 6 de setembro de 2016, às 16:29:38 PDT, Ulf Hermann escreveu: > Do we have a policy about inappropriate content posted to mailing lists and > similar communication channels? No, but there was a side-discussion at QCS that we should write and adopt a Code of Conduct. -- Thiago Ma

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

Em terça-feira, 6 de setembro de 2016, às 14:00:55 PDT, Laszlo Agocs escreveu: > Using one "bin" is the default behavior, yes, but one can pass -hostprefix > to separate them upon install. > > > http://doc-snapshots.qt.io/qt5-5.8/embedded-linux.html#configuring-a-specifi > c-device That's for in

Re: [Development] Using platform-native APIs for terminating QThreads

Em terça-feira, 6 de setembro de 2016, às 16:08:59 PDT, Viktor Engelmann escreveu: > It is just a (more extreme) example of my point: > > If the user bypasses our security measures and shoots himself in the > foot - why should we take any responsibility for that? The problem here is that you wen

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

It kind of reminds me of this joke: http://www.ebaumsworld.com/jokes/blond-hole-diggers/80432143/ Do we have a policy about inappropriate content posted to mailing lists and similar communication channels? If not, I think we should agree on banning at least some basic things like racism or s

Re: [Development] Using platform-native APIs for terminating QThreads

It is just a (more extreme) example of my point: If the user bypasses our security measures and shoots himself in the foot - why should we take any responsibility for that? Am 06.09.2016 um 01:44 schrieb Thiago Macieira: > Em segunda-feira, 5 de setembro de 2016, às 16:08:41 PDT, Viktor Engelma

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

Using one "bin" is the default behavior, yes, but one can pass -hostprefix to separate them upon install. http://doc-snapshots.qt.io/qt5-5.8/embedded-linux.html#configuring-a-specific-device Cheers, Laszlo From: Development on behalf of Thiago Macieira Se

Re: [Development] A faster qUtf8Printable for static trace points?

Em segunda-feira, 5 de setembro de 2016, às 21:20:12 PDT, Milian Wolff escreveu: > Hey Thiago, others. Hey Milian Is this what you were looking for me for on Sunday afternoon? > bool QLibraryPrivate::load() > { > ... > TraceScope<...> ts(qUtf8Printable(fileName)) > ... > } Hmm... I

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

Em terça-feira, 6 de setembro de 2016, às 06:20:34 PDT, Thiago Macieira escreveu: > Building the host tools while cross-compiling is a convenience and I think > we can keep it, but I don't think we should simply have different "bin" > dirs. Fail in sentence rewrite. I wanted to write "don't thin

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

Am 06.09.2016 um 06:52 schrieb Ch'Gans: > On 6 September 2016 at 16:20, Thiago Macieira > wrote: >> Which is, in itself, an argument: why learn yet another buildsystem? > ... > > Why learn yet another programming language? > > ... > > An average software developer knows about, says 10 to 20 prog

Re: [Development] Notes on QtCore session @ QCS2016

Em terça-feira, 6 de setembro de 2016, às 07:24:19 PDT, Marc Mutz escreveu: > On Tuesday 06 September 2016 02:02:50 Thiago Macieira wrote: > > > https://codereview.qt-project.org/#/c/142782/ > > > > We decided to make a QUIP out of this, in a later session. Stay tuned. > > ENOABBREV It's a backr

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

Em terça-feira, 6 de setembro de 2016, às 16:52:47 PDT, Ch'Gans escreveu: > > Which is, in itself, an argument: why learn yet another buildsystem? > > Good question, maybe because it's more powerful, it fits better your > needs, it is more fun, it uses new concepts, ... > Or just out of curiosity!

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

Em terça-feira, 6 de setembro de 2016, às 11:46:12 PDT, Stephen Kelly via Development escreveu: > > Whenever you cross-compile Qt, you end up with tools that can only be run > > on the host. So Qt's cross-compilation mechanism can't be used to build > > tools that can be run on the target platform

Re: [Development] [FYI] on gerrit change retargeting requests

On Tuesday 06 September 2016 11:43:34 Oswald Buddenhagen wrote: > On Mon, Sep 05, 2016 at 09:17:59PM +, J-P Nurmi wrote: > > On 05 Sep 2016, at 19:27, Marc Mutz wrote: > > > It's not about restricting what a user can do. It's simply missing > > > implementation, and I believe that if it were e

Re: [Development] [FYI] on gerrit change retargeting requests

On 06 Sep 2016, at 11:46, Konstantin Tokarev wrote: > > > > 06.09.2016, 12:44, "Oswald Buddenhagen" : >>> On Mon, Sep 05, 2016 at 09:17:59PM +, J-P Nurmi wrote: >>> On 05 Sep 2016, at 19:27, Marc Mutz wrote: >>> > It's not about restricting what a user can do. It's simply missing >>> >

Re: [Development] [FYI] on gerrit change retargeting requests

06.09.2016, 12:44, "Oswald Buddenhagen" : > On Mon, Sep 05, 2016 at 09:17:59PM +, J-P Nurmi wrote: >>  On 05 Sep 2016, at 19:27, Marc Mutz wrote: >>  > It's not about restricting what a user can do. It's simply missing >>  > implementation, and I believe that if it were easy to implement, >>

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

On 06/09/16 02:13, Thiago Macieira wrote: Em segunda-feira, 5 de setembro de 2016, às 12:40:54 PDT, Stephen Kelly via Development escreveu: I think something was lost in transit on this point. I don’t think it would be a PITA to write a CMake buildsystem for Qt. I recall the above point was in

Re: [Development] [FYI] on gerrit change retargeting requests

On Mon, Sep 05, 2016 at 09:17:59PM +, J-P Nurmi wrote: > On 05 Sep 2016, at 19:27, Marc Mutz wrote: > > It's not about restricting what a user can do. It's simply missing > > implementation, and I believe that if it were easy to implement, > > Ossi would have done it long ago instead of playin

Re: [Development] CI/5.6: "Failed 7 times to aqcuire the hardware" (was: Fwd: Change in qt/qtbase[5.6]: qstrncpy: don't call strncpy_s with invalid parameters)

On torsdag 1. september 2016 15.22.29 CEST Marc Mutz wrote: > Hi, > > Twice in succession. > > Any idea what's happening? > > Thanks, > Marc Yes, more or less. vSphere is overloaded and it shows that it doesn't like it... Anyway write a bug report for it. Especially if you see it again. As for