Re: [Development] Proposing Samuel Gaist for approver status

+1 28.07.2018, 11:56, "André" : > Hello all, > > I'd like to propose Samuel as approver. He has been active in the Qt project > for ages. > > He not only provides code changes [0], he is also active reviewing others > changes [1]. > > But that's not all: Samuel is *extremly* active in the Qt

Re: [Development] QtCS 2018: Third-party and security policy

13.07.2018, 17:57, "Mårten Nordheim" : > On 13.07.2018 16:49, Lisandro Damián Nicanor Pérez Meyer wrote: >>  El viernes, 13 de julio de 2018 10:59:09 -03 Mårten Nordheim escribió: >>>  On 05.07.2018 16:48, Thiago Macieira wrote:  On Thursday, 5 July 2018 01:56:43 PDT Kai Koehne wrote: >

Re: [Development] Fornux C++ Superset

14.05.2018, 01:45, "Phil Bouchard" : > On 05/13/2018 06:35 PM, Alexander Nassian wrote: >>  OMFG, besides that these are not the most difficult problems in >> programming, ... that computer voice that just reads what the presentation >> says. Youtube Videos are not the

Re: [Development] Why waste energy supporting Python?

25.04.2018, 04:42, "d3fault" : > Supporting Python first class dilutes Qt, please don't. What's next, > Qt for Java? It's one thing to collect community-developed bindings > for various other languages into a single place... but something else > entirely to pay an entire

Re: [Development] Fornux C++ Superset

25.04.2018, 16:46, "Eric Lemanisser" : > What about > void foo(int ()[3]) > and > template > void foo(int ()[N]) ? > Both of these functions make sure the caller and the callee use the same > array size at compile time. I don't see anybody giving away this kind of >

Re: [Development] qdds image format

17.04.2018, 17:33, "Иван Комиссаров" : > At the point i wrote the plugin, my usecase was simple - to convert plain > QImages to and from DDS icons (used in starcraft2, which uses quite a few > formats DDS can handle). > But yes, i forgot floating point textures. > Compressed

Re: [Development] [Google Summer of Code] [Project Ideas] Qt Quick Controls 2 Sailfish Silica Style

09.04.2018, 16:51, "Fanda Vacek" <fanda.va...@volny.cz>: > On 04/06/2018 08:35 PM, Konstantin Tokarev wrote: >>  06.04.2018, 21:18, "Aleksey Kontsevich" <tantr...@ya.ru>: >>>  Hi all, >>> >>>  Only one argument. >>

Re: [Development] [Google Summer of Code] [Project Ideas] Qt Quick Controls 2 Sailfish Silica Style

06.04.2018, 21:18, "Aleksey Kontsevich" : > Hi all, > > Only one argument. > >> I don't see any point in moving this to QtProject as we don't have Sailfish >> OS platform upstreamed. > > Just let's not miss the moment when it become upstreamed. :-) Things move > very fast

Re: [Development] Nominating people from our release team for approver rights

16.03.2018, 14:44, "Frederik Gladhorn" : > Hello all, > > in 2014 we agreed to make the release team in The Qt Company approvers for the > Qt Project to enable them to work efficiently. > > Since then we had Aapo join the team. Aapo is working hard on improving Coin >

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

12.03.2018, 20:10, "Sérgio Martins" : > 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 is > someone you'll always want to add as

Re: [Development] Coin maintenance notification

27.02.2018, 16:42, "Aapo Keskimölö" : > Coin production was restarted today because it was failing connections to > Opennebula after it was restarted. > > Changelog: > > https://codereview.qt-project.org/#/c/221521/ This is not a public page which everyone here can open,

Re: [Development] [Qt-creator] Requesting repository for telemetry plugin in Qt Creator

23.02.2018, 13:55, "Edward Welbourne" : > André Pönitz (22 February 2018 20:05) >>  Any number for a "measured" value for rate of crashes or memory leaks >>  is uninteresting for me when I run into the problem myself reqularly. >>  And trust me, I do. > > I trust you. >

Re: [Development] [Qt-creator] Requesting repository for telemetry plugin in Qt Creator

22.02.2018, 16:39, "Ryein Goddard" : > This might be nice to make pretty charts to show to managers, but to be > completely honest I think it is 100% useless.  If you don't know what people > are using your software for, or how then you aren't communicating with them. 

Re: [Development] Suggestion: switch binary builds to OpenSSL 1.1 in Qt 5.11

