KhronosGroup / KhronosGroup/Vulkan-Utility-Libraries

[ci] periodic "inclusive" releases w/ VulkanUtilityLibraries + VulkanHeaders

Open
#324 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
103
Forks
49
Avg merge
7h 15m
Merged PRs (30d)
4

Description

Something similar to this: https://git.crueter.xyz/scripts/VulkanUtilityHeaders

Where for each Vulkan version, this repository has a release that contains *both* the VulkanHeaders and VulkanUtilityLibraries sources and headers, combined as one. This would be useful alongside #315 for enforcing projects that vendor VUL/VH *have* to match the versions if they choose to use these releases.

I have an idea on how to do this in a manner that makes sense, but I'm not quite sure how the maintainers would want it done so I'm leaving my CI (that only grabs the string helper from here anyways) for reference.

Contributor guide

Open the contributing guide

Research direction

Start with the linked VulkanUtilityHeaders example and the existing CI referenced in the issue. Review issue #315 for the related version-matching requirement, then determine how releases should combine VulkanHeaders with VulkanUtilityLibraries for each Vulkan version. Done means maintainers agree on the approach and periodic inclusive releases contain both source and header sets.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
ci-cd, release
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.