![]() But, first of all, copying just Qt libraries is not enough, there are some other libraries that need to be deployed along, and secondly, the final size of the deployed application can easily exceed a couple of hundreds of megabytes, which is not really okay even for desktop targets, not to say about embedded devices with quite a limited space available. What I did in the past - I just copied the entire set of Qt libraries to the application directory and then application started working. ![]() 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |