[Mesa-dev] [Bug 107511] KHR/khrplatform.h not always installed when needed

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed May 8 07:06:20 UTC 2019


https://bugs.freedesktop.org/show_bug.cgi?id=107511

Eric Engestrom <fdo-bugs at engestrom.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #3 from Eric Engestrom <fdo-bugs at engestrom.ch> ---
(In reply to Madhurkiran from comment #2)
> Hi all,
> 
> I see that certain GL headers like "glcorearb.h" needs "KHRplatform.h"
> header files. This works seamlessly when the GL and EGL providers are MESA.
> In scenarios where the GL provider is MESA and EGL provider is some GPU
> vendor say ARM, in that scenario, the khrplatform header comes from two
> different providers and that results in conflict. In scenarios like this,
> who should provide the KHRplatform.h header. Some users, may want use
> exclusively EGL/GLES2 binaries, and they dont need GL support. How can we
> resolve this conflict?
> 
> Thanks
> Mads

Hi! Please open a new issue when you encounter a new issue, it helps keep
things clearer ;)

As for your issue, I'm afraid if a user chooses to pull two khrplatform.h from
two different providers, the user is the one who has to choose which one to
keep, or how to merge/combine them.
Neither provider can decide "I'm more important than any other provider, keep
me!"

Hopefully though, this should be easy enough for the user to choose: keep the
most recent one (see the date at the top of the file), and if the other one was
modified from what Khronos provides then copy those modifications :)

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20190508/b52e7a75/attachment.html>


More information about the mesa-dev mailing list