<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - Build problem: meson build can not find wayland-scanner" href="https://bugs.freedesktop.org/show_bug.cgi?id=111126#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - Build problem: meson build can not find wayland-scanner" href="https://bugs.freedesktop.org/show_bug.cgi?id=111126">bug 111126</a> from <a class="email" href="mailto:emil.l.velikov@gmail.com" title="Emil Velikov <emil.l.velikov@gmail.com>"> Emil Velikov</a> <pre>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.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>