Hazel icon indicating copy to clipboard operation
Hazel copied to clipboard

Updated Premake and Vulkan to latest beta versions

Open soulwax opened this issue 2 years ago • 4 comments

Upgraded Premake to version 5.0.0-beta2 and Vulkan SDK to version 1.3.275.0 ensuring compatibility with the latest features and improvements in both tools. These updates address potential stability and performance issues while offering access to more recent enhancements.

This commit along with the updated versions was tested thoroughly.

soulwax avatar Mar 04 '24 23:03 soulwax

Upgraded Premake to 5.0.0-beta3 and Vulkan SDK to 1.3.296.0

Upgraded the scripts to leverage the latest features and improvements in build configuration and graphics development. This update ensures compatibility with recent advancements and stability enhancements, contributing to a more efficient and robust development environment.

Tested for full functionality with success.

soulwax avatar Nov 14 '24 03:11 soulwax

@ViktorPopp please test 7fa8f2c and merge these changes as I was about to initiate a pr for this! thanks!

brodante avatar Nov 20 '24 03:11 brodante

@ViktorPopp please test 7fa8f2c and merge these changes as I was about to initiate a pr for this! thanks!

This seems to take a while.

So let me help out by quoting Vulkan's philosophy of backwards compatibility concisely:

Vulkan works on a major, minor, patch versioning system. Currently, there are 3 minor version releases of Vulkan (1.0, 1.1, 1.2 and 1.3) which are backward compatible with each other. An application can use vkEnumerateInstanceVersion to check what version of a Vulkan instance is supported.

Premake5: https://github.com/premake/premake-core/issues/933 In short: they can't guarantee backwards compatibility when someone comes from Premake4. Otherwise no breaking changes from Premake5 Alpha x to Beta y.

soulwax avatar Dec 03 '24 10:12 soulwax

@ViktorPopp please test 7fa8f2c and merge these changes as I was about to initiate a pr for this! thanks!

This seems to take a while.

So let me help out by quoting Vulkan's philosophy of backwards compatibility concisely:

Vulkan works on a major, minor, patch versioning system. Currently, there are 3 minor version releases of Vulkan (1.0, 1.1, 1.2 and 1.3) which are backward compatible with each other. An application can use vkEnumerateInstanceVersion to check what version of a Vulkan instance is supported.

Premake5: premake/premake-core#933 In short: they can't guarantee backwards compatibility when someone comes from Premake4. Otherwise no breaking changes from Premake5 Alpha x to Beta y.

thank you for the clarification kind sir, I am new to complex projects so I appreciate the time you took to explain this.

brodante avatar Dec 05 '24 13:12 brodante