Installing qml caches

[Lisandro Damián Nicanor Pérez Meyer]

El martes, 3 de julio de 2018 05:21:56 -03 Volker Krause escribió:
[snip] 
> Qt 5.11 actually has something like this, but only covering QML files
> compiled in via qrc, see qtquick_compiler_add_resources() (I needed a very
> recent 5.11 branch build though for this to work, post 5.11.1).
> 
> I have no performance measurements yet, but at least the package size goes
> up contrary to what one might expect, as the compiled binary is 2-3x larger
> than the (non-minified) QML source code. That space would be needed by the
> qmlc files anyway in the end though, so overall disk space cost goes down a
> bit once deployed.
> 
> With the QML sources no longer included you end up with a non-starting
> application after updating Qt though.
> 
> So, interesting for APKs etc where you fully control Qt, but probably not
> for distros.

I was actually thinking in packages shipping qml source files as usual, make 
package register them with some tool and recompile them with any qt update.

Now I don't know if that happens automatically, ie, qml files become compiled 
at runtime in a cache. If that's the case then only the first run for each 
user would just take time.

But again, the benefit really needs to be interesting to deploy something like 
this.


-- 
16: De quien es Internet
    * De DIOS dado que todas las cosas del mundo le pertenecen
    Damian Nadales
    http://mx.grulic.org.ar/lurker/message/20080307.141449.a70fb2fc.es.html

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20180703/a0844c31/attachment.sig>