vulkan-loader/1.4.321 package update

[octo-sts]

[octo-sts]

🛑 Build Failed: Compilation

unknown type name 'PFN_vkReleaseSwapchainImagesKHR'; did you mean 'PFN_vkReleaseSwapchainImagesEXT'?

Build Details

Category	Details
Build System	CMake/Ninja
Failure Point	Compilation of asm_offset.c file

Root Cause Analysis 🔍

The compiler encountered an undefined type 'PFN_vkReleaseSwapchainImagesKHR' in vk_layer_dispatch_table.h. This suggests a mismatch between the Vulkan loader code and the Vulkan headers being used. The error specifically points to line 733 in vk_layer_dispatch_table.h where it's trying to use a function pointer type that doesn't exist, while suggesting a similar type (PFN_vkReleaseSwapchainImagesEXT) does exist.

---

🔍 Build failure fix suggestions

Found similar build failures that have been fixed in the past and analyzed them to suggest a fix:

Suggested Changes

File: package.yaml

• modification at line 24 (environment.contents.packages section)
  Original:

      - vulkan-headers

Replacement:

      - vulkan-headers=1.4.321

File: package.yaml

• modification at line 59 (test.environment.contents.packages section)
  Original:

        - vulkan-headers

Replacement:

        - vulkan-headers=1.4.321

Click to expand fix analysis

Analysis

This build failure stems from a version mismatch between the Vulkan-Loader (version 1.4.321) and the installed vulkan-headers package. The error indicates that the code is trying to use a function pointer type 'PFN_vkReleaseSwapchainImagesKHR' that doesn't exist in the currently installed Vulkan headers, while suggesting that 'PFN_vkReleaseSwapchainImagesEXT' does exist. This suggests that the headers package is not fully compatible with the loader version being built.

Click to expand fix explanation

Explanation

The issue is caused by a version mismatch between the Vulkan-Loader and the vulkan-headers package. The Vulkan-Loader version 1.4.321 introduces or uses the 'PFN_vkReleaseSwapchainImagesKHR' type, but the currently installed vulkan-headers package doesn't contain this definition.

When building Vulkan components, it's critical that the loader and headers versions match exactly, as the Vulkan API evolves with new function types and definitions. The error message specifically mentions 'PFN_vkReleaseSwapchainImagesKHR' not being found but suggests 'PFN_vkReleaseSwapchainImagesEXT' exists - this is a clear indicator of a version mismatch where the KHR extension for this function is not yet available in the installed headers.

By pinning the vulkan-headers dependency to the exact same version as the loader (1.4.321), we ensure that the headers contain all the necessary type definitions needed by the loader code. This version-matching approach is a common requirement for Vulkan components where the API contracts must be precisely aligned between different components of the ecosystem.

Click to expand alternative approaches

Alternative Approaches

• Investigate if there's a newer version of vulkan-headers available (>1.4.321) that also contains the required definitions. This would be a forward-compatible approach but might introduce other compatibility issues.
• Look for and apply any patches from upstream that might address this specific issue without changing the version dependencies.
• Modify the Vulkan-Loader code to conditionally use PFN_vkReleaseSwapchainImagesEXT instead of PFN_vkReleaseSwapchainImagesKHR if the KHR version is not available, but this would be a more invasive change and is not recommended unless absolutely necessary.

---

Was this comment helpful? Please use 👍 or 👎 reactions on this comment.

[octo-sts]

superseded by #59246