13.02.2018, 14:09, "Edward Welbourne" : > On Friday, 9 February 2018 10:04:30 PST Giuseppe D'Angelo wrote: >>  The point isn't which version of Qt comes with the distribution, but the >>  binary builds. Given people do use binary builds (to have an up-to-date >>  Qt) but

Re: [Development] Suggestion: switch binary builds to OpenSSL 1.1 in Qt 5.11

09.02.2018, 18:57, "Thiago Macieira" : > On Friday, 9 February 2018 02:59:31 PST Giuseppe D'Angelo wrote: >>  OpenSUSE Leap 42.3 also has 1.0.2 [7]. > > This release is too old. It still has Qt 5.6. Note that people often work on old distros with new Qt, installed

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

09.02.2018, 16:48, "Konstantin Tokarev" <annu...@yandex.ru>: > 09.02.2018, 10:03, "Kevin Kofler" <kevin.kof...@chello.at>: >>  IMHO, you need to rethink your whole CI approach. This is increasingly being >>  the one bottleneck slowing down Qt d

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

09.02.2018, 10:03, "Kevin Kofler" : > IMHO, you need to rethink your whole CI approach. This is increasingly being > the one bottleneck slowing down Qt development and releases. It might make > more sense to try a different approach, such as allowing all commits through >

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

09.02.2018, 14:07, "Olivier Goffart" : > Am Freitag, 9. Februar 2018, 08:13:01 CET schrieb Thiago Macieira: >>  On Thursday, 8 February 2018 23:02:36 PST Kevin Kofler wrote: >>  > IMHO, you need to rethink your whole CI approach. This is increasingly >>  > being the one

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

08.02.2018, 11:17, "Lars Knoll" : >>  On 8 Feb 2018, at 08:35, Thiago Macieira wrote: >> >>  On Wednesday, 7 February 2018 19:32:25 PST Kevin Kofler wrote: >>>  We are now in early February. By your schedule, 5.11 will be out on the >>> last >>>  

Re: [Development] Deprecation of Qt Quick Controls 1

t; And basically the only thing that really hurts me with controls 2 is that > combobox becomes quite horrible > > On Wed, Feb 7, 2018 at 5:25 PM, Konstantin Tokarev <annu...@yandex.ru> wrote: > >> 07.02.2018, 16:13, "NIkolai Marchenko" <enmarantis...@gmail.co

Re: [Development] Deprecation of Qt Quick Controls 1

07.02.2018, 16:13, "NIkolai Marchenko" : > And no, widgets is not an alterlative to proper qml controls on desktop when > you want custom interface. > I have an app that uses qml to draw a custom listview for users, it would be > extremely hard to replicate it with

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

01.02.2018, 14:19, "Oswald Buddenhagen" : > On Tue, Jan 30, 2018 at 09:38:29PM +, Tuukka Turunen wrote: >>  The item that has received comments both in favor and against is what >>  to do with 5.10 now. I think that instead of closing 5.10, we could >>  move it to

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

29.01.2018, 16:33, "Kevin Kofler" : > Simon Hausmann wrote: >>  In the light of that, I think it would be better to keep the LTS branches >>  open longer and stop doing patch releases for minor releases that are not >>  LTS. > > -1 from a distro packager perspective. LTS

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

29.01.2018, 11:16, "Simon Hausmann" : > Hi, > > I feel that we are generally guiding our users towards the LTS releases. The > minor releases appear to address in particular users who need a particular > feature before it hits the next LTS release. > > In the light of

Re: [Development] Rebasing

26.01.2018, 18:14, "Igor Mironchik" : > Hi, > > What if you have a patch based on 5.11 branch and you want to rebase it > to 5.9, how do you do such work? Do you use regular git rebase? Or maybe > you just do a new branch based on 5.9, do changes, commit and changes >

Re: [Development] #pragma once

25.01.2018, 13:27, "Mathias Hasselmann" : > Let's see what people who know much more about compiler features than > any of us think about "#pragma once". Let's check what GCC and Clang do > for their C++ library headers: > >    $ grep -r pragma.*once

Re: [Development] #pragma once

24.01.2018, 17:09, "Thiago Macieira" <thiago.macie...@intel.com>: > On Wednesday, 24 January 2018 03:53:18 PST Konstantin Tokarev wrote: >>  That's said, if headers are never copied it's safer to use #pragma once than >>  include guards > > And you k

