Hi, just verified that a Qt configured like this -nomake examples -nomake tests -static -no-icu
compiles and applications launched successfully via Explorer double-click, both widgets and qtquick2 based. That was against the stable branch, but I am sure it should work for 5.2 etc as well. Maurice -----Ursprüngliche Nachricht----- Von: [email protected] [mailto:[email protected]] Im Auftrag von Kalinowski Maurice Gesendet: Dienstag, 15. April 2014 07:45 An: [email protected]; Qt Project MailingList Betreff: Re: [Interest] Qt 5.2/5.3 Windows - fully static? Hi, static compilation should work as you described it. If you configured with -static then the plugins get compiled into your application in the end. It was the same in Qt4 times for imageformats etc. There might be some tweaks required in regards to ICU, others can comment on that. If this is not working for you, please verify that against 5.3beta or the upcoming 5.3 RC and create a bug-report asap. BR, Maurice -----Ursprüngliche Nachricht----- Von: [email protected] [mailto:[email protected]] Im Auftrag von Paul Miller Gesendet: Montag, 14. April 2014 17:42 An: Qt Project MailingList Betreff: [Interest] Qt 5.2/5.3 Windows - fully static? I am a commercial customer and have some self-contained tools that I have built with Qt 4.8 static, without the need to include some extra DLLs. With Qt 5.x, it seems I now have to include a platform dll to make the GUI work. This makes having a fully static utility program impossible. Is there any way to work around this, such as building the platform support into a static library I can link with? _______________________________________________ Interest mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/interest _______________________________________________ Interest mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/interest _______________________________________________ Interest mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/interest
