> To accommodate this, we have over the last 6 months done significant work on our build infrastructure to give our users much more fine grained control over the way how Qt is being built. This is what we called the Qt Lite Project.<p>> [...]<p>> From initial measurements, we expect that you will be able to reduce the size of a statically linked Qt Quick application by up to 70% compared to Qt 5.6.<p>Does this mean they fixed static linking in 5.8? It stopped working in 5.7 for some reason in most projects. With 5.6 it was easy to use cmake scripts to create statically linked applications when your Qt installation was build statically. This still worked with qmake projects in 5.7 but not cmake.<p>I kinda wish I could build a Qt installation that has dynamic libs and static archives, but it's not possible to select that at configure time.<p>Stuff either doesn't build or it builds and then still looks for dynamic bits since 5.7. This was fine in 5.6 AFAIR.
It looks like QML/Qt Quick Controls 2 are moving becoming mobile/embedded first, and they are recommending desktop apps stick to QtWidgets for native looking UIs.
The docs for it don't seem to be on docs.qt.io. :(<p>Created a request to add them (<a href="https://bugreports.qt.io/browse/QTBUG-55744" rel="nofollow">https://bugreports.qt.io/browse/QTBUG-55744</a>), to make reading through details of the new modules easier for people.
> I think we need more libraries/widgets in order for us to design native looking Android/iOS apps.<p>So still the same "do your own QML mimic of native widgets"?