On Monday 03 September 2012 00:13:50 Thiago Macieira wrote:
> On segunda-feira, 3 de setembro de 2012 00.02.09, Olivier Goffart wrote:
> > On Sunday 02 September 2012 22:43:33 Laszlo Papp wrote:
> > > > It would be nice to have clang in the CI system.
> > >
> > > I had the impression, clang is alr
Sergio Ahumada said:
> Hi,
>
> We've found that Windows 7 machines are not up and running at the moment
> so we've decided to disable them from Qt Project CI system until we can
> fix them.
>
> This means that you might need to be a little bit more careful with what
> you stage during the week
On segunda-feira, 3 de setembro de 2012 00.02.09, Olivier Goffart wrote:
> On Sunday 02 September 2012 22:43:33 Laszlo Papp wrote:
> > > It would be nice to have clang in the CI system.
> >
> > I had the impression, clang is already in there:
> > http://testresults.qt-project.org/ci/QtBase_master_I
On Sunday 02 September 2012 22:43:33 Laszlo Papp wrote:
> > It would be nice to have clang in the CI system.
>
> I had the impression, clang is already in there:
> http://testresults.qt-project.org/ci/QtBase_master_Integration/latest-succes
> s/ http://qt-project.org/wiki/CI_Configurations
>
> La
On domingo, 2 de setembro de 2012 23.27.34, Sylvain Pointeau wrote:
> > > error: no matching function for call to 'qHash'
> > >
> > > Q_DECL_NOEXCEPT_EXPR(noexcept(qHash(t)))
> >
> > We're not sure if this error is in clang or in our use of noexcept.
>
> How can I disable it for now?
Remove th
>
> It would be nice to have clang in the CI system.
>
I had the impression, clang is already in there:
http://testresults.qt-project.org/ci/QtBase_master_Integration/latest-success/
http://qt-project.org/wiki/CI_Configurations
Laszlo
___
Development ma
On 09/02/2012 11:36 PM, Olivier Goffart wrote:
> On Sunday 02 September 2012 19:51:21 Thiago Macieira wrote:
>> On domingo, 2 de setembro de 2012 19.25.45, Sylvain Pointeau wrote:
>>> clang and libc++ are the only way to use c++11 on mac os x.
>>> I think it is important to have it enable on mac os
On Sunday 02 September 2012 19:51:21 Thiago Macieira wrote:
> On domingo, 2 de setembro de 2012 19.25.45, Sylvain Pointeau wrote:
> > clang and libc++ are the only way to use c++11 on mac os x.
> > I think it is important to have it enable on mac os x users.
> > Do you plan to support it in qt5 rel
>
> > error: no matching function for call to 'qHash'
> > Q_DECL_NOEXCEPT_EXPR(noexcept(qHash(t)))
>
> We're not sure if this error is in clang or in our use of noexcept.
>
>
How can I disable it for now?
___
Development mailing list
Development@qt-pr
On domingo, 2 de setembro de 2012 21.45.57, Sylvain Pointeau wrote:
> error: no matching function for call to 'qHash'
> Q_DECL_NOEXCEPT_EXPR(noexcept(qHash(t)))
We're not sure if this error is in clang or in our use of noexcept.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Ar
On Sun, Sep 2, 2012 at 7:51 PM, Thiago Macieira
wrote:
> On domingo, 2 de setembro de 2012 19.25.45, Sylvain Pointeau wrote:
> > clang and libc++ are the only way to use c++11 on mac os x.
> > I think it is important to have it enable on mac os x users.
> > Do you plan to support it in qt5 release
On domingo, 2 de setembro de 2012 21.08.34, Michael wrote:
> > Hi All,
> >
> > I noticed in qt5 beta1 debugging in Visual Studio 2010 i cannot see the
> > value of QString anymore, just member 'd' address. In 4.8 i could see the
> > string value fex "hello".
> >
> > Is this by design now or am i do
>
> What you're hitting is a bug in qemu while trying to execute mksnapshot,
> which is trying to fire up the v8 engine. What's strange though is that
> configure should detect that you're building inside scratchbox and disable
> v8 snapshots accordingly.
It is also strange that it does not work
Hi,
What you're hitting is a bug in qemu while trying to execute mksnapshot, which
is trying to fire up the v8 engine. What's strange though is that
configure should detect that you're building inside scratchbox and disable v8
snapshots accordingly. Are you building outside of scratchbox? What's
Hi all,
When building Qt 5 on big endian host (PPC) I've found moc breaking on Qt
classes containing Q_PLUGIN_METADATA with
ASSERT: "idx >= 0 && idx < s" in file
../../../include/QtCore/../../src/corelib/tools/qvarlengtharray.h, line 111
It turned out to be a fault of QJsonPrivate::Parser::par
> Hi All,
>
> I noticed in qt5 beta1 debugging in Visual Studio 2010 i cannot see the value
> of QString anymore, just member 'd' address. In 4.8 i could see the string
> value fex "hello".
>
> Is this by design now or am i doing something wrong? I built qt5 from source.
>
> Thanks,
> Mike
Hi,
There is a problem on Harmattan when building the declarative module (Qt5,
beta1) natively, so without the -platform maemo: for qtdeclarative build:
Project ERROR: Unknown module(s) in QT_PRIVATE: v8.
The QtJsBackend package was installed into /opt/qt5.
/opt/qt5/mkspecs/modules/qt_v8.pri is a
On domingo, 2 de setembro de 2012 19.25.45, Sylvain Pointeau wrote:
> clang and libc++ are the only way to use c++11 on mac os x.
> I think it is important to have it enable on mac os x users.
> Do you plan to support it in qt5 release?
$ ls -1d mkspecs/macx-clang*
mkspecs/macx-clang
mkspecs/macx
02.09.2012, 21:25, "Sylvain Pointeau" :
> clang and libc++ are the only way to use c++11 on mac os x.
Not really - FSF GCC is another way.
It seems to be binary incompatible with Apple's compilers though.
--
Regards,
Konstantin
___
Development mailing
clang and libc++ are the only way to use c++11 on mac os x.
I think it is important to have it enable on mac os x users.
Do you plan to support it in qt5 release?
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/
20 matches
Mail list logo
