[vbox-dev] Răspuns: Building QT5 for VirtualBox on windows

Mikhail Kovalev mikhail.kovalev at gmail.com
Wed Jul 20 15:07:53 UTC 2016

Hello Mihai,

thnx for your feedback. I did build QT4 with integrity check, but I also
used a workaround there (building individual VS projects rather than
running a complete build). I guess the best option for QT5 is indeed to do
the signing of the dlls and then re-run the build.


On Wed, Jul 20, 2016 at 11:04 AM Mihai Hanor <mhanor at yahoo.com> wrote:

> Hello,
> Have you build Qt4 with integritycheck? Even with Qt4, you had to manually
> sign at least one Qt tool to continue building Qt. Edit
> qtbase\mkspecs\common\msvc-desktop.conf (adding /integritycheck) and
> manually sign what you need to continue the build process.
> ------------------------------
> *De la:* Mikhail Kovalev <mikhail.kovalev at gmail.com>
> *Către:* VirtualBox developer's list <vbox-dev at virtualbox.org>
> *Trimis:* Miercuri, 20 Iulie 2016 11:45:15
> *Subiect:* [vbox-dev] Building QT5 for VirtualBox on windows
> Hi,
> since version 5.1.0 VirtualBox is now using QT5 by default for Windows
> builds.
> Can anyone give an advice on how to build QT5 libs with integrity check
> enabled on windows?
> I tried to follow similar steps as described here:
> https://forums.virtualbox.org/viewtopic.php?f=10&t=73799,
> but it doesn't work for QT5. The build process builds "uic.exe" and links
> it against the (already built) QtCore5.dll. The dll is built with the
> integrity check turned on but it is obviously not signed yet (because the
> build process of QT doesn't sign libs). As a result, "uic.exe" cannot load
> QtCore5.dll and the build fails.
> Any hint on how to build these libs with the integrity check enabled would
> be helpful.
> Best regards,
> Mikhail
> _______________________________________________
> vbox-dev mailing list
> vbox-dev at virtualbox.org
> https://www.virtualbox.org/mailman/listinfo/vbox-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.virtualbox.org/pipermail/vbox-dev/attachments/20160720/781c5c2f/attachment.html>

More information about the vbox-dev mailing list