On 6 December 2013 19:30, Smith Martin wrote:
> Should I report these warnings in JIRA?
Yes, please.
--
Giuseppe D'Angelo
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Well, yes, I fix the ones that are errors, but I have seen many warnings that
are just warnings.
I saw an uninitialized variable in one of the Qt hash collections, but I
haven't seen that one lately, so someone might have fixed it.
I can't recall the others at the moment. I have been ignoring
On sexta-feira, 6 de dezembro de 2013 17:18:02, Smith Martin wrote:
> I get warnings with clang in OSX. It even treats an unused variable as an
> error.
Which makes you fix them, so we don't get warnings in the repository :-)
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architec
I get warnings with clang in OSX. It even treats an unused variable as an error.
martin
From: development-bounces+martin.smith=digia@qt-project.org
[development-bounces+martin.smith=digia@qt-project.org] on behalf of Thiago
Macieira [thiago.macie.
On sexta-feira, 6 de dezembro de 2013 11:16:20, Kurt Pattyn wrote:
> When compiling applications with compiler flags on, a lot of warnings are
> generated for the Qt header files. I
Which compiler? Which warnings?
We're not supposed to have any warnings with GCC or Clang.
--
Thiago Macieira - th
On sexta-feira, 6 de dezembro de 2013 13:41:34, Olivier Goffart wrote:
> There used to be a 'compilerwarnings' autotest that made sure there was no
> warning in the headers (in a more strict ways that the warnings we check
> while compiling Qt itself). But i think it's gone.
I still have a pend
Hi all,
We have new qt 5.2 snapshot available here:
http://download.qt-project.org/snapshots/qt/5.2/5.2.0/2013-12-06_200/
These packages are considered to be really close to final release packages so
please test these and report your testing effort via
http://testresults.qt-project.org/forms
> -Original Message-
> From: Smith Martin
> Sent: Friday, December 06, 2013 4:35 PM
> To: Koehne Kai; development@qt-project.org
> Subject: RE: Changed qdebug stream operator output (qtbase/dev)
>
> I will miss it. Why did we take it out? Now I have to put << " " everywhere.
I'm not sure
On Friday 6. December 2013 15.34.33 Smith Martin wrote:
> I will miss it. Why did we take it out? Now I have to put << " " everywhere.
No, the change merely removes the _trailing_ space. That added little value :)
Simon
>
> From: development-bounces+mart
I will miss it. Why did we take it out? Now I have to put << " " everywhere.
martin
From: development-bounces+martin.smith=digia@qt-project.org
[development-bounces+martin.smith=digia@qt-project.org] on behalf of Koehne
Kai [kai.koe...@digia.com]
Hi,
Just a small heads-up: I just managed to merge change
https://codereview.qt-project.org/#change,69731 in qtbase , dev branch. That
change gets rid of the trailing space that was added for every qDebug() << ;
statement. I guess nobody will really miss it ... but it might be that there
are s
On 12/06/2013 03:08 PM, Mark Gaiser wrote:
> On Fri, Dec 6, 2013 at 2:02 PM, Mitch Curtis wrote:
>> Hello.
>>
>> At the beginning of this year I started work on a Calendar for Qt Quick
>> Controls as a sort of side project. After removing the "WIP" from the
>> commit message, I got some feedback f
> -Original Message-
> C:/repo/mingw-w64-qt-creator/src/qt-creator-opensource-src-3.0.0-
> rc1/src/plugins/ios/iosdebugsupport.cpp:165:68:
> error: cast from 'Q_PID {aka _PROCESS_INFORMATION*}' to 'int' loses
> precision [-fpermissive]
> m_runControl->engine()->notifyEngineRemoteSe
On Fri, Dec 6, 2013 at 2:02 PM, Mitch Curtis wrote:
> Hello.
>
> At the beginning of this year I started work on a Calendar for Qt Quick
> Controls as a sort of side project. After removing the "WIP" from the
> commit message, I got some feedback from developers who either a) had
> also wrote a Ca
Hello.
At the beginning of this year I started work on a Calendar for Qt Quick
Controls as a sort of side project. After removing the "WIP" from the
commit message, I got some feedback from developers who either a) had
also wrote a Calendar for KDE stuff or b) suggested I ask for feedback
from
On Friday 06 December 2013 11:16:20 Kurt Pattyn wrote:
> When compiling applications with compiler flags on, a lot of warnings are
> generated for the Qt header files. It needs a lot of work to exclude them
> in our builds, and some of them can just not be excluded because they are
> located in mac
Hi!
I'm try to build 64-bit QtCreator-3.0.0-rc1 with mingw-w64 GCC-4.8.2
toolchain and got cast error:
C:/repo/mingw-w64-qt-creator/src/qt-creator-opensource-src-3.0.0-rc1/src/plugins/ios/iosdebugsupport.cpp:
In member function 'void
Ios::Internal::IosDebugSupport::handleGotInferiorPid(Q_PID)':
C
> From: Oswald Buddenhagen
> Subject: Re: [Development] [Request] Compiler warnings in Qt
> Date: 6 Dec 2013 11:56:48 GMT+1
> To:
>
>
> the solution to that would be
> https://bugreports.qt-project.org/browse/QTBUG-7220
Well that would at least be a solution, albeit a poor man’s solution. Aft
On Fri, Dec 06, 2013 at 11:16:20AM +0100, Kurt Pattyn wrote:
> When compiling applications with compiler flags on, a lot of warnings are
> generated for the Qt header files.
> It needs a lot of work to exclude them in our builds, and some of them can
> just not be excluded because they are locate
When compiling applications with compiler flags on, a lot of warnings are
generated for the Qt header files.
It needs a lot of work to exclude them in our builds, and some of them can just
not be excluded because they are located in macros or inline methods.
The same holds for the moc generated c
It is similar to that one, although a resize call won't solve it in my case.
But the situation is same as what David Eller wrote in his comment.
After a makeCurrent() call, QGLContext::currentContext() and
QGLWidget::context() won't be the same.
I forgot to mention that i use Win7, with msvc 11.0.
21 matches
Mail list logo
