Currently kwin packaging doesn't depend on libhybris and doesn't build hwcomposer.. and for mobile we use patched packaging in Neon/mobile branch to enable it : https://packaging.neon.kde.org/plasma/kwin.git/commit/?h=Neon/mobile&id=ba779ae41aed29e011eb693e51c895d8e82aa511 It would be sensible to have Neon/release, Neon/stable branches to depend on libhybris-dev on armhf architecture and enable hwcomposer platform packages so that it can be used by Debian CI as well.. Reproducible: Always
17:55 <shadeslayer> won't Neon have to build their own hybris? 17:55 <Riddell> shouldn't be a problem 17:56 <Riddell> as we don't build for arm in neon it won't affect the neon buids 17:56 <Riddell> go ahead 17:56 <shadeslayer> true Waiting for day if there are objections, otherwise will push change.
shouldn't be a problem build-deps can be made arch only with [armhf] install files are be made arch only debian/kwin-thing.install.armhf needs some Makefile/bash ugly syntax in debian/rules if it needs different cmake arguments and the package is empty when built on amd64
(In reply to Jonathan Riddell from comment #2) > install files are be made arch only debian/kwin-thing.install.armhf Since there is "Architecture: armel armhf", it won't be required.. am I correct? > needs some Makefile/bash ugly syntax in debian/rules if it needs different > cmake arguments No cmake arguments are required.. so we are safe :-P
https://packaging.neon.kde.org/plasma/kwin.git/commit/?id=656959c7e7a9e55dd8f80ff50c3e493b2f046d13
If the package is armhf and armel, so needs the build-dep (currently only armhf)
Okay, I will make that change.. however I've another question, can I add same patch in Neon/release branch?
No clue, probably.