Re: [Development] Changes to Qt offering

On Thu, 30 Jan 2020 at 13:01, Oswald Buddenhagen wrote: > > On Wed, Jan 29, 2020 at 11:40:46PM +0100, Filippo Cucchetto wrote: > >Maybe you didn't get it but i meant to both put a reasonable price for > >a commercial license (500$) and turning everything GPL or commercial. > >Making everything

Re: [Development] Changes to Qt offering

On Tue, 28 Jan 2020, 20:50 Thiago Macieira, wrote: > On Monday, 27 January 2020 22:37:47 PST Benjamin TERRIER wrote: > > You might have missed the info because it is in the blog post, but not in > > Lars email: > > > > There will be no more open source offline installer. > > Thanks, I stand

Re: [Development] Supported compilers for Qt 6

On Mon, 12 Aug 2019, 22:13 Thiago Macieira, wrote: > On Monday, 12 August 2019 13:03:47 PDT Mutz, Marc via Development wrote: > > The milestone is std::byte, which which we could put QByteArray on a > > sound basis. And char8_t, which would make QUtf8String(View) fly. > > QByteArray, due to its

Re: [Development] Supported compilers for Qt 6

On Mon, 12 Aug 2019, 21:37 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? > Clang 8 AFAIK, and let's not forget about their push of libc++ (Vs gnu

Re: [Development] Qt PDF as a new TP module for Qt 5.14

On Mon, 12 Aug 2019, 20:23 Konstantin Tokarev, wrote: > > > 12.08.2019, 21:01, "Thiago Macieira" : > > On Monday, 12 August 2019 08:24:05 PDT Konstantin Tokarev wrote: > >> I guess bigger problem is that Poppler is GPL. PDFium is probably the > only > >> permissively licensed PDF engine. > > >

[Development] Gerrit very slow?

Hi there, Is it just me or code-review.qt-project.org is very slow? I have no problem with other web sites, but code-review keeps timing out? Anyone else has the same problem? Chris ___ Development mailing list Development@qt-project.org

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

On Tue, 18 Jun 2019 at 20:24, Kevin Kofler wrote: > > Christian Gagneraud wrote: > > Please elaborate:https://gcc.gnu.org/install/configure.html > > > > Just from the top of the document: > > --with-pkgversion > > --with-bugurl > > ...

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

On Tue, 18 Jun 2019 at 13:16, Kevin Kofler wrote: > > Christian Gagneraud wrote: > > with/without tells the system to use a thing or not. > > enable/disable tells the system to enable/disable the thing feature. > > The problem is that typical build options are actually

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

On Tue, 18 Jun 2019 at 11:16, Kevin Kofler wrote: > > Konstantin Tokarev wrote: > > Autotools provide human-readable options of standardized format > > > > --with-thing > > --without-thing > > --enable-thing > > --disable-thing > > That's already 2 different standards for essentially the same

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

On Tue, 18 Jun 2019 at 00:27, Christian Gagneraud wrote: > > On Mon, 17 Jun 2019 at 23:06, Jean-Michaël Celerier > wrote: > > > > > The world is not spinning around Qt, sorry for the bad news. > > > > On that we agree : https://www.jetbrains.com/lp/devecosyste

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

On Mon, 17 Jun 2019 at 23:06, Jean-Michaël Celerier wrote: > > > The world is not spinning around Qt, sorry for the bad news. > > On that we agree : https://www.jetbrains.com/lp/devecosystem-2019/cpp/ > I mean, I had actual CMake classes with a CMake exam on paper 6 years ago at > the university

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

On Mon, 17 Jun 2019, 21:13 Konstantin Tokarev, wrote: > > > 17.06.2019, 12:07, "Christian Gagneraud" : > > On Mon, 17 Jun 2019, 20:15 Elvis Stansvik, wrote: > >> Den mån 17 juni 2019 kl 09:12 skrev Christian Gagneraud < > chg...@gmail.com>: > >&g

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

On Mon, 17 Jun 2019, 20:15 Elvis Stansvik, wrote: > Den mån 17 juni 2019 kl 09:12 skrev Christian Gagneraud >: > > > > On Mon, 17 Jun 2019, 18:11 Jedrzej Nowacki, > wrote: > >> > >> On Saturday, June 15, 2019 6:37:24 PM CEST Thiago Macieira wrote: > &

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

On Mon, 17 Jun 2019, 18:11 Jedrzej Nowacki, wrote: > On Saturday, June 15, 2019 6:37:24 PM CEST Thiago Macieira wrote: > > On Saturday, 15 June 2019 02:18:28 PDT Jean-Michaël Celerier wrote: > > > You can download a CMake static binary (https://cmake.org/download/) > that > > > > (...) > > > > I

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

On Fri, 7 Jun 2019 at 03:31, Alexandru Croitor wrote: > On 6. Jun 2019, at 16:48, Christian Gagneraud wrote: > On Fri, 7 Jun 2019 at 02:25, Simon Hausmann wrote: > Am 06.06.19 um 16:17 schrieb Christian Gagneraud: > On Fri, 7 Jun 2019 at 02:08, Simon Hausmann wrote: > Am 06

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

On Thu, 6 Jun 2019 at 23:46, Simon Hausmann wrote: > > 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 > current state can be

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

On Fri, 7 Jun 2019 at 02:25, Simon Hausmann wrote: > > > Am 06.06.19 um 16:17 schrieb Christian Gagneraud: > > On Fri, 7 Jun 2019 at 02:08, Simon Hausmann wrote: > >> > >> Am 06.06.19 um 15:52 schrieb Christian Gagneraud: > >>> On Fri, 7 Ju

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

On Fri, 7 Jun 2019 at 02:08, Simon Hausmann wrote: > > > Am 06.06.19 um 15:52 schrieb Christian Gagneraud: > > On Fri, 7 Jun 2019 at 01:35, Bogdan Vatra via Development > > wrote: > >> Hi, > >> > >> I won't hold my breath for community support

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

On Fri, 7 Jun 2019 at 01:35, Bogdan Vatra via Development wrote: > > Hi, > > I won't hold my breath for community support for iOS. iOS is out for so many > years, yet CMake has no support for t. > > iOs is not a show stopper if and only you're prepared to drop this plaform > from Qt 6 in case

Re: [Development] FP calculations and stability in Qt

On Mon, 13 May 2019 at 07:47, Konstantin Shegunov wrote: > > Thanks for chiming in, I do appreciate the thoughts. > > On Sun, May 12, 2019 at 1:49 PM Christian Gagneraud wrote: >> >> I use to think that Qt could do a better job about FP >> precision/stabilit

Re: [Development] FP calculations and stability in Qt

On Sun, 12 May 2019 at 20:26, Konstantin Shegunov wrote: > > Hi, > I'd want to clear the context out of the way, so this is the bug[1] that got > me thinking. > I appreciate that we want to keep external dependencies to a minimum, and for > a good reason, but can we talk about how feasible it

Re: [Development] QtWebEngine file path too long

On Tue, 12 Mar 2019 at 23:45, Samuel Gaist wrote: > > Hi, > > I’ve been hit by this surprising error when building QtWebEngine. I had this issue too, i fixed it by patching chromium build system, see attached patch (i'm not the author and i don't have the original url). This was with Qt-5.11,

Re: [Development] nmake qtcreator from source failed

On Mon, 25 Feb 2019 17:58 mirchd, wrote: > Hello, > You'll have better luck on qt creator mailing list, as it seems you're trying to build it. It might help to give qtc version along compiler/os env and version. Chris > it says, > -- > link /NOLOGO /DYNAMICBASE /NXCOMPAT /DEBUG /DLL

[Development] Mailing list archive annoyance

Hi all, I do not know what is going on with the mailing list archive, but this is getting frustrating. Trying to move forward and keep positive, i would like to report on a(nother) use case here: https://bugreports.qt.io/browse/QTBUG-71225 This bug report starts with a couple of links to the Qt

Re: [Development] Build system for Qt 6

> >> system, just write a dockerscript that does your cross-compile job. > > Christian Gagneraud (17 December 2018 13:50) > > What do you mean by 'everywhere'? Native Windows dockers are still > > experimental, and i haven't heard of native MacOS docker yet (might > > have mi

Re: [Development] Build system for Qt 6

On Mon, 17 Dec 2018 at 21:43, Jean-Michaël Celerier wrote: > > CMake doesn't support (very well) cross-compilation for android on > > Windows for example, > > fairly interesting considering that Android Studio uses CMake: > https://developer.android.com/studio/projects/add-native-code Fairly

Re: [Development] Build system for Qt 6

On Mon, 17 Dec 2018 at 17:53, Ray Donnelly wrote: > On Sun, Dec 16, 2018, 10:36 PM Richard Weickelt > The discussion about build systems reminds me a bit of a religious war. I >> made my peace with CMake and use it only when being paid for. It allows me >> to use the browser more often and to

Re: [Development] Build system for Qt 6

On Mon, 17 Dec 2018 at 18:38, Thiago Macieira wrote: > > On Sunday, 16 December 2018 20:12:47 PST Richard Weickelt wrote: > > ... and if you cross-compile, you definetly don't want to your build system > > to stick its nose into your system librararies on any platform. > > No, you really DO. The

Re: [Development] CMake && QtCreator cross-compilation for ARM fails

On Sat, 15 Dec 2018 at 01:59, Kevin Kofler wrote: > >> This is a bug that was already fixed by: > >> https://gitlab.kitware.com/cmake/cmake/merge_requests/2668 > > > > Apparently it will make it into 3.14, in 2 months. > > It's a bummer to have to maintain a work around, or should i add cmake > >

Re: [Development] Remove artemis_poo...@aol.com from list (spammer)

On Sat, 15 Dec 2018 at 05:19, Jason H wrote: > > I request removal of artemis_poo...@aol.com for spam. Email can be forwarded > to the appropriate party. > Have others gotten a direct reply? Yes, i have received 4 phishing attempts from this email. Chris

Re: [Development] CMake && QtCreator cross-compilation for ARM fails

On Fri, 14 Dec 2018 at 00:54, Kevin Kofler wrote: > This is a bug that was already fixed by: > https://gitlab.kitware.com/cmake/cmake/merge_requests/2668 Apparently it will make it into 3.14, in 2 months. It's a bummer to have to maintain a work around, or should i add cmake to my toolkit, so

Re: [Development] CMake && QtCreator cross-compilation for ARM fails

Hi Kevin, On Fri, 14 Dec 2018 at 00:54, Kevin Kofler wrote: > Bootstrapping QMake has always been the least pleasant part of the Qt build > process. Yes, i think we all agree on that one. > I am looking forward to this bootstrapping hack going away by just using > CMake. So you want to

Re: [Development] CMake && QtCreator cross-compilation for ARM fails

On Thu, 13 Dec 2018 at 12:27, Kevin Kofler wrote: Hi Kevin, > > PS: WTF? Why the Qt's management choosed the CMake's instead of QBS? > > Because CMake is a widespread tool written in C++/STL Some people are scared of the wolf, i'm scared of the sheepple. > (so, unlike QBS, it > does not depend

Re: [Development] Who is in charge of qt-project.org?

> I was told, there's a qbs.io or something going on? Wow, kudo to whoever, qbs.io redirects to doc.qt.io/qbs Chris ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Who is in charge of qt-project.org?

On Sat, 3 Nov 2018 at 01:15, Martin Smith wrote: > > >You've just dropped Qbs, what's next? > >I don't trust you anymore, nor the company-ies you represent - Nothing > >personal. > >I think that it is time for the qt-project.org domain to be handed > >back to the Qt Project community. > > But

Re: [Development] Who is in charge of qt-project.org?

On Fri, 2 Nov 2018 at 23:55, Lars Knoll wrote: > > > On 2 Nov 2018, at 11:45, Christian Gagneraud wrote: > > On Thu, 1 Nov 2018 at 22:25, Kain Vampire via Development > wrote: > > > > Hi, > I have to apologise for my behaviour. While I still think Christia

Re: [Development] Who is in charge of qt-project.org?

On Thu, 1 Nov 2018 at 22:25, Kain Vampire via Development wrote: > > > Hi, > I have to apologise for my behaviour. While I still think Christian > Gagneraud's attack on the Qt company abilities was unfair and uncalled for, > it's not a justification for my actions. > Creating an hostile

Re: [Development] Who is in charge of qt-project.org?

On Thu, 1 Nov 2018 at 05:28, Kain Vampire via Development wrote: > > WHAT A TWAT! > > P.S. > > Yes, feel free to ban me, it was worth it. Was it? You could have used the word 'idiot', at least it is not an insult to the feminine gender. You could have as well quoted which part of the message

Re: [Development] Who is in charge of qt-project.org?

g, so please hand it over to the community. Chris > > Andy > > Development på vegne av Christian Gagneraud > chg...@gmail.com> skrev følgende den 31.10.2018, 14:36: > > Hi, > > Can we have Qt mailing list archive back? > I believe it is tracked by >

[Development] Who is in charge of qt-project.org?

Hi, Can we have Qt mailing list archive back? I believe it is tracked by https://bugreports.qt.io/browse/QTWEBSITE-831 and as been going on for weeks. Can the "Qt Project Hosting Foundation" (from whois record) take care of that? What is going on? Chris

Re: [Development] Build system for Qt 6

On Wed, 31 Oct 2018 at 22:47, Christian Kandeler wrote: > > On Wed, 31 Oct 2018 10:44:43 +1300 > Christian Gagneraud wrote: > > > On Wed, 31 Oct 2018 at 10:27, Thiago Macieira > > wrote: > > > On Tuesday, 30 October 2018 13:56:45 PDT NIkolai Marchenk

Re: [Development] Build system for Qt 6

On Wed, 31 Oct 2018 at 11:08, Thiago Macieira wrote: > On Tuesday, 30 October 2018 14:44:43 PDT Christian Gagneraud wrote: > > On Wed, 31 Oct 2018 at 10:27, Thiago Macieira > wrote: > > > On Tuesday, 30 October 2018 13:56:45 PDT NIkolai Marchenko wrote: > > >

Re: [Development] Build system for Qt 6

Hi Lars, On Tue, 30 Oct 2018 at 23:42, Lars Knoll wrote: > > On 30 Oct 2018, at 05:00, Christian Gagneraud wrote: > > On Tue, 30 Oct 2018 at 01:17, Lars Knoll wrote: > > Then why spend energy/money to fix something that is broken by design? > > (Again, that is a per

Re: [Development] Build system for Qt 6

On Wed, 31 Oct 2018 at 10:27, Thiago Macieira wrote: > On Tuesday, 30 October 2018 13:56:45 PDT NIkolai Marchenko wrote: > The only thing I'm criticising is that its proper chance involves Qt being the > guinea pig. Find someone else instead and grow your community. Get track > record for

Re: [Development] Build system for Qt 6

> > On 30 Oct 2018, at 05:00, Christian Gagneraud wrote: > > - Any track record that Qbs was not fit for the job? (Please no "we > > can't build Qt with it", as you cannot build Qt with anything but > > qmake right now) > > No, of course one could have made

Re: [Development] Build system for Qt 6

On Tue, 30 Oct 2018 at 22:50, Denis Shienkov wrote: > == R I P, QBS == Please stop these "RIP", you're cautioning a burial ceremony that is just pure speculation so far. "CMake will fail" (tm) [another burial ceremony that is just pure speculation so far] Chris

Re: [Development] Build system for Qt 6

On Tue, 30 Oct 2018 at 22:18, Richard Weickelt wrote: > > Ich schick's doch nicht an die Liste, ist wenig konstruktiv :-/ > > No conspiracy here, but i have a few more questions (not related, in > > no particular order) > > - Did Jake left the QtC due to your early decision to drop qbs? ( I > >

Re: [Development] Build system for Qt 6

On Tue, 30 Oct 2018 at 01:17, Lars Knoll wrote: > > Hi all, Hi Lars, Playing the devil's advocate here. May I ask: Which democratic/meritocratic process was used to take this decision? I do understand that the QtC is the Qbs instigator/maintainer, so nobody can blame you for pulling the plug

Re: [Development] Build system for Qt 6

On Tue, 30 Oct 2018 at 20:47, Иван Комиссаров wrote: > Иван Комиссаров > > 30 окт. 2018 г., в 4:34, Thiago Macieira > > написал(а): > > Can you name any project of moderate complexity using it? > > > > How about Qt creator? How about commercial projects? > > But what I would like to ask is how

Re: [Development] Build system for Qt 6

Warning: Free sarcasm, i'm not serious (well, maybe a little bit...) On Tue, 30 Oct 2018 at 18:29, wrote: > > Honestly I feel very disappointed as well with this decision. I feel > similarly to others, Qbs is now being phased out so fast (half a year of > development, another half a year of

Re: [Development] Qt 6 buildsystem support requirements

On 22 July 2018 at 00:42, Kevin Kofler wrote: > Bogdan Vatra via Development wrote: >> Anyway IMHO is more important to have a clean, nice and easy to use syntax >> and to be tooling friendly than 1.b. > > A custom build system is always a major pain point for distributions. A > circular

Re: [Development] Qt 6 buildsystem support requirements

On 22 July 2018 at 14:05, Thiago Macieira wrote: > On Saturday, 21 July 2018 16:52:44 PDT Jason Newton wrote: >> -Ability to build external libraries from source or pull in binary >> libraries > > This is not a feature. It's a misfeature. > > It's EXACTLY the reason our seniormost engineers spent

Re: [Development] clang-format

On 20 June 2018 at 03:33, Allan Sandfeld Jensen wrote: > Btw. Just for your information. > > I have attached a few random examples of what we can look forward too after > running an auto-"beautifying" tool over our hand-formated Qt code. And these > changes are NOT something we can configure out

Re: [Development] Why waste energy supporting Python?

On 25 April 2018 at 13:41, d3fault wrote: > 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

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

Hi Thiago, Thanks for the details, i'll switch to qt-interest. I've made progress but still have a weird package conflict for QtWebEngine. Chris On 7 January 2018 at 03:27, Thiago Macieira <thiago.macie...@intel.com> wrote: > On Saturday, 6 January 2018 09:21:35 -02 Christian Gagner

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

On 5 January 2018 at 15:11, Thiago Macieira wrote: >> I wish too, i could target Linux-x86_64, but i cannot. This codebase >> currently builds for WINTEL32 and Linux/ARM32, it used to be built for >> a Geode or VIA proc, some time ago, with Qt-4.x > > The fact that you

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

On 5 January 2018 at 15:11, Thiago Macieira <thiago.macie...@intel.com> wrote: > On Thursday, 4 January 2018 23:40:40 -02 Christian Gagneraud wrote: >> Neatpick: AVX itself doesn't require billions of transistors, the >> first intel proc to require more than a billion t

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

On 5 January 2018 at 12:22, Thiago Macieira <thiago.macie...@intel.com> wrote: > On Thursday, 4 January 2018 20:52:40 -02 Christian Gagneraud wrote: >> On 5 January 2018 at 03:16, Kevin Kofler <kevin.kof...@chello.at> wrote: >> > Thiago Macieira wrote:

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

On 5 January 2018 at 03:16, Kevin Kofler wrote: > Thiago Macieira wrote: >> In particular: -no-sse2. >> >> If you use that option, that means you're optimising for Pentium III and >> earlier, not Pentium 4. All Pentium 4 processors have SSE2. I was looking at LEDE (a

Re: [Development] Future of QBS

On 18/10/17 21:35, Kevin Funk wrote: On Monday, 16 October 2017 22:48:06 CEST Christian Gagneraud wrote: I think my questioning was legit, even if the style was far from perfect. Right, let me excuse myself as well for the strong wording. Hi Kevin, "Sweet as" as they say h

Re: [Development] Qt installation prefix path issue

On 18/10/2017 8:08 pm, "Thiago Macieira" wrote: [moving to the interest mailing list; please drop development@ when replying] On Tuesday, 17 October 2017 23:38:24 PDT bhaskar kotha wrote: > How to configure Qt so that Qmake should not take absolute path. That's not

Re: [Development] Future of QBS

On 17/10/2017 11:27 PM, Jake Petroules wrote: We both want to solve the same problems, but I'm not sure exactly what you mean here about how building Qt with Qbs is a trap and that we should not "leak". The trap: From reading your comments, I had the feeling that you're thinking that building

Re: [Development] Future of QBS

On 17/10/2017 9:30 pm, "Jake Petroules" <jake.petrou...@qt.io> wrote: > On Oct 17, 2017, at 9:21 AM, Christian Gagneraud <chg...@gmail.com> wrote: > > On 17/10/2017 7:52 pm, "Jake Petroules" <jake.petrou...@qt.io> wrote: > > > On Oct 16,

Re: [Development] Future of QBS

On 17/10/2017 7:52 pm, "Jake Petroules" wrote: > On Oct 16, 2017, at 3:34 PM, jeandet wrote: > > I have the feeling that a Qt build system will always force the users > to choose between another tool they know but where the Qt support might

Re: [Development] Future of QBS

On 16 October 2017 at 21:40, Kevin Funk <kevin.f...@kdab.com> wrote: > On Sunday, 15 October 2017 11:20:13 CEST Christian Gagneraud wrote: >> On 14 October 2017 at 04:22, Jean-Michaël Celerier >> >> <jeanmichael.celer...@gmail.com> wrote: >> >> nobody

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

Few days ago, should be easy to find on mailing list archives Sorry on my phone right now. Go to October arch. Chris ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Future of QBS

On 16/10/2017 7:31 pm, "BogDan Vatra" <bog...@kdab.com> wrote: On luni, 16 octombrie 2017 17:38:53 EEST Christian Gagneraud wrote: > On 16 October 2017 at 15:42, Kevin Kofler <kevin.kof...@chello.at> wrote: > > Christian Gagneraud wrote: > >> I would

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

>From an end user point of view, i think it's a great idea but I think it conflicts with Qml. At work we have our own set of highly customised widgets, for embedded devices, it simply works, no need (yet) for Qml. I would be interested to see your work and give my opinion if it can help. Full

Re: [Development] Future of QBS

On 16 October 2017 at 15:42, Kevin Kofler <kevin.kof...@chello.at> 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 explain anything, doesn't gives any an

Re: [Development] Future of QBS

On 15 October 2017 at 23:23, Jake Petroules <jake.petrou...@qt.io> wrote: > > >> On Oct 15, 2017, at 11:20 AM, Christian Gagneraud <chg...@gmail.com> wrote: >> >> On 14 October 2017 at 04:22, Jean-Michaël Celerier >> <jeanmichael.celer...@gmail.com>

Re: [Development] Future of QBS

On 14 October 2017 at 04:22, Jean-Michaël Celerier wrote: >> nobody is going to port Qt to CMake (if you disagree start a new thread) > > https://plus.google.com/+AaronSeigo/posts/fWAM9cJggc8 I would resume this post as "I love CMake, CMake is the only way. You're

Re: [Development] QtCS 2017 logging/tracing session notes

On 12 October 2017 at 10:10, Arnaud Clère wrote: > Regarding the ParTraP language, currently, you need to parse, transform and > classify > unstructured traces in a JSON form to be able to use it. JSON will remain the > pivot format > between trace stores and

Re: [Development] QtCS 2017 logging/tracing session notes

On 11 October 2017 at 21:20, Christian Gagneraud <chg...@gmail.com> wrote: > In the kernel mode case, you access the events from /proc, which is > backed by a kernel RCU list/buffer, i don't know how they have > implemented their userspace solution, but i'm expecting something >

Re: [Development] QtCS 2017 logging/tracing session notes

Hi, Going through the wiki, the pdf and the codereview again, i see 3 different things: - Qt: Logging framework - ModMed: real-time dissection of organised/structured logs - Ltt/ETW: event tracing/profiling Different needs, different means, different reasons and different goals. I like all 3!

Re: [Development] QtCS 2017 logging/tracing session notes

On 10 October 2017 at 22:48, Thiago Macieira wrote: > do not change qdebug but provide structured tracing as a new facility Any chance this can be made lock-free from a caller point of view? (PS: I don't even know if qDebug streaming is lock-free and i'm interested to

[Development] codereview website down?

https://codereview.qt-project.org is not loading, it hangs. Is it just for me? Chris ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

[Development] Is qt.io down?

Hi there, Is qt.io and all *.qt.io down for you or is it just me? Krys. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] New Module for Serial Buses

On 27/05/15 03:04, Thiago Macieira wrote: On Tuesday 26 May 2015 15:47:04 Simon Hausmann wrote: My first suggestion is to give the module a better name. Bus is an overloaded term with many meanings and it is IMO too close to our DBus module. Why not go with what your first sentence in the

Re: [Development] QtModeling - the last mile

On 26/05/15 07:18, Sandro Andrade wrote: On Wed, Apr 29, 2015 at 6:08 PM, Sandro Andrade sandroandr...@kde.org wrote: On Wed, Apr 29, 2015 at 6:01 PM, Konstantin Ritt ritt...@gmail.com wrote: Any links/code/docs?) Yes, sorry :) Wiki page: http://wiki.qt.io/QtModeling Git repository:

Re: [Development] Introducing Qt Gamepad, a new qt-labs project

On Wed, 13 May 2015 08:00:07 Nichols Andy wrote: On 13 May 2015, at 01:04, Christian Gagneraud chg...@gna.orgmailto:chg...@gna.org wrote: Any chance QtGamepad would provide support for devices like the SpaceNavigator (3D mouse) [1]? I recently posted a question about

Re: [Development] Introducing Qt Gamepad, a new qt-labs project

On Tue, 12 May 2015 16:16:00 Nichols Andy wrote: You may have noticed if you religiously watch #qt-labs or just poke around on code.qt.io page that a new project has recently been added to qt-labs. QtGamepad is a spare-time / creative Friday project that I've been playing with on-and-off

Re: [Development] QGView and deprecated indirect painting

On 08/04/15 00:10, Paul Olav Tvete wrote: On Wednesday 1. April 2015 13.28.50 Christian Gagneraud wrote: So, my question is: Do you guys plan to remove this feature, and if yes (which seems likely to me), how could I then control colors, opacity and drawing order on a per view basis

[Development] QGView and deprecated indirect painting

Hi Trolls! Note: I'm sending this email to qt-dev not to qt-interest because it deals with deprecated features and API changes of the Qt Graphics View framework. QGraphicsView has an optimisation flag called IndirectPainting, which when set restore the old painting algorithm that calls

Re: [Development] Add widgets into qt3d window

On 31/03/15 01:08, Arjun Das wrote: Hi , I have created a simple qt3d application in c++, which has a rotating cube. I would like to add buttons to the windows to stop/start rotating the cube. I am not able to see such an example anywhere in the qt3d examples which has support for widgets.

Re: [Development] Problems running Qt3D examples

Hi Sean, On 24/03/15 22:33, Sean Harmer wrote: Hi, On Tuesday 24 March 2015 13:09:23 Christian Gagneraud wrote: Hi there, I've just build qt5 from git (5.5 branch, commit cdc3bf5) and I'm having problems running some qt3d examples. I've run *all* examples and only a few don't work

[Development] Problems running Qt3D examples

Hi there, I've just build qt5 from git (5.5 branch, commit cdc3bf5) and I'm having problems running some qt3d examples. I've run *all* examples and only a few don't work: - assimp, multiviewport: window content is black - gltf: window content is never drawn Don't know if it's related, but the

[Development] = 5.3 bug? GraphicsView and mouse event doubleclick flag

Hi Trolls! The documentation said that the Qt::MouseEventCreatedDoubleClick flag of Qt::​MouseEventFlags Indicates that Qt has created a MouseButtonDblClick event from this event. The flag is set in the causing MouseButtonPress, and not in the resulting MouseButtonDblClick. It is marked as

