While everything works on your development machine, being deployed on another machine your applications most likely will complain about all sorts of missing libraries. Why build Qt staticallyĭeployment of dynamically linked Qt applications always was (is) not a trivial task. But here is a more recent partly related article about installing Qt without official installer, which covers Qt 6.x too. configure -static -release -no -pch -prefix "/path/to/qt/5.15.2-static" -skip qtwebengine -nomake tests -nomake examplesĪlso note that this article was written when Qt 5.x was the latest version available, so it doesn’t account for all the peculiarities of building Qt 6.x or newer ( although the process is mostly the same). The article has really exploded in volume over the years, so here are some general commands for configuration and building static Qt. Variable has incomplete type struct stat64.Could not find the Qt platform plugin XCB.QQmlApplicationEngine failed to load component, qtquick2plugin not found.Non-existent module or unknown command line option.Text is not visible, because there are no fonts. I always used dynamic builds and had lots of involuntary sexual intercourses with macdeployqt/ windeployqt ( perhaps I should write about this too).īut not anymore, because I finally overcame my fears/stupidity/laziness, RTFMed and managed to build Qt statically.Īlthough the article is about making a static build, it also covers the task of building Qt from sources in general. For quite a long time statically built Qt was kind of a mystery to me.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |