[Interest] static build for android and ios

Gian Maxera gmaxera at gmail.com
Tue Jul 14 10:35:51 CEST 2015

The advantage on mobile is the size of the App.
Qt is made of module, if you compile it statically, you don’t have a giant big library, but a lot of static modules.
So, every module link against (at least) QtCore … that means you have a lot of duplication of static code to link against it
and the result will be a bigger app full of duplication of object code.

Another advantage is the startup time. A static app is a big .exe to put fully on the memory before to start the app. That means if your app is bigger of 40Mb at startup your mobile device need to fully load it into memory before start the app.
If it’s dynamic link, the library are loaded only when needed. That means, if your app is only 2Mb of code, you load at startup only 2Mb and then when some features are needed the corresponding library is loaded.

> On 14 Jul 2015, at 04:49, Hamish Moffatt <hamish at risingsoftware.com> wrote:
> On 14/07/15 01:01, Gian Maxera wrote:
>> If you can use dynamic link … use dynamic link !! There is only advantages over static link.
> What advantages on a mobile device? You aren't sharing the libraries 
> with other apps, and you're guaranteed not to get any code stripping...
> Hamish
> _______________________________________________
> Interest mailing list
> Interest at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest

More information about the Interest mailing list