Re: [Development] Setup QT creator for developing QT apps on wandboard-Error

On 29/07/2014 4:46 p.m., Nilesh Kokane wrote: [...] Manage: Name:wandboard-solo Authentication type :password Host Name:minda-HP-dx2480-MT-VP562PA SSH port:22 usearname:root Password: 1)With that when i tried to test the device with the ethernet connection i'm getting the following

Re: [Development] Setup QT creator for developing QT apps on wandboard-Error

On 29/07/2014 4:46 p.m., Nilesh Kokane wrote: Hello , referring to http://wiki.wandboard.org/index.php/Setup_QT_creator_for_developing_QT_apps_on_wandboard#Build_and_Deploy_application_in_QT_Creator [...] 2)The second error is that even a simple default Qt console app program is

Re: [Development] Support for your evaluation of Qt

On 10/07/2014 11:19 p.m., Mitch Curtis wrote: On 07/10/2014 12:20 PM, Ch'Gans wrote: On 09/07/14 19:53, Andrea Barna wrote: Hi, I am Andrea from Digia Qt, I have recently taken over the Qt businessin your region. Hi Andrea, All the best for your new position! I noticed that you

Re: [Development] Support for your evaluation of Qt

On 11/07/2014 11:22 a.m., Thiago Macieira wrote: On Friday 11 July 2014 10:05:03 Christian Gagneraud wrote: Boot To Qt for Embedded Linux (Not talking about android here), is based on Yocto (which is open-source), there exists a Qt5 layer (Dedicated Yocto sub-project), and I think that Digia

