wayland-protocols 1.21

[ericLemanissier]

Specify library name and version: wayland-protocols/1.21

close #6946

• 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.

[ericLemanissier]

Here we go: this recipe only packages xml files, and it should generate the following .pc file:

prefix=/usr
datarootdir=${prefix}/share
pkgdatadir=${pc_sysrootdir}${datarootdir}/wayland-protocols

Name: Wayland Protocols
Description: Wayland protocol files
Version: 1.20

Which conan is currently not able to generate, because it has no way of specifying pkg-config variables.
We have to choose between:

• making it a regular conan package, add it to KB-H014 allow list, and let consumer recipe patch the .pc file like this
• making it a system package, but it's not very satisfying because we are able to compile it properly
• don't make a package for wayland-procols, which means gtk package (regular package, not the system one currently available on CCI) will have to be built without wayland support by default
• something else ?

[ericLemanissier]

that's high level crickets!
@uilianries @SSE4 @Croydon wdyt ?

[Croydon]

Urgh o.O

Is there any chance that pkg-config files can get a path to themselves, so we can construct a path that always works?

[ericLemanissier]

I don't think so. the "regular package" solution would need something like conan-io/conan#4048 in order to patch the .pc file after install, or manual patching by consumers like bincrafters/conan-gtk@2ce2d80#diff-63f09721ade419d29886e8190ffa3c9c756baa9bef8802a7f2aeabf3b545164fR107-R108

[Croydon]

I agree that this feels like it requires more Conan features.

Either we let Conan generate the .pc file and we get a correct prefix path to the package folder, but we won't have the custom variables then.

Or we package the .pc file and could define own variables, but there seems to be no way to guess the correct path after installation of the package.

[stale]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[ericLemanissier]

Rethinking about this, I think the least bad option is to use a regular conan package, and rely on consumers (for now, that would be only gtk) to patch the generated wayland-protocols.pc and add the correct path in the pkgdatadir variable, or patch their build system to get the path to pkgdatadir from something else than pkg-config

[stale]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[ericLemanissier]

this is now blocked by the deployment of conan 1.36.0 now that conan-io/conan#8727 is merged

[stale]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[ericLemanissier]

blocked by conan-io/hooks#337

[ericLemanissierBot]

I detected other pull requests that are modifying wayland-protocols/all recipe:

• [wayland-protocols] Add recipe #6946

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

[jgsogo]

I didn't realize about this PR and I've created mine here: #6946

I'm fine moving forward with any of them.

[jgsogo]

This is not needed to build (at least using Meson) although the build-system declares the dependency.

[jgsogo]

It has no deps

Suggested change

generators = "pkg_config"

[conan-center-bot]

All green in build 10 (1e36717d9173dc1d47a0dcffa9512a12664daa4a):

• wayland-protocols/1.21@:
  All packages built successfully! (All logs)

[ericLemanissier]

When this recipe was originally written, wayland-protocols did not have meson support. Let's continue with the other PR