search

KhronosGroup / SPIRV-Headers

SPIRV-Headers
Other
269 stars 254 forks source link

Create release that matches spire-tools 2024.3 release #438

Closed ZzEeKkAa closed 6 days ago

ZzEeKkAa commented 3 months ago

spirv-tools 2024.3 requires 2acb319af38d43be3ea76bfabf3998e5281d8d12 commit. Is it possible to create release from this commit?

What is the dependency between headers and tools? Is possible to have headers release that is compatible with spirv-tools releases in the future?

Currently, It breaks condo build (and may be others) https://github.com/conda-forge/spirv-tools-feedstock/pull/15 . I believe that headers version mismatch is the reason.

jeremy-lunarg commented 2 months ago

For the Vulkan SDK, we create a set of tags (e.g. vulkan-sdk-1.3.290.0) for all source repos. Would it work for you to update against the SDK release cadence? We also perform additional testing against the SDK releases.

bashbaug commented 1 month ago

@ZzEeKkAa will using the Vulkan SDK tags work for you? We're interested in your feedback - thanks!

Note also that spirv-tools includes a DEPS file describing the version requirements for its dependencies that may be useful.

ZzEeKkAa commented 6 days ago

I guess there was an issue that vulkan-sdk-1.3.290.0 was not tagged, and spirv-tools 2024.3 was already tagged. In conda forge you can distribute only tagged libraries.

https://github.com/KhronosGroup/SPIRV-Tools/blob/main/DEPS works good, but it requires manually checking what is the release version for this commit. Ideally I would want somehow to get the headers version, not the commit hash.