Re: [Development] QtCS2014 - QtPrintSupport Session

On 14/06/14 05:06, John Layt wrote: Hi, The notes form the QtPrintSupport session are available at https://qt-project.org/groups/qt-contributors-summit-2014/wiki/QtPrintSupport . Basically it's a long list of all the work needing to be done to finish the new print library. While a lot is

Re: [Development] Windows Online Installer problem(s)

to download a package for android (foo-bar-baz-dwarf-something.7z). BTW, do you have plan to sign your package? Right now, there's just a checksum file. Chris Br, Jani -Original Message- From: Chris Gagneraud [mailto:chg...@googlemail.com] On Behalf Of Christian Gagneraud Sent: 6

Re: [Development] Windows Online Installer problem(s)

-bounces+jani.heikkinen=digia@qt-project.org] On Behalf Of Christian Gagneraud Sent: 5. helmikuuta 2014 4:03 To: development@qt-project.org Subject: [Development] Windows Online Installer problem(s) Hi there, I tried to install Qt with the latest official online installer on a Windows

Re: [Development] Windows Online Installer problem(s)

[mailto:development-bounces+jani.heikkinen=digia@qt-project.org] On Behalf Of Christian Gagneraud Sent: 5. helmikuuta 2014 4:03 To: development@qt-project.org Subject: [Development] Windows Online Installer problem(s) Hi there, I tried to install Qt with the latest official online installer

