On Wednesday 24 of June 2015 14:03:07 Zhang Qun wrote:
> QMetaType::registerType: Binary compatibility break -- Size mismatch for
> type 'QPaintBufferCacheEntry' [1024]. Previously registered size 0, now
> registering size 16.
Hi,
It looks like a build issue, qt library version mismatch... Does
On Wednesday 24 June 2015 14:03:07 Zhang Qun wrote:
> #4 0x7677dc5a in ?? () from
> /home/zq/Qt5.4.0/5.4/gcc_64/lib/libQt5Gui.so.5
We need to know what this ?? is. Please recompile in debug mode and rerun.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel O
Dear all
I manage to compile my code with Qt 5 but when I run the program and
encountered the following error:
QMetaType::registerType: Binary compatibility break -- Size mismatch for
type 'QPaintBufferCacheEntry' [1024]. Previously registered size 0, now
registering size 16.
Aborted (core dump
On Tuesday 23 June 2015 22:01:27 Thiago Macieira wrote:
> On Tuesday 23 June 2015 18:47:47 Giuseppe D'Angelo wrote:
> > Random thought: call it Qt 6? :-P
>
> Let's not.
I agree. Qt 5 required full C++98 support, IMO, Qt 6 should require full C++11
support, maybe C++14, and that's still far, far
On Tuesday 23 June 2015 18:47:47 Giuseppe D'Angelo wrote:
> Random thought: call it Qt 6? :-P
Let's not.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing list
Develop
On 23/06/15 20:56, "Konstantin Ritt"
mailto:ritt...@gmail.com>> wrote:
2015-06-23 20:47 GMT+04:00 Giuseppe D'Angelo
mailto:dange...@gmail.com>>:
On Tue, Jun 23, 2015 at 12:17 PM, Knoll Lars
mailto:lars.kn...@theqtcompany.com>> wrote:
> Qt 5.7:
>
> * New compiler baseline with gcc 4.7 and VC++ 2
2015-06-23 20:47 GMT+04:00 Giuseppe D'Angelo :
> On Tue, Jun 23, 2015 at 12:17 PM, Knoll Lars
> wrote:
> > Qt 5.7:
> >
> > * New compiler baseline with gcc 4.7 and VC++ 2012
> > * Enable and use the C++11 features supported by these compilers
> > unconditionally
> > * WEC7 not supported anymore,
On Tue, Jun 23, 2015 at 12:17 PM, Knoll Lars
wrote:
> Qt 5.7:
>
> * New compiler baseline with gcc 4.7 and VC++ 2012
> * Enable and use the C++11 features supported by these compilers
> unconditionally
> * WEC7 not supported anymore, WEC2013 supported
> * Probably remove support for older Android,
On Tuesday 23 June 2015 19:07:12 Marc Mutz wrote:
> On Tuesday 23 June 2015 15:12:36 Mike Krus wrote:
> > Hi
> >
> > while investigating crashes in QAtomicInteger on iOS, I was
> > wondering why the default is not the use the C++11 implementation if it’s
> > available? In particular, in qbasicatom
On Tuesday 23 June 2015 15:12:36 Mike Krus wrote:
> Hi
>
> while investigating crashes in QAtomicInteger on iOS, I was
> wondering why the default is not the use the C++11 implementation if it’s
> available? In particular, in qbasicatomic.h, the asm-based implementations
> are preferred for all ar
On Tuesday 23 June 2015 14:12:36 Mike Krus wrote:
> Hi
>
> while investigating crashes in QAtomicInteger on iOS, I was
> wondering why the default is not the use the C++11 implementation if it’s
> available?
Because the quality of the implementation varies a lot. They first showed up in
GCC 4.6
On Tuesday 23 June 2015 10:17:40 Knoll Lars wrote:
> Qt 5.6:
>
> * We make 5.6 a long term supported release
> * We still support C++98 compilers in this release (for the last time),
> i.e. We keep the 5.5 compiler baseline
> * WEC7 will be still supported
> * QNX 6.5 is not supported anymore
> *
Hi
while investigating crashes in QAtomicInteger on iOS, I was wondering
why the default is not the use the C++11 implementation if it’s available?
In particular, in qbasicatomic.h, the asm-based implementations are preferred
for all arm platforms (and others).
Shouldn’t the version using std::a
Hi all,
We are quite close to releasing Qt 5.5.0 final so it is good time to start
thinking & writing down the lessons learnt from that release.
We are so much late so there should be pretty much thing to be improved at
least. I have created a wiki page for collecting the information, see
ht
Hi,
we're currently working on a 3D showcase game of the new Qt3D module.
When loading a Mesh (.obj format) and applying a texture with
DiffuseMapMaterial, the texture is not applied correctly though. I've
tried several different objects and none of them work.
Any pointers what could cause this
Hi,
I’ve went through the plans that we now have for Qt 5.6 and think that we
need to slightly adjust our plans to deprecate certain compilers and move
over to C++11.
We are currently around 6 weeks away from the 5.6 feature freeze, and
currently the dev branch is still nicely compiling in C++98
Hi folks,
I'm a happy user of qtscriptgenerator and I was wondering if there is
anywhere online a short documentation that would explain how I can write
a xml for one of my own class and feed it to the generator.
It is surprising how powerful this tool is, yet there's no resource
available onli
As promised in the talk, I moved the qmlbench tool to a separate repo and gave
it a readme: https://github.com/sletta/qmlbench
Still under my github account, but now it is at least documented so others can
take part in interpreting the results.
> On 22 Jun 2015, at 14:47, Robin Burchell wrot
18 matches
Mail list logo
