The verification of the change series that removed VS 2013 and follow
-up changes, is flaky, e.g.: https://gerrit.libreoffice.org/#/c/23199/
tb73: is correctly detects MSVC 14.0:
checking Visual C++... checking whether vs inst is 14.0 15.0...
checking ver is now: 14.0... C:/PROGRA~2/MICROS~3.0/VC/
but failing with "(implementation limitation)":
C:/cygwin/home/tdf/lode/jenkins/workspace/lo_gerrit/Config/windows_msc_
dbgutil_32/vcl/source/app/IconThemeInfo.cxx(19): error C2220: warning
treated as error - no 'object' file generated
C:/cygwin/home/tdf/lode/jenkins/workspace/lo_gerrit/Config/windows_msc_
dbgutil_32/vcl/source/app/IconThemeInfo.cxx(19): warning C4592:
'HIGH_CONTRAST_ID': symbol will be dynamically initialized
(implementation limitation)
However, on tb77, that also correctly detects MSVC 14.0:
checking Visual C++... checking whether vs inst is 14.0 15.0...
checking ver is now: 14.0... C:/PROGRA~2/MICROS~3.0/VC/
for the same change series:
https://gerrit.libreoffice.org/#/c/22588/16
this implementation limitation bug isn't reported:
http://ci.libreoffice.org/job/lo_gerrit/7192/Config=windows_msc_dbgutil
_32/
I also cannot reproduce the problem in MSVC 14.0, update 3 and on MSVC
15.0 RC3. All is fine, even with --enable-werror on both compilers.
Conclusion: tb73 and probably other TBs need to be upgraded to the
latest MSVC 2015 update 3.
Context
- Can tb73 be upgraded to VS 2015 Update 3, to avoid false negative? · David Ostrovsky
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.