xkbcommon: Use PkgConfigDeps build context for wayland

[jwillikers]

Specify library name and version: xkbcommon/*

Now that PkgConfigDeps can generate pkg-config files for the build context as of Conan 1.52.0, the xkbcommon recipe should make use of it for the wayland and wayland-protocols dependencies which are used as tool_requires.

---

• I've read the guidelines for contributing.
• I've followed the PEP8 style guides for Python code in the recipes.
• I've used the latest Conan client version.
• I've tried at least one configuration locally with the conan-center hook activated.

[ghost]

I detected other pull requests that are modifying xkbcommon/all recipe:

• xkbcommon: finer grain requirements #13604

This message is automatically generated by https://github.com/ericLemanissier/conan-center-conflicting-prs so don't hesitate to report issues/improvements there.

[prince-chrismc]

if you dont ass the context suffix could this be removed?

[jwillikers]

I'll get an error if I don't set the build_context_suffix for the wayland package because this library requires the wayland-client library from the wayland package as a regular requires while simultaneously requiring the wayland-scanner tool from the wayland package as a tool_requires.

If we were able to place the build-context pkg-config files in a separate directory from the others, this would avoid naming conflicts and the necessary patching to find the tool_requires dependencies. Meson would be able to handle this gracefully just by setting the standard project option build.pkg_config_path to a value including the directory for the build-context pkg-config files.

[jwillikers]

I've gone ahead and re-worked this PR to use a separate directory for the pkg-config files in the build context. This doesn't require using replace_in_file when a build profile is present.

[prince-chrismc]

Sometimes I ask questions for myself to learn. Don't feel obligated to make changes the community (aka you) know more than me and that's a good thing.

Reading and looking qt the code I feel like it's a limitation on the client, like there's nothing in the layout for separation... seems like a useful feature

Maybe we can open an issue again the main repo and see what the team thinks?

[jwillikers]

I think that'd be a good idea, even if it's only useful for Meson. Your question hit on something that'd been bothering me, too. I'm glad you brought it up. It really seems more maintainable if we don't have to patch the build system in order to use the pkg-config files in the build context. I think the changes here will be a great demonstration of the desired functionality. I'll take care of opening the issue tomorrow unless you get to it first.

[prince-chrismc]

I created conan-io/conan#12342 but feel free to correct me if I misunderstood or left something important out :)

[jwillikers]

Thanks! I just realized my workaround doesn't actually work... I'd have to not only generate pkg-config files for the wayland dependency, but also for everything listed as a requires for the wayland::wayland-scanner component. Without the pkg-config files available for the dependencies, pkg-config reports that the dependency was not found.

[jwillikers]

@ericLemanissier I've cherry-picked your commit in #13604 now that your changes to the X11 packages have been merged.

[conan-center-bot]

All green in build 4 (05bab6bebd90212f425c0653376a1069b737cf8b):

• xkbcommon/1.4.1@:
  All packages built successfully! (All logs)

• xkbcommon/1.3.1@:
  All packages built successfully! (All logs)

• xkbcommon/1.4.0@:
  All packages built successfully! (All logs)

• xkbcommon/1.3.0@:
  All packages built successfully! (All logs)

• xkbcommon/1.0.1@:
  All packages built successfully! (All logs)

• xkbcommon/1.2.1@:
  All packages built successfully! (All logs)

• xkbcommon/1.0.3@:
  All packages built successfully! (All logs)

• xkbcommon/1.1.0@:
  All packages built successfully! (All logs)

• xkbcommon/0.10.0@:
  All packages built successfully! (All logs)