Arch Linux

WilliamLewww

Member

Registered: 2022-03-04

Posts: 2

Vulkan SDK Packages

I was wondering if doing the following would be acceptable:

There exists the vulkan-headers package in the any repository and also the vulkan-headers-git package in the AUR.

vulkan-headers targets a specific version of the repository but vulkan-headers-git just targets the upstream version.

A problem I often run into when using vulkan-headers-git is that the upstream version will often contain API changes that would break builds for other projects.

I was thinking about creating vulkan-headers-sdk-git that would use the SDK version of Vulkan-Headers. It would be more stable than using the upstream version because the SDK version is definite. Reading the submission guidelines, I am not sure if this package would violate the "The submitted PKGBUILDs must not build applications already in any of the official binary repositories under any circumstances" rule of submission. I think I might be misinterpreting the rule, but would any -git package also be violating the rule?

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 14,840

Re: Vulkan SDK Packages

There doesn't seem to be a separate vulkan sdk repository, just branches for specific versions .

Every time a new sdk version is branched off you would have to switch to the newer branch.
Much easier to build from a specific tarball .

The vulkan headers seem to exist in 3 variants :
vulkan-headers-git VCS development package
vulkan-headers released version
vulkan-headers-sdk well-tested release (usually older) versions .

That suggests there are real differences between vulkan-header releases and vulkan-headers-sdk releases.
The rule you quote appears to be "not applicable" for such  a package ..

.

Last edited by Lone_Wolf (2022-03-05 11:20:59)

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

WilliamLewww

Member

Registered: 2022-03-04

Posts: 2

Re: Vulkan SDK Packages

Thanks for the response!

Yea, I was thinking about using the tarballs provided by the GitHub tags: https://github.com/KhronosGroup/Vulkan-Headers/tags to decide what version to build.

The only purpose of the package would be to have a stable version of the vulkan-headers-git package; I always run into an issues where vulkan-headers-git is between versions causing API misuse in my development.

Another issue I run into is vulkan-icd-loader-git also uses the development branch. What I usually do is have a local clone of the Vulkan development repositories, but I realized that some packages depend on the vulkan-icd-loader package (steam depends on vulkan-icd-loader). This would cause me to have two instances of the vulkan-icd-loader on my machine which isn't an issue but I would prefer to have one unified package.

It is not too big of an issue (maybe not even an issue at all) but I thought that creating a stable vulkan-headers-git package could prevent these types of issues / bugs.