Re: [Development] #pragma once

24.01.2018, 14:33, "Jean-Michaël Celerier" : > I certainly have been bitten much more times by include guards that were the > same in different files (especially in old libraries where guards look like > #ifdef QUEUE_H because of course there is a single queue.h

Re: [Development] Using native webview on OS X

23.01.2018, 17:09, "Morten Sørvig" <morten.sor...@qt.io>: >>  On 22 Jan 2018, at 18:22, Alberto Mardegan <ma...@users.sourceforge.net> >> wrote: >> >>  On 22/01/2018 18:49, Konstantin Tokarev wrote: >>>  From [1] it seems like QT_MAC_U

Re: [Development] Using native webview on OS X

22.01.2018, 18:37, "Alberto Mardegan" : > Hi all! >   I've developed a desktop application which uses the WebView QML > module, with the hope of publishing it in the Apple store. However, > unless I am seriously mistaken, this is just not possible (or maybe the >

Re: [Development] how to include further changes while previous commit is still under review?

that it's not always possible to reorder sequential commits without conflicts > > martin > > ________ > From: Konstantin Tokarev <annu...@yandex.ru> > Sent: Monday, January 22, 2018 12:36:38 PM > To: Martin Smith; Daniel Savi; Samuel Gais

Re: [Development] how to include further changes while previous commit is still under review?

ng. In rebase -i menu don't reorder anything, instead mark commits for edit >> martin>> > From: Development <development-bounces+martin.smith=qt...@qt-project.org> on behalf of Konstantin Tokarev <annu...@yandex.ru>> Sent: Mond

Re: [Development] how to include further changes while previous commit is still under review?

eature branches". What I've suggested is a pragmatic shortcut, to avoid switching branches and therefore save a bit of time by avoid excessive file rewrites and following recompilation. > Am 20. Januar 2018 23:28:13 MEZ schrieb Konstantin Tokarev > <annu...@yandex.ru>: >> 2

Re: [Development] how to include further changes while previous commit is still under review?

21.01.2018, 01:25, "Daniel Savi" <daniel.s...@gaess.ch>: > On 19.01.2018 18:40, Konstantin Tokarev wrote: >>  19.01.2018, 01:58, "Samuel Gaist" <samuel.ga...@edeltech.ch>: >>>>    On 18 Jan 2018, at 22:42, Daniel Savi <daniel.s...@gaess.ch&

Re: [Development] how to include further changes while previous commit is still under review?

19.01.2018, 01:58, "Samuel Gaist" : >>  On 18 Jan 2018, at 22:42, Daniel Savi wrote: >> >>  Hello qt devs >> >>  I'm back with another newbie question. I have committed a patch that is >> still under review on gerrit. >> >>  Meanwhile, I've got a

Re: [Development] Setters: Clarifying the ownership

19.01.2018, 20:07, "Adam Treat" : > How about "transfer" Why not just use move semantics of language instead of inventing new terms? > > On 01/19/2018 11:57 AM, Thiago Macieira wrote: >>  On sexta-feira, 19 de janeiro de 2018 08:26:21 PST Philippe wrote: >>>  +20 years ago,

Re: [Development] Setters: Clarifying the ownership

19.01.2018, 18:16, "Jesus Fernandez" : > Hi all! > > I always found something annoying in the Qt API. The problem comes with the > setters of our properties. When I want to pass an object to a property I > never know if I need to take care of the object or relay on

Re: [Development] QHash

18.01.2018, 17:13, "René J.V. Bertin" : > Hi, > > It took me a while to figure out why my QHash map of a const char* to > something else didn't work despite containing the expected key,value > combinations. I understand that the bug was in my code rather than in QHash, >

Re: [Development] QtCoap: QNAM-like API or not

18.01.2018, 12:58, "Adrien LERAVAT" <alera...@witekio.com>: >>  From: Konstantin Tokarev [mailto:annu...@yandex.ru] >>  Sent: Thursday, January 18, 2018 10:42 AM >> >>>   The API sounds interesting, but it's a departure of what we are used in >>

Re: [Development] QtCoap: QNAM-like API or not

14.01.2018, 20:50, "Adrien LERAVAT" : > Hi all, > > Before feature freeze, we wanted to challenge the current API for the CoAP > module. > > It is currently similar to QNAM APIs: > > \code > > QCoapClient client; > > QCoapReply *reply = client.get(QUrl("1.2.3.4:5683")); >

Re: [Development] QtCoap: QNAM-like API or not

18.01.2018, 12:35, "Adrien LERAVAT" : > On Sunday 14 January 2018 17:49:48 Adrien LERAVAT wrote: >>  > In that case, the QCoapReply life is managed with a >>  > QSharedPointer in the request. >>  > >>  > QCoapRequest does not inherit from QObject. Anyone sees a problem with

Re: [Development] Undeprecating QString::null

16.01.2018, 19:18, "Uwe Rathmann" : > On Tue, 16 Jan 2018 16:47:57 +0100, Olivier Goffart wrote: > >>  Just change your code to use "= QString()", no #ifdef necessary. > > The "just change" introduces a binary incompatibility - right ? > > Please be aware, that Qwt is

Re: [Development] Repository request: Qt Notifier

16.01.2018, 17:46, "Shawn Rutledge" <shawn.rutle...@qt.io>: >>  On 16 Jan 2018, at 15:18, Konstantin Tokarev <annu...@yandex.ru> wrote: >> >>  Is cloud aspect so principal? Can there be "non-cloud" backend which just >> uses persistent

Re: [Development] Repository request: Qt Notifier

16.01.2018, 17:05, "Shawn Rutledge" : >>  On 16 Jan 2018, at 14:49, Kari Oikarinen wrote: >> >>  On 15.01.2018 17:25, Ryan Chu wrote: >>>  Hi all, >>>  I'm working on a task supporting "Push Notification" for Qt applications. >>> This feature will be

Re: [Development] Coin, Boot2Qt, and OE_QMAKE_PATH_HOST_BINS variable

09.01.2018, 17:32, "Samuli Piippo" <samuli.pii...@qt.io>: > On 09.01.2018 12:27, Konstantin Tokarev wrote: >>  Hello, >> >>  I've tried to enable cross-compilation in Coin for QtWebKit 5.212 to improve >>  platform coverage in each build, however I'v

Re: [Development] Coin, Boot2Qt, and OE_QMAKE_PATH_HOST_BINS variable

09.01.2018, 17:32, "Samuli Piippo" <samuli.pii...@qt.io>: > On 09.01.2018 12:27, Konstantin Tokarev wrote: >>  Hello, >> >>  I've tried to enable cross-compilation in Coin for QtWebKit 5.212 to improve >>  platform coverage in each build, however I'v

[Development] Coin, Boot2Qt, and OE_QMAKE_PATH_HOST_BINS variable

Hello, I've tried to enable cross-compilation in Coin for QtWebKit 5.212 to improve platform coverage in each build, however I've faced following problem. Our Linux cross-compilation platform is Boot2Qt which is based on meta-qt5 Yocto layer. QtWebKit uses CMake internally, and Qt cmake config

Re: [Development] [Qt-creator] [FYI] the new way to retarget gerrit changes

08.01.2018, 16:51, "Orgad Shaneh" <org...@gmail.com>: > On Mon, Jan 8, 2018 at 3:48 PM, Konstantin Tokarev <annu...@yandex.ru> wrote: > >> 08.01.2018, 16:40, "Oswald Buddenhagen" <oswald.buddenha...@qt.io>: >>> On Mon, Sep 12, 2016 at 0

Re: [Development] [Qt-creator] [FYI] the new way to retarget gerrit changes

08.01.2018, 16:40, "Oswald Buddenhagen" : > On Mon, Sep 12, 2016 at 02:39:57PM +0300, Orgad Shaneh wrote: >> Either extend the sanity bot, or create a new bot, which listens on >> gerrit's event stream. >> If the change's owner (or an approver?) posts a

Re: [Development] About the presence of /System/Library/Frameworks/Carbon.framework

er /System/Library/Frameworks onto said >>>>  Linux rig because I use it for cross-platform development. >>>> >>>>  Apart from the fact that it should probably check for a framework with a >>>>  more certain future, isn't there a less "rootsy" way of

Re: [Development] Pushing with the same change id to the another branch.

> Hello, > > I pushed a change for code review into the 5.10 branch. But this patch > can't be merged into 5.10 branch since this is behavior change. Now I > want to push the same change (commit) into dev branch. So my question is > it possible to do just: > > git push gerrit HEAD:refs/for/dev

Re: [Development] about the Cocoa/Freetype fontengine

31.12.2017, 03:11, "Nikolaus Waxweiler" : >>>  We want to get to "Gamma 1.8, darkenend": >>>  https://www.freetype.org/image/BlendingExamples.png >> >>  On Mac (FT and/or FT+FC *without* Infinality+Ultimate patches) I >>  find 1.5 comes closer to the native CoreText font

Re: [Development] 32bit linux build of qt5.10.0 w/ webengine

22.12.2017, 15:26, "Thiago Macieira" : > On quinta-feira, 21 de dezembro de 2017 22:00:26 -02 Kevin Kofler wrote: >>  Thiago Macieira wrote: >>  > To build? At least 8 GB of RAM and please use a 64-bit toolchain. You may >>  > compile for 32-bit, but you need to use a

Re: [Development] Reporting errors for powershell scripts executed by Coin

B is fixed already, however one VM snapshot had to be manually removed for re-provisioning > > -T > > -Original Message- > From: Development > [mailto:development-bounces+tony.sarajarvi=qt...@qt-project.org] On Behalf Of > Konstantin Tokarev > Sent: torstai 21.

[Development] Reporting errors for powershell scripts executed by Coin

Hi all, AFAIU, some time ago Coin considered ps1 script to be failed its exit code was non-null (e.g, Exit(1) certainly aborted further provisioning process). Now I see that Exit(1) is ignored (see [1]). What is the correct way now, throw exception? [1]

Re: [Development] About the presence of /System/Library/Frameworks/Carbon.framework

21.12.2017, 19:53, "René J.V. Bertin" : > On Thursday December 21 2017 16:25:02 Jake Petroules wrote: > >>  > Possibly: just `uname` returns Darwin. That should certainly work for the >> desktop OS, but I have no way of checking what it returns on other Apple OSes >> >>  

Re: [Development] About the presence of /System/Library/Frameworks/Carbon.framework

> Hi, > > Here's a silly one: configuring Qt for building on my Linux rig I was told > that I needed Xcode, and how to get it. :) > > Long story short, it turns out that the configure script determines whether > it's building on Mac by checking if the Carbon framework exists in the >

Re: [Development] Weird issue in CI

> On onsdag 20. desember 2017 17.00.18 CET Konstantin Tokarev wrote: > >> I'm repeatedly getting this error: >> >> Failed to provision template 'qtci-linux-Ubuntu-16.04-x86_64-1-b46ac1': >> Failed repeatedly to launch build/test agent > > This means it

[Development] Weird issue in CI

I'm repeatedly getting this error: Failed to provision template 'qtci-linux-Ubuntu-16.04-x86_64-1-b46ac1': Failed repeatedly to launch build/test agent Details: https://testresults.qt.io/coin/integration/qt/qtwebkit/tasks/1513784851 No log exist. -- Regards, Konstantin

Re: [Development] Proposal to remove QNX 6.6 support from Qt 5.11 onwards

15.12.2017, 22:04, "Tuukka Turunen" : > Hi, > > I propose to remove support for QNX 6.6 from Qt 5.11 onwards. > > Since Qt 5.9.0 we have supported both QNX 6.6 and 7.0, but going forward we > would support only QNX 7.0 with new Qt versions. QNX 6.6 continues to be >

Re: [Development] How fast grab a QML item's content to image when it updates?

12.12.2017, 16:53, "Denis Shienkov" <denis.shien...@gmail.com>: >  > Did you try QQuickItem::grabToImage? > > Of course, it is veeery slowly. I guess your best bet then is hardware grabbing video output > > 12.12.2017 16:40, Konstantin Tokarev пишет: >

Re: [Development] How fast grab a QML item's content to image when it updates?

12.12.2017, 16:13, "Denis Shienkov" : > Hi all... > > Is it possible to grab a QQuickItem content (e.g. with all sub-items) > when an item changes? Did you try QQuickItem::grabToImage? > > E.g. with widgets I use the following code: > > bool MyWidget::event(QEvent

Re: [Development] Suggestion to add labels when changing API

08.12.2017, 22:53, "Adam Treat" : > On 12/08/2017 12:47 PM, Sergio Ahumada wrote: >>  On 08.12.2017 16:50, Oswald Buddenhagen wrote: >>>  On Fri, Dec 08, 2017 at 04:15:10PM +0100, Sergio Ahumada wrote:  On 08.12.2017 15:42, Adam Treat wrote: >  Relying upon qt5

Re: [Development] Suggestion to add labels when changing API

08.12.2017, 18:50, "Oswald Buddenhagen" : > On Fri, Dec 08, 2017 at 04:15:10PM +0100, Sergio Ahumada wrote: >>  On 08.12.2017 15:42, Adam Treat wrote: >>  > Relying upon qt5 submodule pins is the problem. The underlying issue is >>  > atomicity of commits. Oswald is

Re: [Development] Suggestion to add labels when changing API

08.12.2017, 17:14, "Tor Arne Vestbø" : > On 08/12/2017 14:54, Sergio Ahumada wrote: >>  an old concept that used to pin the sha1 of repo/module's dependency, eg >> >>   >>

Re: [Development] QtCS 2017 QtCore sessions

04.12.2017, 17:31, "Ville Voutilainen" : > On 4 December 2017 at 16:20, Allan Sandfeld Jensen wrote: >>  On Montag, 4. Dezember 2017 15:00:53 CET Marc Mutz wrote: >>>  Ah, well, yes. Nothing truly originates in C++, true. But, IIRC, the >>>  

Re: [Development] QtCS 2017 QtCore sessions

>> . I would be fine having the same developer experience in C++ > > even if I had to change name spaces and includes, but doesn't seem usual > > practice in C++. > > uh... ? I have been polyfilling optional, string_view, any, and variant for > almost three years with boost, or

Re: [Development] Urgent: Qt 5.9.3 binaries built with too NEW Linux distribution

> Is there any plans for an out-of-schedule update about this (if plan exists > at all =), as I have to deliver something end of next week, so if it’s not > going to happen next week I have to start making steps to rebuild things > myself. Even if 5.9.3 is be rebuilt and new binaries are

Re: [Development] Urgent: Qt 5.9.3 binaries built with too NEW Linux distribution

01.12.2017, 12:54, "Yuri Alexandrov" : > Am I right then thinking that only way to make 5.9.3 works on RH6 is to > rebuild from sources as online installer is not working there due to glibc > issues? Same should be true for all previous releases starting from 5.8.0, as all

Re: [Development] Urgent: Qt 5.9.3 binaries built with too NEW Linux distribution

30.11.2017, 20:47, "Thiago Macieira" : > See https://bugreports.qt.io/browse/QTBUG-64820 and > http://lists.qt-project.org/pipermail/interest/2017-November/028766.html > > The Qt 5.9.3 binaries were compiled by GCC 6, which is too new for the latest > Ubuntu LTS

Re: [Development] [Offtopic] QtCS 2017 QtCore sessions

30.11.2017, 17:05, "Marc Mutz" : > On 2017-10-10 14:49, Thiago Macieira wrote: > [...] >>  * We think members are cleaner and we don't want to add these > > You have members where members are possible. > But you can't add members to char16_t[]! Just in case somebody didn't

Re: [Development] Any supported platforms not tested in CI?

14.11.2017, 11:28, "Tuukka Turunen" : > For some platforms we test compilation only. Also some tests/combinations are > only run with full qt5.git integration. > > More information in wiki: https://wiki.qt.io/Qt_5.9_Tools_and_Versions See also coin/platform_configs

Re: [Development] Any supported platforms not tested in CI?

14.11.2017, 11:28, "Tuukka Turunen" : > For some platforms we test compilation only. Also some tests/combinations are > only run with full qt5.git integration. > > More information in wiki: https://wiki.qt.io/Qt_5.9_Tools_and_Versions See also coin/platform_configs

Re: [Development] Qt 5.10 beta 3 released

09.11.2017, 00:20, "Thiago Macieira" : > On Wednesday, 8 November 2017 12:54:16 PST Mat Sutcliffe wrote: >>  OK, thanks anyway. I remember this discussion: >>  http://lists.qt-project.org/pipermail/development/2017-April/029762.html >> >>  That seemed to conclude that

Re: [Development] QtCS 2017 QtCore sessions

t second thought (it's just a compiler warning, who looks at them after all), so using unsigned may increase number of bugs on user side. > > Philippe > > On Wed, 01 Nov 2017 18:25:01 +0300 > Konstantin Tokarev <annu...@yandex.ru> wrote: > >>  01.11.2017, 18:21, "Thi

Re: [Development] QtCS 2017 QtCore sessions

01.11.2017, 18:46, "Thiago Macieira" <thiago.macie...@intel.com>: > On quarta-feira, 1 de novembro de 2017 08:25:01 PDT Konstantin Tokarev wrote: >>  > No, not really, since it's already limited to half the full VM space. No >>  > object can be larger tha

Re: [Development] QtCS 2017 QtCore sessions

01.11.2017, 18:21, "Thiago Macieira" : > On quarta-feira, 1 de novembro de 2017 05:23:04 PDT Иван Комиссаров wrote: >>  Sorry for digging the thread, but how is >>  * use qssize_t >>  and >>  ** Wrapping std::{unordered_}map may be acceptable >>   combines? >>  

Re: [Development] QtCS 2017 QtCore sessions

01.11.2017, 15:30, "Philippe" : > And offtop - what about allocators? They would be accesibble for wrappers, > but not accesible for QVector/QString? > > Something sure, a Qt6 feature such as std::pmr::memory_resource (cf. > https://www.youtube.com/watch?v=v3dz-AKOVL8)

Re: [Development] Getting build flags for platforms without pkg-config

30.10.2017, 22:11, "Thiago Macieira" <thiago.macie...@intel.com>: > On segunda-feira, 30 de outubro de 2017 11:20:25 PDT Konstantin Tokarev wrote: >>  > As for MSVC, the issue will be similar: teaching pkg-config about the MSVC >>  > linker syntax. Hint:

Re: [Development] Getting build flags for platforms without pkg-config

31.10.2017, 01:03, "Konstantin Tokarev" <annu...@yandex.ru>: > 31.10.2017, 00:56, "Thiago Macieira" <thiago.macie...@intel.com>: >>  On segunda-feira, 30 de outubro de 2017 09:46:42 PDT jeandet wrote: >>>   > AFAIK there no technical reas

Re: [Development] Getting build flags for platforms without pkg-config

31.10.2017, 00:56, "Thiago Macieira" : > On segunda-feira, 30 de outubro de 2017 09:46:42 PDT jeandet wrote: >>  > AFAIK there no technical reason why providing .pc files for MSVC and >>  > macOS >>  > frameworks would be impossible. >> >>  I agree, I would add that

Re: [Development] Getting build flags for platforms without pkg-config

30.10.2017, 21:11, "Thiago Macieira" <thiago.macie...@intel.com>: > On segunda-feira, 30 de outubro de 2017 09:11:39 PDT Konstantin Tokarev wrote: >>  AFAIK there no technical reason why providing .pc files for MSVC and macOS >>  frameworks would be impos

Re: [Development] Getting build flags for platforms without pkg-config

30.10.2017, 18:53, "Konstantin Tokarev" <annu...@yandex.ru>: > 30.10.2017, 18:43, "Thiago Macieira" <thiago.macie...@intel.com>: >>  On segunda-feira, 30 de outubro de 2017 08:27:02 PDT Konstantin Tokarev >> wrote: >>>   >> $ cmake

Re: [Development] Getting build flags for platforms without pkg-config

30.10.2017, 18:43, "Thiago Macieira" <thiago.macie...@intel.com>: > On segunda-feira, 30 de outubro de 2017 08:27:02 PDT Konstantin Tokarev wrote: >>  >> $ cmake --find-package -DNAME=Qt5Core -DCOMPILER_ID=GNU -DLANGUAGE=CXX >>  >> -DMODE=COMPILE >&g

Re: [Development] Getting build flags for platforms without pkg-config

30.10.2017, 18:23, "Thiago Macieira" : > On segunda-feira, 30 de outubro de 2017 05:22:00 PDT Aleix Pol wrote: >>  $ cmake --find-package -DNAME=Qt5Core -DCOMPILER_ID=GNU -DLANGUAGE=CXX >>  -DMODE=COMPILE >>  -I/home/apol/devel/kde5/include/ >>  

Re: [Development] Repository request: MaterialWidgets

30.10.2017, 17:18, "iman ahmadvand" : > Well. > If it's OK to add new classes then we can create our classes And do the style > related things in private part until Qt6 release, on that time we can move > our changes to QStyle API. > And also in this way the application

Re: [Development] Getting defines from pkg-config for Qt modules

26.10.2017, 20:20, "Jeandet Alexis" : > Hello, > > I already asked this on IRC but I got no answer. > On Fedora and Ubuntu I can say that "pkg-config --cflags Qt5[any module]" > does only provides include flags and no defines such as -DQT_CORE_LIB or >

Re: [Development] Any supported platforms not tested in CI?

20.10.2017, 18:14, "Thiago Macieira" <thiago.macie...@intel.com>: > On Friday, 20 October 2017 07:09:26 PDT Konstantin Tokarev wrote: >>  I've found this on Intel side: >> >>  https://software.intel.com/en-us/node/628867 >> >>  I hope Thiago

Re: [Development] Any supported platforms not tested in CI?

20.10.2017, 17:03, "Ville Voutilainen" <ville.voutilai...@gmail.com>: > On 20 October 2017 at 16:59, Konstantin Tokarev <annu...@yandex.ru> wrote: >>  20.10.2017, 16:55, "Dmitry Shachnev" <mitya57...@gmail.com>: >>>  On Wed,

Re: [Development] Any supported platforms not tested in CI?

20.10.2017, 16:55, "Dmitry Shachnev" : > On Wed, Oct 11, 2017 at 01:23:58PM +0200, Thiago Macieira wrote: >>  Are there any supported platforms that we do not test in the CI? Probably >>  INTEGRITY? >> >>  [...] >> >>  So the question is: are there any platforms that could

Re: [Development] Qt with sanitizers

18.10.2017, 12:03, "Jedrzej Nowacki" : > Hi, > >   I made an experiment to see if we should enable sanitizers in CI, by > default. Essentially, how much we would slow down integrations and what would > be the tests pass rate. Short answer is that, currently, it is not an

Re: [Development] Future of QBS

17.10.2017, 17:26, "Matthew Woehlke" <mwoehlke.fl...@gmail.com>: > On 2017-10-16 22:05, Kevin Kofler wrote: >>  Konstantin Tokarev wrote: >>>  I have no real experience with Meson, but at least it has following >>>  advantages: >>> >>>

Re: [Development] Speeding up the review process (was: PostgreSQL cross compile for Pi)

17.10.2017, 16:10, "Kai Koehne" : >>  -Original Message- >>  From: Development [mailto:development-bounces+kai.koehne=qt.io@qt- >>  project.org] On Behalf Of Martin Smith >>  [...] >>  I am a member of the Qt documentation team, and I am often included as a >>  reviewer

Re: [Development] Speeding up the review process (was: PostgreSQL cross compile for Pi)

17.10.2017, 10:17, "Martin Smith" : > +1 > > I am a member of the Qt documentation team, and I am often included as a > reviewer for code changes that also include changes to qdoc comments. I > always assume I am meant to review only the documentation, so if the >

Re: [Development] Review for new widget module [your advices are needed]

17.10.2017, 15:05, "Shawn Rutledge" : >>  On 14 Oct 2017, at 09:33, iman ahmadvand wrote: >> >>  Hi everyone. >> >>  Before I send some code base on codereview and decide whether my >> implementation meets the requirements, I just want to know your

Re: [Development] Future of QBS

17.10.2017, 12:49, "Konstantin Tokarev" <annu...@yandex.ru>: > 17.10.2017, 05:06, "Kevin Kofler" <kevin.kof...@chello.at>: >>>   * Its language has native support for properties, with syntax that really >>>   looks like properties in ano

Re: [Development] Future of QBS

17.10.2017, 05:20, "Kevin Kofler" <kevin.kof...@chello.at>: > PS: Oh, and I forgot: > > Konstantin Tokarev wrote: >>  [Meson] is written in scripting language > > In addition to what I already wrote, this also implies that the scripting > language (Pyth

Re: [Development] Future of QBS

17.10.2017, 04:01, "Kevin Kofler" <kevin.kof...@chello.at>: > Konstantin Tokarev wrote: >>  This problem is solved by having access to full "project" model from the >>  same language. E.g. this is how I implemented Premake plugin for Qt >>  

Re: [Development] Future of QBS

17.10.2017, 05:06, "Kevin Kofler" <kevin.kof...@chello.at>: > Konstantin Tokarev wrote: >>  I have no real experience with Meson, but at least it has following >>  advantages: >> >>  * Its language is typed(!), > > CMake also has a concept

Re: [Development] Future of QBS

16.10.2017, 19:02, "jeandet" <alexis.jean...@member.fsf.org>: > Le lundi 16 octobre 2017 à 15:46 +0300, Konstantin Tokarev a écrit : >>  That said, I totally dislike the idea of inventing restricted DSL >>  language for build system >>  instead of using gener

<    1   2   3   4   5   6   7   >