[Development] Windows Online Installer problem(s)

Hi there, I tried to install Qt with the latest official online installer on a Windows computer [1], and I couldn't install it on the 'D' disk, because the 'C' disk didn't have enough space to store the downloaded data (I guess in the system temp dir, which is likely to be on c:) Another

Re: [Development] GLSL Optimizer

On 02/03/2014 10:17 PM, Sean Harmer wrote: Hi, On Sunday 02 February 2014 17:09:24 Michal Lazo wrote: Hi I found pretty nice article about shaders optimization in arm GPU drivers For example Unity3d use it in there shaders compiler http://aras-p.info/blog/2010/09/29/glsl-optimizer/

Re: [Development] ChangeLog updated for 5.2.0

On 19/11/13 17:02, Thiago Macieira wrote: I've just updated the Changelog for 5.2.0 with the output from the script that I've just uploaded at https://codereview.qt-project.org/71641. The changelog The help message still refer to header-diff BTW. my 2 cents, Chris update is at

[Development] Qt-5.1, qglobal.h and PIC detection

Hi, I'm using CLang build-analize tool, and when I switched from Qt 4.8 to Qt 5.1 (insalled from Qt project's download area), I got a Qt #error, basically the code is built with -fPIC, but CLang doesn't define a PIC macro, so the build fails due to a check in qglobal.h (see details below). Is

Re: [Development] Qt-5.1, qglobal.h and PIC detection

On 06/11/13 12:25, Olivier Goffart wrote: On Wednesday 06 November 2013 12:17:56 Christian Gagneraud wrote: Hi, I'm using CLang build-analize tool, and when I switched from Qt 4.8 to Qt 5.1 (insalled from Qt project's download area), I got a Qt #error, basically the code is built with -fPIC

  1   2   >