On Wed 13 Sep 2017, Emil Velikov wrote:
> On 2 September 2017 at 09:17, Chad Versace wrote:
> > Just as Mesa imports the Khronos Vulkan headers, it should import this
> > Android-private Vulkan header too. This guarantees that Mesa will
> > continue to build even when upstream Android breaks heade
On 2 September 2017 at 09:17, Chad Versace wrote:
> Just as Mesa imports the Khronos Vulkan headers, it should import this
> Android-private Vulkan header too. This guarantees that Mesa will
> continue to build even when upstream Android breaks header
> compatibility.
>
That's the thing - upstream
Just as Mesa imports the Khronos Vulkan headers, it should import this
Android-private Vulkan header too. This guarantees that Mesa will
continue to build even when upstream Android breaks header
compatibility.
This header is only for *implementers* of Vulkan, not for consumers of
Vulkan.
Importe
