[PATCH 0/6] Teach cmake.bbclass to put cmake page files in -dev packages

[Mike Crowe <mac@mcrowe.com>]

We've added a few of our own recipes recently for projects that use cmake
and it's a pain to have to add the required magic to ensure that cmake's
package files (a bit like .pc files) end up in the -dev package. Forgetting
to do this causes annoying warnings about unpackaged files.

So, let's just teach cmake.bbclass to deal with this itself.

I've tested that each of the packages build correctly without generating
warnings about left-over files. But I haven't checked that anything that
might be relying the package files can still find them afterwards. I did
test that core-image-sato still builds, but that probably doesn't prove
much.

I don't think there's any harm for third-party recipes that continue to
contain equivalent FILES_${PN}-dev assignments.

Mike.

Mike Crowe (6):
  cmake: Always put cmake package files in -dev packages
  libsolv: Rely on cmake.bbclass to put cmake package files in dev
    package
  vulkan: Rely on cmake.bbclass to put cmake package files in dev
    package
  waffle: Rely on cmake.bbclass to put cmake package files in dev
    package
  libical: Rely on cmake.bbclass to put cmake package files in dev
    package
  libproxy: Rely on cmake.bbclass to put cmake package files in dev
    package

 meta/classes/cmake.bbclass                       | 2 ++
 meta/recipes-extended/libsolv/libsolv_0.6.29.bb  | 1 -
 meta/recipes-graphics/vulkan/assimp_4.0.1.bb     | 2 --
 meta/recipes-graphics/waffle/waffle_1.5.2.bb     | 3 ---
 meta/recipes-support/libical/libical_2.0.0.bb    | 2 --
 meta/recipes-support/libproxy/libproxy_0.4.15.bb | 1 -
 6 files changed, 2 insertions(+), 9 deletions(-)

-- 
2.11.0