Bingo! That appears to have been the problem. Just like the report, I too
was using jom, and when I changed my expert-knowledge build script to force
nmake for static builds, it breezed through the 32-bit static release build
with no problems. Why this wasn't encountered with 64-bit static I don't
know, but it certainly appears to have been the exact problem preventing the
32-bit static build from completing.
Thanks so much, Mike. :)
On 7/7/2016 10:10 AM, Mike Chinander wrote:
Looks like it could be related to this bug report:
https://bugreports.qt.io/browse/QTBUG-53393
Did you try re-running nmake/jom after you got this error?
On Thu, Jul 7, 2016 at 10:57 AM, Bob Hood <bho...@comcast.net
<mailto:bho...@comcast.net>>wrote:
I'm trying to build Qt 5.6.1-1 32-bit licensed static using Visual
Studio 2013. I am configuring with the following command:
configure -commercial -confirm-license -static -prefix
Q:\Qt\5.6.1\32_static -mp -release -nomake examples -no-qml-debug
-no-compile-examples -nomake tests -opengl desktop
I have successfully built 64-bit versions, static and DLL, licensed and
open source, with similar config commands just prior to attempting the
32-bit builds. At some point in the 32-bit build, I'm getting:
LINK : fatal error LNK1181: cannot open input file
'D:\Qt\build\32_static\qtimageformats\plugins\imageformats\qwebp.lib'
I read that the webkit had been removed from the 5.6 distribution (I'm
using the source tarballs), but it looks like there's some kind of
dependency upon it anyway. I configured the 64-bit builds with ICU, but
I did not with 32-bit because we don't want the webkit builds in the
32-bit static. I tried adding the '-skip qtwebkit' command (which works
fine for prior Qt versions), but then I get the different build error:
Attempting to skip non-existent module qtwebkit.
Error: File Makefile doesn't exist.
Removing '-skip qtwebkit' from the config line leads me to the link
error with the image format plug-in.
Do I now need to provide ICU to the 32-bit builds even though we
/aren't/building the webkit module, or is there some new means of
disabling the webkit as part of that type of build?I'd appreciate any
insights here.
_______________________________________________
Interest mailing list
Interest@qt-project.org <mailto:Interest@qt-project.org>
http://lists.qt-project.org/mailman/listinfo/interest
_______________________________________________
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
_______________________________________________
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
