[PATCH] WIP: use kirigami plugin instead of embedding in qrc

[Marco Martin]

On Thursday 05 May 2016 11:03:45 Dirk Hohndel wrote:
> >> to move further to me is important to know if is easy enough to deploy,
> >> as i wouldn't move in a direction that makes things too hard for who is
> >> using it> 
> > I'm sure we can figure this out - I'll make playing with this a priority
> > and will report back :-)
> 
> So Kirigami requires ECM. and KF5Plasma. and that requires KF5Activities.
> Which requires Boost. And KF5.
> 
> I think at this point we need to talk about scope.

no, KF5Plasma is completely optional and you don't want it to be found on 
Android.
basically it selects two possible versions of 3 classes
Theme Units and Icon that integrate with the system (folders fallbacktheme vs 
plasmatheme, you want fallbacktheme on both android and ios)

i had the intention to make this selectable at runtime instead of build time, 
so would remove this build time warning

ECM provides something similar to the current cmake macro subsurface is using 
to deploy on android.
Another thing that uses it is a work in progress cmake macro provided in 
kirigami to package icons (similar what the build script is doing, but 
completely cmake based even if not super pretty, could be useful)

I can make ecm eventually optional as well if needed (even tough is just a 
bunch of cmake files without further dependencies)

-- 
Marco Martin