[Development] Building with Qt 5.11.1 and Visual Studio 2017
We're currently using Qt 5.6 but looking to upgrade soon. I tried building our
app on Qt 5.11.1 with Visual Studio 2017 V15.8.2 and it failed on the first
file:
1>c:\qt\qt5.11.1\5.11.1\msvc2015\include\qtcore\qalgorithms.h(51): error C4430:
missing type specifier - int assumed. Note: C++ does not support default-int
1>c:\qt\qt5.11.1\5.11.1\msvc2015\include\qtcore\qalgorithms.h(51): error C2146:
syntax error: missing ';' before identifier 'QT_WARNING_PUSH'
1>c:\qt\qt5.11.1\5.11.1\msvc2015\include\qtcore\qalgorithms.h(57): error C2143:
syntax error: missing ';' before '{'
1>c:\qt\qt5.11.1\5.11.1\msvc2015\include\qtcore\qalgorithms.h(57): error C2447:
'{': missing function header (old-style formal list?)
1>c:\qt\qt5.11.1\5.11.1\msvc2015\include\qtcore\qalgorithms.h(317): error
C2144: syntax error: 'void' should be preceded by ';'
1>c:\qt\qt5.11.1\5.11.1\msvc2015\include\qtcore\qalgorithms.h(317): error
C2065: 'ForwardIterator': undeclared identifier
1>c:\qt\qt5.11.1\5.11.1\msvc2015\include\qtcore\qalgorithms.h(317): error
C2146: syntax error: missing ')' before identifier 'begin'
1>c:\qt\qt5.11.1\5.11.1\msvc2015\include\qtcore\qalgorithms.h(318): error
C2143: syntax error: missing ';' before '{'
1>c:\qt\qt5.11.1\5.11.1\msvc2015\include\qtcore\qalgorithms.h(318): error
C2447: '{': missing function header (old-style formal list?)
1>c:\qt\qt5.11.1\5.11.1\msvc2015\include\qtcore\qalgorithms.h(685): error
C4430: missing type specifier - int assumed. Note: C++ does not support
default-int
1>c:\qt\qt5.11.1\5.11.1\msvc2015\include\qtcore\qalgorithms.h(685): error
C2146: syntax error: missing ';' before identifier 'Q_DECL_CONSTEXPR'
1>c:\qt\qt5.11.1\5.11.1\msvc2015\include\qtcore\qalgorithms.h(686): error
C2143: syntax error: missing ';' before '{'
1>c:\qt\qt5.11.1\5.11.1\msvc2015\include\qtcore\qalgorithms.h(686): error
C2447: '{': missing function header (old-style formal list?)
1>c:\qt\qt5.11.1\5.11.1\msvc2015\include\qtcore\qalgorithms.h(698): error
C4430: missing type specifier - int assumed. Note: C++ does not support
default-int
1>c:\qt\qt5.11.1\5.11.1\msvc2015\include\qtcore\qalgorithms.h(698): error
C2086: 'int Q_DECL_CONST_FUNCTION': redefinition
1>c:\qt\qt5.11.1\5.11.1\msvc2015\include\qtcore\qalgorithms.h(685): note: see
declaration of 'Q_DECL_CONST_FUNCTION'
(cont)
I searched around and found:
https://forum.qt.io/topic/93714/visual-studio-15-8-0-and-qt-5-11-1-does-not-compile-qrandom-std-aligned_storage
but I've already done a completely clean build. It seems like there are changes
being made here:
https://codereview.qt-project.org/#/c/236948/2/src/corelib/tools/qalgorithms.h
so should I wait for Qt5.11.2?
Tom Isaacson
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] iMX6 EGLGS 2D (QtWidgets) painting acceleration
On Wednesday, 5 September 2018 12:57:39 PDT Uwe Rathmann wrote: > On Wed, 05 Sep 2018 09:55:41 -0700, Thiago Macieira wrote: > >> It also raises questions about the status of the X11 paint engine. > >> Several bugs have been closed because of not fixing the X11 paint > >> engine anymore. > > > > This being the reason why the X11 engine is not good for everyone. > > O.k. - but that does not answer my question regarding the status of the > code ? I'm guessing it's "Experimental, use at your own risk, please report bugs, don't expect quick turnaround time." -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] iMX6 EGLGS 2D (QtWidgets) painting acceleration
On Tuesday, 4 September 2018 23:26:27 PDT André Pönitz wrote: > > Because it's not an important improvement for most people. Your case and > > Denis's, as seen in this thread, are very specific. Most people are > > fine with the raster engine. > > If "Most people do not $X" were a sensible line of reasoning in the > Qt context we could remove pretty much every feature in Qt one-by-one. You're completely right. What I meant to say is that the audience is very restricted, which is why it wasn't announced widely. From what I gather, it's still got a few rough edges, so it wouldn't make sense to announce yet either. As soon as it's usable, it should appear in the ChangeLog. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] iMX6 EGLGS 2D (QtWidgets) painting acceleration
On Wed, 05 Sep 2018 09:55:41 -0700, Thiago Macieira wrote: >> It also raises questions about the status of the X11 paint engine. >> Several bugs have been closed because of not fixing the X11 paint >> engine anymore. > > This being the reason why the X11 engine is not good for everyone. O.k. - but that does not answer my question regarding the status of the code ? Uwe ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] iMX6 EGLGS 2D (QtWidgets) painting acceleration
On Wed, 05 Sep 2018 13:04:39 +0300, Denis Shienkov wrote: > Uwe, wow :) What Qt5 version are you use? Seems to work with Qt5 >= 5.10. Uwe ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] iMX6 EGLGS 2D (QtWidgets) painting acceleration
On Wed, Sep 05, 2018 at 09:55:41AM -0700, Thiago Macieira wrote: > On Wednesday, 5 September 2018 02:29:15 PDT Uwe Rathmann wrote: > > I also googled for QT_XCB_NATIVE_PAINTING without almost no results. I > > understand, that reverting a decision is not stuff for big announcements, > > but for such an important improvement: has it been communicated at least > > somewhere ? > > Because it's not an important improvement for most people. Your case and > Denis's, as seen in this thread, are very specific. Most people are > fine with the raster engine. If "Most people do not $X" were a sensible line of reasoning in the Qt context we could remove pretty much every feature in Qt one-by-one. Most people are *not* using Linux. Most people are *not* using Android. Most people are *not* using iOS. Most people are *not* using Window 7. Most people are *not* using Window 10. ... Most people are *not* using Webkit. Most people are *not* using WebEngine. Most people are *not* using print support. Most people are *not* using 3D ... Most people are *not* using CBOR ... See the pattern? Andre' ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Strange behavior on 5.12 branch and moc genrated file ( KDE application )
On Wednesday, 5 September 2018 09:57:30 PDT Thiago Macieira wrote:
> On Wednesday, 5 September 2018 00:20:22 PDT Helio Chissini de Castro wrote:
> > jsonplugin2.moc:153:1: error: narrowing conversion of ‘'\303'’
> > from ‘char’ to ‘unsigned char’ inside { } [-Wnarrowing]
> > };
>
> [cut]
>
> > lude/jsonplugin2.moc:123:48: error: constant expression evaluates to -61
> > which cannot be narrowed to type 'unsigned char' [-Wc++11-narrowing]
> > ']', 0x76, 'E', 's', 't', 'e', ' ', '\xc3',
> >^~
>
> I guess I didn't test non-ASCII content.
>
> moc was changed recently to save data in CBOR format instead of our binary
> JSON.
Please test this fix:
https://codereview.qt-project.org/238950
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Strange behavior on 5.12 branch and moc genrated file ( KDE application )
On Wednesday, 5 September 2018 00:20:22 PDT Helio Chissini de Castro wrote:
> jsonplugin2.moc:153:1: error: narrowing conversion of ‘'\303'’
> from ‘char’ to ‘unsigned char’ inside { } [-Wnarrowing]
> };
[cut]
> lude/jsonplugin2.moc:123:48: error: constant expression evaluates to -61
> which cannot be narrowed to type 'unsigned char' [-Wc++11-narrowing]
> ']', 0x76, 'E', 's', 't', 'e', ' ', '\xc3',
>^~
I guess I didn't test non-ASCII content.
moc was changed recently to save data in CBOR format instead of our binary
JSON.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] iMX6 EGLGS 2D (QtWidgets) painting acceleration
On Wednesday, 5 September 2018 02:29:15 PDT Uwe Rathmann wrote: > I also googled for QT_XCB_NATIVE_PAINTING without almost no results. I > understand, that reverting a decision is not stuff for big announcements, > but for such an important improvement: has it been communicated at least > somewhere ? Because it's not an important improvement for most people. Your case and Denis's, as seen in this thread, are very specific. Most people are fine with the raster engine. > It also raises questions about the status of the X11 paint engine. > Several bugs have been closed because of not fixing the X11 paint engine > anymore. This being the reason why the X11 engine is not good for everyone. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Strange behavior on 5.12 branch and moc genrated file ( KDE application )
On 9/5/18 2:11 PM, Ville Voutilainen wrote: On 5 September 2018 at 14:42, Helio Chissini de Castro wrote: Unfortunately not. Just compiled again reverting this commit and the issue still there. No ideas for now :-/ Any volunteers to bisect the problem? Most likely https://codereview.qt-project.org/233481 (Plugins: store the metadata in CBOR instead of binary JSON) ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Strange behavior on 5.12 branch and moc genrated file ( KDE application )
On 5 September 2018 at 14:42, Helio Chissini de Castro wrote: > Unfortunately not. > > Just compiled again reverting this commit and the issue still there. > > No ideas for now :-/ Any volunteers to bisect the problem? ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Strange behavior on 5.12 branch and moc genrated file ( KDE application )
Unfortunately not.
Just compiled again reverting this commit and the issue still there.
No ideas for now :-/
On Wed, 5 Sep 2018 at 10:17, Liang Qi wrote:
> Perhaps it's related with https://codereview.qt-project.org/#/c/235352/ .
>
> --Liang
>
> On Wed, 5 Sep 2018 at 09:20, Helio Chissini de Castro
> wrote:
>
>> Morning guys
>>
>> After compile 5.12 branch from yesterday morning, i got one KDE
>> application failing due a compiler error on a generated moc file.
>> Is there any moc relevant change ? I didn't change my compiler
>> environment from previous 5.11 and always compile all in a clean chroot,
>> with no previous versions installed.
>> Qt itself was build with clang 6.0.1
>>
>> Here's the logs
>>
>> With gcc 8.1.1 x86_64:
>>
>> In file included from
>> /code/kde/src/frameworks/kcoreaddons/autotests/jsonplugin2.cpp:23:
>> /code/kde/src/frameworks/kcoreaddons/src/lib/plugin/kpluginfactory.h: In
>> member function ‘void KPluginFactory::registerPlugin(const QString&,
>> KPluginFactory::CreateInstanceFunction) [with T = JsonPlugin2;
>> KPluginFactory::CreateInstanceFunction = QObject* (*)(QWidget*, QObject*,
>> const QList&); QVariantList = QList]’:
>> /code/kde/src/frameworks/kcoreaddons/src/lib/plugin/kpluginfactory.h:487:74:
>> warning: zero as null pointer constant [-Wzero-as-null-pointer-constant]
>> =
>> InheritanceChecker().createInstanceFunction(reinterpret_cast(0)))
>>
>> ^~~~
>> In file included from
>> /code/kde/src/frameworks/kcoreaddons/autotests/jsonplugin2.cpp:34:
>> /code/kde/build-kde/frameworks/kcoreaddons/autotests/jsonplugin2_autogen/include/jsonplugin2.moc:
>> At global scope:
>> /code/kde/build-kde/frameworks/kcoreaddons/autotests/jsonplugin2_autogen/include/jsonplugin2.moc:153:1:
>> error: narrowing conversion of ‘'\303'’ from ‘char’ to ‘unsigned
>> char’ inside { } [-Wnarrowing]
>> };
>> ^
>> /code/kde/build-kde/frameworks/kcoreaddons/autotests/jsonplugin2_autogen/include/jsonplugin2.moc:153:1:
>> error: narrowing conversion of ‘'\3777651'’ from ‘char’ to ‘unsigned
>> char’ inside { } [-Wnarrowing]
>>
>>
>>
>> With clang 6.0.1 x86_64
>>
>> [ 63%] Building CXX object
>> autotests/CMakeFiles/jsonplugin2.dir/jsonplugin2.cpp.o
>> In file included from
>> /code/kde/src/frameworks/kcoreaddons/autotests/jsonplugin2.cpp:34:
>> /code/kde/build-kde/frameworks/kcoreaddons/autotests/jsonplugin2_autogen/include/jsonplugin2.moc:123:48:
>> error: constant expression evaluates to -61
>> which cannot be narrowed to type 'unsigned char' [-Wc++11-narrowing]
>> ']', 0x76, 'E', 's', 't', 'e', ' ', '\xc3',
>>^~
>> /code/kde/build-kde/frameworks/kcoreaddons/autotests/jsonplugin2_autogen/include/jsonplugin2.moc:123:48:
>> note: insert an explicit cast to silence
>> this issue
>> ']', 0x76, 'E', 's', 't', 'e', ' ', '\xc3',
>>^~
>>static_cast> char>( )
>> /code/kde/build-kde/frameworks/kcoreaddons/autotests/jsonplugin2_autogen/include/jsonplugin2.moc:124:5:
>> error: constant expression evaluates to -87
>> which cannot be narrowed to type 'unsigned char' [-Wc++11-narrowing]
>> '\xa9', ' ', 'o', 'u', 't', 'r', 'o', ' ',
>> ^~
>>
>> Any idea ?
>>
>>
>> ___
>> Development mailing list
>> Development@qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/development
>>
>
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Submitting Qt to oss-fuzz
Am 05.09.2018 um 12:40 schrieb Peter Hartmann: > Hello Robert, > > On 04.09.2018 14:03, Robert Löhning wrote: >> I saw your post and it helped me get started. Thanks for that! > > cool, thanks for the feedback! > >> >> By the way: In step 1 you use >> -fsanitize-coverage=edge >> whereas I followed LLVM's example [1] and used >> -fsanitize-coverage=trace-pc-guard >> >> Unfortunately the documentation seems to be a bit scarce. Could you >> please tell me briefly about the advantages of either one? >> >> I guess I should include "edge" to [2], shouldn't I? Instead of >> hacking the mkspec you could then just use >> /configure -sanitize address -coverage edge > > The "-fsanitize-coverage=edge" just comes from an older clang version > when there was no trace-pc-guard. Nowadays "trace-pc-guard" without > other args implies "edge", so the latter can be ignored when configuring > with address sanitizer. > > IIUC edge just provided information on whether a piece of code was > executed or not, while trace-pc-guard provides a callback which allows > for more fine-grained coverage information; the callback itself is then > implemented in libFuzzer. > > What might be interesting to look at is "-fsanitize-coverage=trace-cmp" > though... Definitely interesting, but will it be useful for fuzzing? If I get this right, it will record all different values at comparisons. So, if we take a simple example: if (x == 0) foo() else bar() Then all values of x will be considered different. For fuzzing, though, only the two cases x == 0 and x != 0 will matter. Do I miss something here? Cheers, Robert ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Problems in CI
Hi, You may have noticed that CI is having problems to get build machines and builds seems to be in stuck. This is because machines aren't booting up at all or the booting time is very slow. CI team is investigating the problem Br Heikki Halmet ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Submitting Qt to oss-fuzz
Hello Robert, On 04.09.2018 14:03, Robert Löhning wrote: > I saw your post and it helped me get started. Thanks for that! cool, thanks for the feedback! > > By the way: In step 1 you use > -fsanitize-coverage=edge > whereas I followed LLVM's example [1] and used > -fsanitize-coverage=trace-pc-guard > > Unfortunately the documentation seems to be a bit scarce. Could you > please tell me briefly about the advantages of either one? > > I guess I should include "edge" to [2], shouldn't I? Instead of > hacking the mkspec you could then just use > /configure -sanitize address -coverage edge The "-fsanitize-coverage=edge" just comes from an older clang version when there was no trace-pc-guard. Nowadays "trace-pc-guard" without other args implies "edge", so the latter can be ignored when configuring with address sanitizer. IIUC edge just provided information on whether a piece of code was executed or not, while trace-pc-guard provides a callback which allows for more fine-grained coverage information; the callback itself is then implemented in libFuzzer. What might be interesting to look at is "-fsanitize-coverage=trace-cmp" though... Regards, Peter -- Peter Hartmann // Titurelstrasse 2 // 89125 Munich // Germany pe...@hartmann.tk www.peter.hartmann.tk ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] iMX6 EGLGS 2D (QtWidgets) painting acceleration
> Using Qwt with a current Qt version seems to run the same ways as with Qt4/X11 without any problems. Uwe, wow :) What Qt5 version are you use? Denis ср, 5 сент. 2018 г. в 12:31, Uwe Rathmann : > On Wed, 05 Sep 2018 09:56:36 +0100, Sérgio Martins via Development wrote: > > >> What needs to be done to make it become effective ? > > > > export QT_XCB_NATIVE_PAINTING=1 > > I did a quick check with using QPainter on a QPixmap and indeed it runs > the X11 paint engine. Using Qwt with a current Qt version seems to run > the same ways as with Qt4/X11 without any problems. > > So this is great news - at least for me, others might be aware of this > option for a longer time. > > I also googled for QT_XCB_NATIVE_PAINTING without almost no results. I > understand, that reverting a decision is not stuff for big announcements, > but for such an important improvement: has it been communicated at least > somewhere ? > > It also raises questions about the status of the X11 paint engine. > Several bugs have been closed because of not fixing the X11 paint engine > anymore. > > Does it make sense to write bug reports, when it behaves not according to > the specs - or when it differs from what the raster paint engine does ? > > Uwe > > ___ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development > ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] iMX6 EGLGS 2D (QtWidgets) painting acceleration
On Wed, 05 Sep 2018 09:56:36 +0100, Sérgio Martins via Development wrote: >> What needs to be done to make it become effective ? > > export QT_XCB_NATIVE_PAINTING=1 I did a quick check with using QPainter on a QPixmap and indeed it runs the X11 paint engine. Using Qwt with a current Qt version seems to run the same ways as with Qt4/X11 without any problems. So this is great news - at least for me, others might be aware of this option for a longer time. I also googled for QT_XCB_NATIVE_PAINTING without almost no results. I understand, that reverting a decision is not stuff for big announcements, but for such an important improvement: has it been communicated at least somewhere ? It also raises questions about the status of the X11 paint engine. Several bugs have been closed because of not fixing the X11 paint engine anymore. Does it make sense to write bug reports, when it behaves not according to the specs - or when it differs from what the raster paint engine does ? Uwe ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Merge and Integration status report - 2018.09.05
Integrations * qt5 5.11/5.11.2/5.12 integrations are healthy, finally for 5.12 * qt5 dev, 5.12->dev merge + dev submodule update integration just started, let's see COIN is a bit slow recently, the difference between backend vm numbers and coin running numbers is a bit too much. Colleagues are working on that. During this period, perhaps qmake timeout issue is very common on all platforms, including Linux, Windows and macOS. -- Liang ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] iMX6 EGLGS 2D (QtWidgets) painting acceleration
On 2018-09-05 06:58, Uwe Rathmann wrote: On Tue, 04 Sep 2018 20:51:38 +0200, Martin Koller wrote: added the native X11 graphicssystem support from Qt4 to Qt5 Very cool. Andrew told me that there were 2 concurrent attempts to revive X11 as the situation for running widget applications on remote desktops is simply not good, when using Raster. But I never realized, that finally something went into the Qt code base. What needs to be done to make it become effective ? export QT_XCB_NATIVE_PAINTING=1 Regards, -- Sérgio Martins | sergio.mart...@kdab.com | Senior Software Engineer Klarälvdalens Datakonsult AB, a KDAB Group company Tel: Sweden (HQ) +46-563-540090, USA +1-866-777-KDAB(5322) KDAB - The Qt, C++ and OpenGL Experts ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] iMX6 EGLGS 2D (QtWidgets) painting acceleration
Hi, > added the native X11 graphicssystem support from Qt4 to Qt5 According to that commit (and next depends commits), seems this porting is not completed yet to Qt5. So, it is interest to know: can we use it in current time, and since what of Qt version? Is it work at all as in Qt4? And, as Uwe said: how we can enable this feature, what needs to do? Denis ср, 5 сент. 2018 г. в 9:01, Uwe Rathmann : > On Tue, 04 Sep 2018 20:51:38 +0200, Martin Koller wrote: > > > added the native X11 graphicssystem support from Qt4 to Qt5 > > Very cool. > > Andrew told me that there were 2 concurrent attempts to revive X11 as the > situation for running widget applications on remote desktops is simply > not good, when using Raster. But I never realized, that finally something > went into the Qt code base. > > What needs to be done to make it become effective ? > > Uwe > > > ___ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development > ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Strange behavior on 5.12 branch and moc genrated file ( KDE application )
Perhaps it's related with https://codereview.qt-project.org/#/c/235352/ .
--Liang
On Wed, 5 Sep 2018 at 09:20, Helio Chissini de Castro wrote:
> Morning guys
>
> After compile 5.12 branch from yesterday morning, i got one KDE
> application failing due a compiler error on a generated moc file.
> Is there any moc relevant change ? I didn't change my compiler environment
> from previous 5.11 and always compile all in a clean chroot, with no
> previous versions installed.
> Qt itself was build with clang 6.0.1
>
> Here's the logs
>
> With gcc 8.1.1 x86_64:
>
> In file included from
> /code/kde/src/frameworks/kcoreaddons/autotests/jsonplugin2.cpp:23:
> /code/kde/src/frameworks/kcoreaddons/src/lib/plugin/kpluginfactory.h: In
> member function ‘void KPluginFactory::registerPlugin(const QString&,
> KPluginFactory::CreateInstanceFunction) [with T = JsonPlugin2;
> KPluginFactory::CreateInstanceFunction = QObject* (*)(QWidget*, QObject*,
> const QList&); QVariantList = QList]’:
> /code/kde/src/frameworks/kcoreaddons/src/lib/plugin/kpluginfactory.h:487:74:
> warning: zero as null pointer constant [-Wzero-as-null-pointer-constant]
> =
> InheritanceChecker().createInstanceFunction(reinterpret_cast(0)))
>
> ^~~~
> In file included from
> /code/kde/src/frameworks/kcoreaddons/autotests/jsonplugin2.cpp:34:
> /code/kde/build-kde/frameworks/kcoreaddons/autotests/jsonplugin2_autogen/include/jsonplugin2.moc:
> At global scope:
> /code/kde/build-kde/frameworks/kcoreaddons/autotests/jsonplugin2_autogen/include/jsonplugin2.moc:153:1:
> error: narrowing conversion of ‘'\303'’ from ‘char’ to ‘unsigned
> char’ inside { } [-Wnarrowing]
> };
> ^
> /code/kde/build-kde/frameworks/kcoreaddons/autotests/jsonplugin2_autogen/include/jsonplugin2.moc:153:1:
> error: narrowing conversion of ‘'\3777651'’ from ‘char’ to ‘unsigned
> char’ inside { } [-Wnarrowing]
>
>
>
> With clang 6.0.1 x86_64
>
> [ 63%] Building CXX object
> autotests/CMakeFiles/jsonplugin2.dir/jsonplugin2.cpp.o
> In file included from
> /code/kde/src/frameworks/kcoreaddons/autotests/jsonplugin2.cpp:34:
> /code/kde/build-kde/frameworks/kcoreaddons/autotests/jsonplugin2_autogen/include/jsonplugin2.moc:123:48:
> error: constant expression evaluates to -61
> which cannot be narrowed to type 'unsigned char' [-Wc++11-narrowing]
> ']', 0x76, 'E', 's', 't', 'e', ' ', '\xc3',
>^~
> /code/kde/build-kde/frameworks/kcoreaddons/autotests/jsonplugin2_autogen/include/jsonplugin2.moc:123:48:
> note: insert an explicit cast to silence
> this issue
> ']', 0x76, 'E', 's', 't', 'e', ' ', '\xc3',
>^~
>static_cast(
> )
> /code/kde/build-kde/frameworks/kcoreaddons/autotests/jsonplugin2_autogen/include/jsonplugin2.moc:124:5:
> error: constant expression evaluates to -87
> which cannot be narrowed to type 'unsigned char' [-Wc++11-narrowing]
> '\xa9', ' ', 'o', 'u', 't', 'r', 'o', ' ',
> ^~
>
> Any idea ?
>
>
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
[Development] Strange behavior on 5.12 branch and moc genrated file ( KDE application )
Morning guys
After compile 5.12 branch from yesterday morning, i got one KDE application
failing due a compiler error on a generated moc file.
Is there any moc relevant change ? I didn't change my compiler environment
from previous 5.11 and always compile all in a clean chroot, with no
previous versions installed.
Qt itself was build with clang 6.0.1
Here's the logs
With gcc 8.1.1 x86_64:
In file included from
/code/kde/src/frameworks/kcoreaddons/autotests/jsonplugin2.cpp:23:
/code/kde/src/frameworks/kcoreaddons/src/lib/plugin/kpluginfactory.h: In
member function ‘void KPluginFactory::registerPlugin(const QString&,
KPluginFactory::CreateInstanceFunction) [with T = JsonPlugin2;
KPluginFactory::CreateInstanceFunction = QObject* (*)(QWidget*, QObject*,
const QList&); QVariantList = QList]’:
/code/kde/src/frameworks/kcoreaddons/src/lib/plugin/kpluginfactory.h:487:74:
warning: zero as null pointer constant [-Wzero-as-null-pointer-constant]
=
InheritanceChecker().createInstanceFunction(reinterpret_cast(0)))
^~~~
In file included from
/code/kde/src/frameworks/kcoreaddons/autotests/jsonplugin2.cpp:34:
/code/kde/build-kde/frameworks/kcoreaddons/autotests/jsonplugin2_autogen/include/jsonplugin2.moc:
At global scope:
/code/kde/build-kde/frameworks/kcoreaddons/autotests/jsonplugin2_autogen/include/jsonplugin2.moc:153:1:
error: narrowing conversion of ‘'\303'’ from ‘char’ to ‘unsigned
char’ inside { } [-Wnarrowing]
};
^
/code/kde/build-kde/frameworks/kcoreaddons/autotests/jsonplugin2_autogen/include/jsonplugin2.moc:153:1:
error: narrowing conversion of ‘'\3777651'’ from ‘char’ to ‘unsigned
char’ inside { } [-Wnarrowing]
With clang 6.0.1 x86_64
[ 63%] Building CXX object
autotests/CMakeFiles/jsonplugin2.dir/jsonplugin2.cpp.o
In file included from
/code/kde/src/frameworks/kcoreaddons/autotests/jsonplugin2.cpp:34:
/code/kde/build-kde/frameworks/kcoreaddons/autotests/jsonplugin2_autogen/include/jsonplugin2.moc:123:48:
error: constant expression evaluates to -61
which cannot be narrowed to type 'unsigned char' [-Wc++11-narrowing]
']', 0x76, 'E', 's', 't', 'e', ' ', '\xc3',
^~
/code/kde/build-kde/frameworks/kcoreaddons/autotests/jsonplugin2_autogen/include/jsonplugin2.moc:123:48:
note: insert an explicit cast to silence
this issue
']', 0x76, 'E', 's', 't', 'e', ' ', '\xc3',
^~
static_cast( )
/code/kde/build-kde/frameworks/kcoreaddons/autotests/jsonplugin2_autogen/include/jsonplugin2.moc:124:5:
error: constant expression evaluates to -87
which cannot be narrowed to type 'unsigned char' [-Wc++11-narrowing]
'\xa9', ' ', 'o', 'u', 't', 'r', 'o', ' ',
^~
Any idea ?
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] iMX6 EGLGS 2D (QtWidgets) painting acceleration
On Tue, 04 Sep 2018 20:51:38 +0200, Martin Koller wrote: > added the native X11 graphicssystem support from Qt4 to Qt5 Very cool. Andrew told me that there were 2 concurrent attempts to revive X11 as the situation for running widget applications on remote desktops is simply not good, when using Raster. But I never realized, that finally something went into the Qt code base. What needs to be done to make it become effective ? Uwe ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
