[Development] Qt5 release integration build

Kurt Pattyn pattyn.kurt at gmail.com
Tue Dec 10 20:06:24 CET 2013


I suppose that the warnings in the list beneath are still unsolved. Is that correct?
How critical is it to solve those warnings? If they are critical for the release, I want to give a helping hand to remove them (after all there are more than 900, the list below is a synopsis).
Cheers,

Kurt

On 10 Dec 2013, at 17:30, Mitch Curtis <mitch.curtis at digia.com> wrote:

> https://codereview.qt-project.org/#change,65936
> https://codereview.qt-project.org/#change,66052
> https://codereview.qt-project.org/#change,66018
> https://codereview.qt-project.org/#change,66061
> https://codereview.qt-project.org/#change,66041
> 
> You can see more by searching through gerrit. E.g.:
> 
> https://codereview.qt-project.org/#q,owner:Friedemann.Kleint%2540digia.com+message:warnings,n,z
> 
> or Git:
> 
> git submodule foreach "git log | grep warning ||:"
> 
> Patches are welcome. :)
> 
> On 12/10/2013 11:40 AM, Kurt Pattyn wrote:
>> Hi,
>> 
>> is anybody aware of the many warnings of Qt5 release build for Windows?
>> For instance the build
>> win32-msvc2010_developer-build_qtnamespace_Windows_7 (build log:
>> http://testresults.qt-project.org/ci/Qt5_release_Integration/build_00286/win32-msvc2010_developer-build_qtnamespace_Windows_7/log.txt.gz),
>> contains the following warnings:
>> 
>> warning C4996: 'fopen': This function or variable may be unsafe. Consider using fopen_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
>> 
>> warning C4996: 'strncpy': This function or variable may be unsafe. Consider using strncpy_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
>> 
>> warning C4996: 'strerror': This function or variable may be unsafe. Consider using strerror_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
>> 
>> And a lot more of these ‘unsafe’ warnings, probably harmless.
>> I think the following ones needs more attention:
>> 
>> warning C4018: '>' : signed/unsigned mismatch
>> 
>> warning C4146: unary minus operator applied to unsigned type, result still unsigned
>> 
>> warning C4305: 'argument' : truncation from 'double' to 'float'
>> 
>> warning C4138: '*/' found outside of comment
>> 
>> Command line warning D9025 : overriding '/Zm200' with '/Zm500'
>> 
>> warning C4996: 'putenv': The POSIX name for this item is deprecated. Instead, use the ISO C++ conformant name: _putenv. See online help for details.
>> 
>> warning C4189: 'eventDispatcher' : local variable is initialized but not referenced
>> 
>> testqrc\test.qrc: Warning: potential duplicate alias detected: 'aliasdir.txt'
>> 
>> warning C4341: 'EnumTest_Enum1_bigValue' : signed value is out of range for enum constant
>> 
>> warning C4309: 'initializing' : truncation of constant value
>> 
>> warning C4290: C++ exception specification ignored except to indicate a function is not __declspec(nothrow)
>> 
>> warning C4996: 'FunctionWithAttributes::test2': was declared deprecated
>> 
>> warning C4723: potential divide by 0
>> 
>> warning C4005: 'M_E' : macro redefinition
>> 
>> warning C4530: C++ exception handler used, but unwind semantics are not enabled. Specify /EHsc
>> 
>> warning C4307: '*' : integral constant overflow
>> 
>> warning D9002 : ignoring unknown option '-g'
>> 
>> warning C4995: 'UnknownBaud': name was marked as #pragma deprecated
>> 
>> warning C4244: 'function' : conversion from 'uint64' to 'size_t', possible loss of data
>> 
>> warning C4345: behavior change: an object of POD type constructed with an initializer of the form () will be default-initialized
>> 
>> Cheers,
>> 
>> Kurt
>> 
>> 
>> 
>> _______________________________________________
>> Development mailing list
>> Development at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/development
>> 




More information about the Development mailing list