1.3.252 generator imports modules existing only in VulkanSC-Headers

[incertia]

1.3.252 generator imports modules existing only in VulkanSC-Headers

[oddhack]

I should also clarify what the repository is actually for. There's a bunch of stuff in here which is a snapshot of generated files from published spec updates. The actual C/C++ header files are probably all that should be packaged by a downstream distro. The other stuff is not provided for developers using Vulkan in their apps, but for people doing downstream ecosystem components like CTS, validation layers, language bindings, and so on. That isn't made clear today.

[oddhack]

@incertia please check if #408 helps clarify the repository contents / purpose.

[oddhack]

Which modules?

[incertia]

It appears as if registry/genvk.py will attempt to import from

• json_parser
• schema_generator
• json_generator
• json_h_generator
• json_c_generator
• docgenerator
• extensionmetadocgenerator
• interfacedocgenerator
• spirvcapgenerator
• hostsyncgenerator
• formatsgenerator
• syncgenerator
• jsgenerator
• pygenerator
• rubygenerator
• reflib
• validitygenerator

but they do not exist in the Vulkan-Headers registry.

It appears as if these imports have been around for a lot longer so either the missing generators should be added to Vulkan-Headers or genvk.py should be removed, but the latter does not seem correct as genvk.py still generates all of the C headers we want.

[oddhack]

TBH I'm not sure why genvk.py is here, other than that some downstream repos use a similar script to build their targets using their own generators and want to be able to keep in sync with changes in genvk.py. It would take a very long time to check with every downstream consumer and find out if or how they're using this file, so I don't want to remove it. But there's no intention that people actually run the script in this repository for any of the targets it supports - you should be using Vulkan-Docs for that. I can add a note to that effect in the README if that would help.

(Edit: oh, I see this happened with some VulkanSC stuff was brought across to keep the repos more closely synced. I don't know what SC is using this for, if anything, but the point above remains.)

[incertia]

It would probably make sense to add a note in the README. This issue mostly arised because I saw genvk.py within archlinux's vulkan-headers package (based on this repository) but it didn't seem to work. The Vulkan-Docs based package only installs the HTML docs but that is a packaging issue.

[incertia]

LGTM