<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 12 July 2017 at 08:11, Khem Raj <span dir="ltr"><<a href="mailto:raj.khem@gmail.com" target="_blank">raj.khem@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="m_-8739775874278883400m_4452814043463377778m_-9200332532879437627HOEnZb"><div class="m_-8739775874278883400m_4452814043463377778m_-9200332532879437627h5">On Tue, Jul 11, 2017 at 9:56 PM, Andrea Galbusera <<a href="mailto:gizero@gmail.com" target="_blank">gizero@gmail.com</a>> wrote:<br>> I may be in the need to craft something locally to unbreak building with<br>
> current master... Could you please shed some light on how this should be<br>
> done then? Is this a matter of completely removing either mesa-gl or<br>
> userland from gtk+3 deps or a more selective change to avoid the clash in<br>
> recipe-sysroot?<br>
<br>
</div></div>Firstly, determine where this file belongs to. If it is part of<br>
egl/gles then it should go to userland, otherwise it should be<br>
provided by mesa when using userland for graphics<br>
</blockquote></div><br></div><div class="gmail_extra">It's a "generic" Khronos platform header (so not part of EGL or GLES[1-3] but needed by all), in a perfect world we could use any version of it ... unfortunately "Adopters may modify this file to suit their platform" and of course that's what Userland has done.</div><div class="gmail_extra"><br></div><div class="gmail_extra">I think I'll just send a patch to mesa-gl recipe to not install the header. If someone wants to solve this properly with the upstreams, be my guest. </div><div class="gmail_extra"><br></div><div class="gmail_extra">Jussi</div></div>