So AFAIK we always put the extensions there that we need to implement to be able to claim that version, or that is my understanding for GL at least.
For vulkan, because 1.0 is the initial version, there are no extensions to implement to get to that version, so having an extensions list would be nonsensical. All the extensions you will find using the listed commands are the ones that are shown in the subsequent list for non version-specific extensions, or are not listed at all because of being KHX/EXT or vendor extensions. - Bas On Thu, Sep 14, 2017 at 11:46 PM, Romain Failliot <romain.faill...@foolstep.com> wrote: > Hi! > > I'm working on exposing the vulkan information recently added in > features.txt in mesamatrix.net, but there is no extension list under "Vulkan > 1.0 - all DONE: anv, radv" > > There is a couple of command lines in the commit message though: > https://cgit.freedesktop.org/mesa/mesa/commit/?id=fe3d2559d941f8f69dbdb369221af69a9974d017 > > I could generate the list locally, but if a new driver comes in (nvidia for > instance), or if new extensions are added to Vulkan 1.0.xx, this will start > to be hard to maintain. > > Is it possible to do the same as for OpenGL and list all the vulkan > extensions directly in features.txt? > > Thanks, > Romain > > _______________________________________________ > mesa-dev mailing list > mesa-dev@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/mesa-dev > _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
