https://bugs.freedesktop.org/show_bug.cgi?id=111126
--- Comment #4 from Emil Velikov <emil.l.veli...@gmail.com> ---
BTH it's been a while, so I don't recall the details. It was either:
- target machine was missing wayland-scanner (correct), so we had to tell
meson to use the one of the build host, or
- meson was trying to run the target wayland-scanner on the build host, and
failing since they are different architectures
Quick look around shows that meson 0.51 release notes mentions something about
this in "Specifying options per mer machine". Yet I cannot see a clear example
having meson.build compatible with old and new meson :-\
FWIW I'm inclined to call this a meson bug - changing behaviour is w/o a big
fat preemptive WARNING is not nice. Yet I won't object if you want to revert my
patch.
--
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
