On 2017-12-19 16:18, Thiago Macieira wrote:
On terça-feira, 19 de dezembro de 2017 03:25:17 PST Sergio Martins
wrote:
Furthermore, supporting both android and android-clang is a
maintenance
burden: the mkspecs are often broken, either because of a new Qt
version
or because of a new NDK version
Hi all,
We need to start offering pre-built android binaries built with
android-clang and bump our minimum supported NDK version.
gcc on android is pretty much dead since 2016:
"GCC is no longer supported. It will be removed in NDK r18.
libc++ is now the default STL for CMake and standalone
On 2017-11-29 16:02, Jose Fernandez Navarro wrote:
Hello,
I have a QOpenGLWidget object where I draw
using both OpenGL and QPainter. When I called
grab() on the object prior 5.9.2 I would get a seg. fault.
Now (5.9.2) I can grab the widget's image but
the QPainter stuff is missing and actually i
Hi,
I'd like to nominate Christoph Schleifenbaum for Approver.
He's been with KDAB for 12 years and has done dozens of fixes for cocoa,
widgets and item views.
He' also one of the developers who worked on the Qt3DStudio port to Qt
very recently.
https://codereview.qt-project.org/#/q/owne
On 2017-10-11 08:17, Eike Ziller wrote:
On 10. Oct 2017, at 15:41, Sergio Martins
wrote:
Oops, here's the non-internal URL:
https://docs.kdab.com/analysis/qt5/clazy.html
Thanks Mitch
I’d be interested in seeing results for Qt Creator too :)
Hi Eike,
Here you go: https://docs.kda
On 2017-10-13 16:12, Thiago Macieira wrote:
On Friday, 13 October 2017 07:56:47 PDT Sergio Martins wrote:
IMHO the qt-project is not in a position to reject Qt building with
qbs,
simply because there's no other implementation, nobody is going to
port
Qt to CMake (if you disagree start
Hi,
At the QtCS it was mentioned that maybe qbs could use JavaScriptCore and
std:: types,
at first I thought this was for making it easy for qbs to be a non-Qt
project, but then I realized it was for boot-strapping purposes.
I don't know if you have a vision, but given that most other build
Oops, here's the non-internal URL:
https://docs.kdab.com/analysis/qt5/clazy.html
Thanks Mitch
On 2017-10-10 14:27, Sergio Martins wrote:
Hi,
KDAB is now running clazy over the Qt code base, you can check the
results here: https://ci.kdab.com/~build/analysis/qt5/clazy.html
Next st
Hi,
KDAB is now running clazy over the Qt code base, you can check the
results here: https://ci.kdab.com/~build/analysis/qt5/clazy.html
Next step is to figure out which sub-set we want to use in within
qt-project, if we want to enforce any via CI, which ones we want to fix
for Qt5 and which
On 2017-10-10 13:01, Rafael Roquetto wrote:
Howdy,
I would like to nominate Andras Mantia, a fellow colleague at KDAB, for
approver status. Andras has been a key contributor in the develpment of
the
recently unveiled Qt3DStudio. His continuous involvement with the
project and
deep understandi
On 2017-09-30 13:54, René J. V. Bertin wrote:
Apart from this I'd suspect you will still get the SEGV if you do not
block
- even if the frequency changes. This points to you using some kind of
pointer that is not properly controlled (e.g. sending a signal to a
QFSW
that is already deleted).
On 2017-08-30 23:13, Thiago Macieira wrote:
Ok, so you found by git bisect (or similar) action. I was hoping you
had some
interesting way of debugging that the problem is timers constantly
firing. I
woder if GammaRay can give you a list of timers active in a thread and
which
objects it's conne
On 2017-07-11 12:25, Simon Hausmann wrote:
Hi,
I'd like to propose Viktor for approver status. Since August last year
he's been contributing to QtWebEngine full-time. Based on my
experience talking to him and working with him, I trust him to review
changes thoroughly and approve or reject change
On 2017-05-17 17:19, Thiago Macieira wrote:
Since I am unable to fulfill my duties as maintainer, I am stepping
down and
opening the way up for someone else.
Hi Thiago,
Do you have an overview on what's the current state of the module ? Just
so the next maintainer gets an idea of where to st
On 2017-05-06 16:00, Thiago Macieira wrote:
Someone could do that. I'd even appreciate just a backtrace from the
deadlocked application.
Have you asked the CI guys for such backtrace ? Why isn't there a JIRA
issue for this ?
Regards,
--
Sérgio Martins | sergio.mart...@kdab.com | Senior Soft
On 2017-05-05 11:00, Michal Klocek wrote:
Hi
With 5.8.0 we released web engine libs which export operator new ,
new[] , delete, delete[] globally, unfortunately the issue was not
spotted in time.
https://bugreports.qt.io/browse/QTBUG-60565
With 5.9.0 we plan to correct the issue, unfortunately
On 2017-05-04 15:18, Thiago Macieira wrote:
Em quinta-feira, 4 de maio de 2017, às 06:58:53 PDT, Konstantin Tokarev
escreveu:
But we could have Linux clang configuration with clazy plugin.
Why? Clazy is not part of our development philosophy. We should only do
that
after there's a QUIP explai
On 2017-05-04 14:53, Thiago Macieira wrote:
Em quinta-feira, 4 de maio de 2017, às 00:23:46 PDT, Heikki Halmet
escreveu:
Clang 4: Do we really need this to be tested with Linux in CI? If yes,
then
which configuration it will be replaced?
I don't think we need to. The macOS builds should be su
On 2017-05-04 14:51, Konstantin Tokarev wrote:
03.05.2017, 17:27, "Sergio Martins" :
On 2017-05-03 15:02, Konstantin Tokarev wrote:
Remaining question is versioning. While it's fine to dub current
release "5.9" (but not 5.0, because we will have another WebKit
up
On 2017-05-03 15:02, Konstantin Tokarev wrote:
Remaining question is versioning. While it's fine to dub current
release "5.9" (but not 5.0, because we will have another WebKit update
in 5.10 time frame), using Qt versions in QtWebKit has downsides:
1. It is not clear if 5.N+1 ships with the same
On 2017-04-20 18:06, Matthew Woehlke wrote:
On 2017-04-16 10:44, Corentin wrote:
If you want the same behavior, you can create a proxy for your
associative
container instance, with a custom iterator whose operator*() returns a
std
pair ( or a QPair ) - quite a bit of boilterplate code.
...or
On 2017-04-07 14:02, Lars Knoll wrote:
There might be a little catch with regards to structs containing
members that are 8 bytes in size (aka quint64). Are those getting
passed in registers on 32bit ARM?
struct struct_16Bytes
{
unsigned long long first, second;
};
unsigned long long test(s
Hi,
Some time ago I documented the guidelines on passing by value vs
const-ref:
https://wiki.qt.io/API_Design_Principles#Passing_by_const-ref_vs._Passing_by_value
This was discussed in #qt-labs at the time and informally +2'd there.
But the reality is that passing small structs by value is n
On 2017-02-06 14:54, Alex Blasche wrote:
There were no objections and maintainer of a module implies approver,
so could
somebody do the honours and grant Mike the rights please? The
necessary period
has long since passed.
I am sorry but being the maintainer does not imply approver rights.
h
On 2017-01-31 12:50, Philippe wrote:
As far as I understand, I see a performance regression with
QStringView, for all the cases where copy-on-write can't take place
any longer.
In the following code, an extra malloc is needed. Or am I wrong?
void bar()
{
QString s("hello");
foo(s
On 2017-01-02 11:01, Frédéric Marchal wrote:
(...)
There is more to it than converting a date to a string:
* Add N days to a date.
* Find the number of days in a month.
* Compare two dates.
* Count the number of days between two dates.
Hi,
Have you seen KCalendarSystem ?
https://api.kde.org
On 2016-12-05 12:23, Allan Sandfeld Jensen wrote:
Hi all,
I just noticed Konstantin Tokarev who has been doing most of the
development,
and practical maintenance of QtWebKit after it moved into "removed"
state is
still missing reviewer status. I suggest we correct this.
+1
Regards,
--
Sér
On 2016-10-26 16:01, Thiago Macieira wrote:
On quarta-feira, 26 de outubro de 2016 10:18:49 PDT Ola Røer Thorsen
wrote:
I'm getting compile errors building both Qt 5.6.2 and 5.8 beta from
source
when configuring Qt with -qreal float and building using g++ on Linux.
The
affected modules are Cha
On 2016-10-20 21:43, Thiago Macieira wrote:
Em quinta-feira, 20 de outubro de 2016, às 17:28:39 PDT, Philippe
escreveu:
std::atomic is used as underlying implementation for the the Qt atomic
API with CLang on Mac.
But why not with Visual Studio 2015? You will certainly mention some
bug,
but th
On 2016-10-12 20:59, Thiago Macieira wrote:
Hello
We've got a number of issues that got fixed in 5.7 by the change that
made
QFactoryLoader stop unloading plugins (notably, the Network Manager
bearer
plugin). Given that QtDBus in 5.6 is now heavily threaded, a number of
new
issues have croppe
On 2016-09-30 11:39, Sean Harmer wrote:
Hi,
just a query as to how people do bulk checkouts of different branches
when working with the Qt git modules. It would be nice to be able to
use git submodule foreach ... but this is a problem because not all
modules use the same branching scheme.
So, w
On Sunday, 11 September 2016 21:43:46 WEST Jérémie Delaitre wrote:
> Can the same checks be implemented in clang-tidy instead of having yet
> another tool? clang-tidy now has boost specific checks so maybe they would
> also accept a Qt specific module in there.
I haven't been able to use clang-tid
Hi,
I've been developing a Qt oriented clang compiler plugin called clazy [1].
It has about 50 custom checks/warnings for common Qt and C++ mistakes.
I would like to propose clazy to be used to sanitize API of new Qt modules. Of
course, only a few of the 50 checks are relevant to API, so I will
On Tuesday, August 30, 2016 01:51:04 PM Tor Arne Vestbø wrote:
> Hi all!
>
> Mike Krus was so kind to contribute support for Apple's tvOS to the
> UIKit platforms, and I'd like to make it official that he's the tvOS
> maintainer.
Can't vote for maintainership as I'm not a maintainer, but +1 for b
On Friday, 1 July 2016 11:36:56 WEST Thiago Macieira wrote:
> Premises not under discussion:
>
> Qt source code is product and meant to be read by our users
> Qt source code must be clean and readable
> The above is not up for debate.
>
> For some time now, we've had a flurry of chang
On Thursday, 2 June 2016 08:17:08 WEST Massimo Callegari via Development
wrote:
> Hi everyone,
>
> is it just me or QtMultimedia 5.6.0 video playback is quite broken on Ubuntu
> 16.04 ?
>
> I think the reason is that Qt 5.6.0 (and 5.7.0 as well) are still built
> against gstreamer 0.10, which is
On Wednesday, 1 June 2016 15:44:22 WEST Marc Mutz wrote:
> On Wednesday 01 June 2016 15:15:17 Sergio Martins wrote:
> > Subjective reasons against leading commas:
> > - It's ugly
> >
> > Subjective reasons against trailling commas:
> > - It's ugly
>
On Wednesday, 1 June 2016 14:41:30 WEST Marc Mutz wrote:
> Hi,
>
> There seems to have been a silent underground move to uglify the Qt sources
> , by using commas to introduce lines
> . I have no idea where this came from
> , but it looks butt
> -ugly and it is in violation of http
> (http://wiki.
On Tuesday, 31 May 2016 13:23:24 WEST Berkay Elbir wrote:
> Hello All,
>
> I have a problem about Qt Stylesheets, I am using Qt 5.6 on windows.(This
> problem does not exist in Qt 5.5.1) I use this code piece, this is a QLabel
> inside a QDialog.
>
> ui.newGroupNameLabel->setStyleSheet("QLabel {
On Wednesday, 27 April 2016 12:37:26 WEST Denis Shienkov wrote:
> Hi developers.
>
> I faced with a big problem with the video playback performance, when I try
> to open the mp4 video file from any of QML video examples. I have a high
> CPU loading (~40%) and the video is freezing and jerks. But t
On Wednesday, March 30, 2016 09:34:40 AM Sean Harmer wrote:
> Hi All,
>
> I'd like to nominate Volker Krause for approver status. Volker is one of the
> main authors of GammaRay, is very active in the Qt Automotive sphere where
> he leads up KDAB's contributions, and has touched many parts all ove
On Friday, March 18, 2016 10:46:41 AM Koehne Kai wrote:
> > -Original Message-
> > From: Development [mailto:development-
> > [...]
> > It remains that this document is expected to be quite stable, so there
> > would be some sense to having a stable URL to which we routinely copy the
> > ne
On Friday, March 18, 2016 02:52:42 PM René J. V. Bertin wrote:
> Till Oliver Knoll wrote:
> > According to
> >
> > https://wiki.qt.io/New_Features_in_Qt_5.6
> >
> > "Optional support for using FreeType on Mac OS X" is now available.
>
> Yeah, but apparently not exactly as planned:
Where was -
On Saturday, March 19, 2016 12:50:26 PM René J.V. Bertin wrote:
> What about fontconfig, is that library used on OS X when Qt is configured
> with -fontconfig?
I don't think so, see QCocoaIntegration::fontDatabase(), it returns
QCoreTextFontDatabase inconditionally.
Doesn't seem like much work
On Thursday, March 17, 2016 02:30:03 PM Koehne Kai wrote:
(snip)
> Completely orthogonal to this is though in which format the documents
> are. You're specifically mentioning .qdoc, but I assume it wouldn't really
> matter if it's Markdown (from the 'reusability' perspective)?
If we keep these d
On Thursday, March 17, 2016 11:24:10 AM Mathias Hasselmann wrote:
> Am 17.03.2016 um 10:01 schrieb Sorvig Morten:
> > How about treating the coding guidelines as \internal documentation?
> > We could then at some point build and publish it together with the
> > rest of the \internal's. (suitably se
(snip)
On Friday, March 18, 2016 08:48:52 AM Jedrzej Nowacki wrote:
> So I think, that we should not discuss what is better qdoc or md. The real
> discussion is about tooling, what is the best tool to sanitize Qt code.
This thread is derailing.
Kai wants to move a few wiki documents to git, ther
On Monday, February 29, 2016 07:40:07 PM Michael Möllney wrote:
> Am 29.02.2016 um 19:15 schrieb Thiago Macieira:
> > On segunda-feira, 29 de fevereiro de 2016 18:33:39 PST Michael Möllney
wrote:
> >> At least this is what can be found on:
> >> http://en.cppreference.com/w/cpp/compiler_support
> >
On Tuesday, 23 February 2016 13:09:10 WET Thiago Macieira wrote:
> On terça-feira, 23 de fevereiro de 2016 21:01:39 PST Sergio Martins wrote:
> > On Monday, 22 February 2016 22:01:31 WET Thiago Macieira wrote:
> > > On terça-feira, 23 de fevereiro de 2016 05:32:55 PST Tur
On Monday, 22 February 2016 22:01:31 WET Thiago Macieira wrote:
> On terça-feira, 23 de fevereiro de 2016 05:32:55 PST Turunen Tuukka wrote:
> > > Is Qt 5.7 going to be the *only* release to support WEC2013?
> >
> > No. Both Qt 5.6 and Qt 5.7 will support WEC13.
>
> Quoting you on your yesterday'
On Monday, February 01, 2016 11:08:54 AM Marc Mutz wrote:
> Hi,
>
> We're seeing increasing use of lambdas in dev, and I'm a bit unhappy about
> the result.
>
> E.g. (not picking on Anton here, I have done the same before):
>
> auto firstEqualsName = [&name](const QPair &header)
> {
> ret
On Tuesday, 22 December 2015 15:06:34 WET Konstantin Tokarev wrote:
> 22.12.2015, 14:50, "Bubke Marco" :
> > Clazy is nice but it's under GPL so it's not possible to integrate it in
> > the creator clang code model. But I think we need something like clazy
> > for the clang code model too.
> I see
On Wednesday, 9 December 2015 16:38:02 WET Joerg Bornemann wrote:
> > - in some situations, it makes code easier to understand (:
> > m_foo(nullptr)).
> So nullptr is easier to understand, because assigning 0 to a pointer
> variable didn't make clear that it now contains a null pointer?
> If there
On Wednesday, 9 December 2015 14:29:19 WET Thiago Macieira wrote:
> On Wednesday 09 December 2015 22:47:51 Marc Mutz wrote:
> > > const char *ptr = 0;
> >
> > What we agreed on was for Q_NULLPTR.
> >
> > Some developers back then were complaining that the *macro* is ugly, and
> > that by
On Wednesday, 9 December 2015 16:14:00 WET Marc Mutz wrote:
> Arguments in favour:
> - it's the C++ way of writing the null pointer constant these days
> - we need to use it in headers, anyway, to allow people to use -Wzero-as...,
> and it makes no sense to have two sets of rules for headers and i
On Sunday, 2 August 2015 01:24:50 WET John Layt wrote:
> It would require a lot of shuffling code around, as a lot of code is
> in the d_ptr, it would horribly complicate things and there's the
> potential for interesting corner cases, like say adding enough years
> to a date to push it from one im
On Thursday, November 05, 2015 11:44:33 AM Thiago Macieira wrote:
> Proposal: force QStringLiteral uses to always address a heap-allocated
> QString, instead of pointing to the static data. Possibly, this should be an
> interned atom/quark à la GQuark, so two passes on the same QStringLiteral
> wou
On Wednesday, June 10, 2015 01:55:01 PM Matthew Woehlke wrote:
> On 2015-06-10 10:20, Koehne Kai wrote:
> > Hi,
> >
> > I'm currently converting a codebase from old-style connects to new-style
> > ones. Thanks to Qt Creator's refactoring support this is actually quite
> > easy ... it gets ugly tho
On Tuesday, October 27, 2015 04:40:07 PM Thiago Macieira wrote:
>
> From qcompilerdetection.h:
>
> # if defined(_HAS_DINKUM_CLIB) && !defined(_HAS_NULLPTR_T)
> #undef Q_COMPILER_NULLPTR
> # endif
By the way, _HAS_DINKUM_CLIB is about the C library, not C++.
Should be replaced with: !_GLIB
On Wednesday, October 21, 2015 03:15:38 AM Robert Griebl wrote:
> On 20.10.2015 17:56, Thiago Macieira wrote:
> > ...because the application will unload the libraries while other threads
> > are still running code from those threads. In the bug report, the crash
> > happens because of the QXcbEvent
Hi,
Can we disable gcc's feature of emitting extra code to make local static
initialization thread safe ? (-fno-threadsafe-statics)
Since MSVC doesn't support it we can't rely on this feature in cross-platform
Qt code (maybe only in QPA code).
Generates uneeded code and helps hidding crashes
On Thursday, June 04, 2015 16:01:01 Aleix Pol wrote:
>
> Is it really that much work? I hear there's tools to do so [1] and
> it's the compiler telling whether it's correct or not.
>
> Aleix
I've added Q_DECL_OVERRIDE to some kdepim libraries with clang-modernize and 5
minutes of my time.
I a
On Monday, March 23, 2015 13:59:11 Rafael Roquetto wrote:
> The plan is to keep the BB10 plugin around for now (just that we will no
> longer be officially supporting it), but eventually we plan to remove it
> completely from the Qt codebase in case no one looks after it. We will keep
> it around
On Tuesday, March 03, 2015 16:52:43 Thiago Macieira wrote:
> Since we're seeing both operator() and the innerFunction frames, I assume
> you compiled in debug mode. Correct?
yes
>
> Anyway, I have GCC 4.9.2, Binutils 2.25.0 (using gold) and I cannot
> reproduce in either debug, regular release o
On Tuesday, March 03, 2015 11:45:49 Thiago Macieira wrote:
> On Tuesday 03 March 2015 13:55:29 Sergio Martins wrote:
> > Hi,
> >
> > So that you don't waste time pulling your hair out: plugin loading is
> > broken with gcc 4.9.2
> >
> > There'
Hi,
So that you don't waste time pulling your hair out: plugin loading is
broken with gcc 4.9.2
There's some clash between global static QFactoryLoader instances.
Reproduced on Archlinux (and on Fedora by jpnurmi).
Regards,
--
Sérgio Martins | sergio.mart...@kdab.com | Software Engineer
Klarä
On Friday, December 12, 2014 17:47:16 Gunnar Roth wrote:
> I fix it by using
> #if defined(_M_ARM) // QTBUG-42038 , only talks about winrt but this also
> happens at least on wec2013 arm devices too, maybe even on ce 6/7. #pragma
> optimize("", off)
> #endif
>
> instead of
>
> #if defined(Q_OS_WI
On Friday, October 10, 2014 11:39:33 Milian Wolff wrote:
> Hello all,
>
> once more I'm preparing a Qt 5 build for profiling purposes and wonder again
> why there is no way to combine -release and -debug in Qt's configure
> script. The only way to get a sane build for profiling Qt code itself that
On Tuesday, February 11, 2014 12:59:45 Thiago Macieira wrote:
> Current tests are frequently showing the following error messages:
>
> c:
> \work\build\qt\qtbase\tests\auto\corelib\global\qtendian\tst_qtendian.cpp(14
> 0)
> : fatal error C1001: An internal error has occurred in the compiler.
If t
On Saturday, January 04, 2014 00:16:26 Jiergir Ogoerg wrote:
> I did file the bug, but what happens after that is entirely up to the
> glibc devs:
> https://sourceware.org/bugzilla/show_bug.cgi?id=16391
Hi,
You're using an old version of glibc. This issue has been fixed upstream.
Regards,
--
S
On Saturday, September 07, 2013 05:25:56 PM Mark wrote:
> Hi,
>
> While trying to update my Qt build i got this nasty unexpected error:
> http://paste.kde.org/p7c51188c/
Try http://bpaste.net/show/130243/ in qtmultimedia.
Regards,
--
Join us in October at Qt Developer Days 2013 - https://devda
71 matches
Mail list logo