Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#50151 - [vulkan-headers] Request to include api registry within headers package or as a separate package
Attached to Project:
Arch Linux
Opened by Ashwin Balasubramaniyan (ashwin.vbs) - Tuesday, 26 July 2016, 09:43 GMT
Last edited by Laurent Carlier (lordheavy) - Tuesday, 26 July 2016, 16:04 GMT
Opened by Ashwin Balasubramaniyan (ashwin.vbs) - Tuesday, 26 July 2016, 09:43 GMT
Last edited by Laurent Carlier (lordheavy) - Tuesday, 26 July 2016, 16:04 GMT
|
DetailsDescription:
Each release of vulkan headers comes with a API registry as a xml file (refer: https://www.khronos.org/registry/vulkan/#apiregistry). The registry is used by third party tools like vkCppGenerator (https://github.com/nvpro-pipeline/vkcpp) to generate headers. As vulkan header version must precisely match the version of registry used, it would be useful to package the registry along with the headers. Even if the registry is introduced as a new package, it would be easier to update if the registry package is generated at the same time the header package is. |
This task depends upon
Closed by Laurent Carlier (lordheavy)
Tuesday, 26 July 2016, 16:04 GMT
Reason for closing: Implemented
Additional comments about closing: vulkan-headers-1:1.0.21-2
Tuesday, 26 July 2016, 16:04 GMT
Reason for closing: Implemented
Additional comments about closing: vulkan-headers-1:1.0.21-2
I've also pushed html documentation in the vulkan-html-docs package