register QML modules at build time + use qmlcachegen

[Be-ing]

Fixes #242

[Be-ing]

I removed the qml_extension_plugin example now that this is automatically generating QML plugins under the hood. If the user wants a dynamically linked QML extension plugin, that can easily be created by specifying crate-type = ["cdylib"] in Cargo.toml and linking ${CRATE} instead of "$<LINK_LIBRARY:WHOLE_ARCHIVE,${CRATE}-static>" in CMakeLists.txt.

[ahayzen-kdab]

I removed the qml_extension_plugin example now that this is automatically generating QML plugins under the hood. If the user wants a dynamically linked QML extension plugin, that can easily be created by specifying crate-type = ["cdylib"] in Cargo.toml and linking ${CRATE} instead of "$<LINK_LIBRARY:WHOLE_ARCHIVE,${CRATE}-static>" in CMakeLists.txt.

I wonder if we should still have an example somewhere of using the crate-type as cdylib to a) show how this is done b) so we don't forget and c) to ensure it compiles, as i thought the dynamic linking before picked up some other cases.

Maybe it doesn't need to be explicitly called extension plugin, but instead dynamic linking or something. Although would this be for cargo-only builds ? For a CMake example where one is dynamic linking would you just create a CMake library and static link the Rust into that as normal ?

[Be-ing]

Maybe it doesn't need to be explicitly called extension plugin, but instead dynamic linking or something. Although would this be for cargo-only builds ? For a CMake example where one is dynamic linking would you just create a CMake library and static link the Rust into that as normal ?

A cdylib QML plugin example could be for either Cargo-only or CMake builds. With CMake, the cdylib generated by Cargo would be linked into the C++ executable.

[ahayzen-kdab]

Maybe it doesn't need to be explicitly called extension plugin, but instead dynamic linking or something. Although would this be for cargo-only builds ? For a CMake example where one is dynamic linking would you just create a CMake library and static link the Rust into that as normal ?

A cdylib QML plugin example could be for either Cargo-only or CMake builds. With CMake, the cdylib generated by Cargo would be linked into the C++ executable.

Lets instead document this in the book :-)

[ahayzen-kdab]

LGTM, lets start with this and any refactors of qt-build-utils etc can be later.

Awesome work getting the QML modules to build correctly and removing the qrc files 🎉 🥳