wayland: fix cross-building tests to use correct method

[kuroneko]

• Fix [package] wayland/1.22.0: conanfile uses wrong test for cross building. #22166: switch from using cross_building to using can_run so the conf option that explicitly says we must (or must not) cross build is respected correctly.

Specify library name and version: waylland/1.22.0

---

• I've read the contributing guidelines.
• I've used a recent Conan client version close to the currently deployed.
• I've tried at least one configuration locally with the conan-center hook activated.

[github-actions]

🤖 Beep Boop! This pull request is making changes to 'recipes/wayland//'.

👋 @jwillikers you might be interested. 😉

[ghost]

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

• [wayland] Add ECM naming to aliases #19412

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

[jwillikers]

LGTM!

[conan-center-bot]

Conan v1 pipeline ✔️

All green in build 2 (65f749aff180e0d18618316990ce77336b02ef35):

• wayland/1.22.0:
  All packages built successfully! (All logs)

• wayland/1.21.0:
  All packages built successfully! (All logs)

• wayland/1.19.0:
  All packages built successfully! (All logs)

• wayland/1.20.0:
  All packages built successfully! (All logs)

• wayland/1.18.0:
  All packages built successfully! (All logs)

---

Conan v2 pipeline ✔️

Note: Conan v2 builds are now mandatory. Please read our discussion about it.

All green in build 2 (65f749aff180e0d18618316990ce77336b02ef35):

• wayland/1.22.0:
  All packages built successfully! (All logs)

• wayland/1.21.0:
  All packages built successfully! (All logs)

• wayland/1.20.0:
  All packages built successfully! (All logs)

• wayland/1.19.0:
  All packages built successfully! (All logs)

• wayland/1.18.0:
  All packages built successfully! (All logs)

[SpaceIm]

Fix #22166: switch from using cross_building to using can_run so the conf option that explicitly says we must (or must not) cross build is respected correctly.

Just one comment: tools.build.cross_building:can_run doesn't express whether we cross-build or not. It can just tell to conan that executables cross-compiled for host can be executed on build machine.

[kuroneko]

Fix #22166: switch from using cross_building to using can_run so the conf option that explicitly says we must (or must not) cross build is respected correctly.

Just one comment: tools.build.cross_building:can_run doesn't express whether we cross-build or not. It can just tell to conan that executables cross-compiled for host can be executed on build machine.

From the meson perspective, it should be doing exactly that (See conan-io/conan#11035 for why can_run got introduced).

If the outputs run natively on the platform (transparent emulation or not), then you don't need to cross-build.

If the outputs can't run (without magic) despite the rest matching (such as caused by ABI mismatch), then you are cross-building.

So whilst I appreciate your niggle to the letter of the how the variable is described, the reality is that is meant to provide an override for cross building decisions where the automated approach decides incorrectly.