Comments (4)
The latest SDK build still shows issues: http://erusea:8080/view/Manual/job/manual-sdk/529/console
WARNING: generated BOM C:\j\msdk\vulkantest-results\bom\qt-repo-BOM.txt added entries not in reference BOM C:\j\msdk\build\Vulkan-SDK-Packaging\repo\SDK_creation\Windows\qt-repo-BOM.txt:
+ CoreSDK,Bin\VkLayer_khronos_shader_object.dll
+ CoreSDK,Bin\VkLayer_khronos_shader_object.json
+ CoreSDK,Bin\VkLayer_khronos_shader_object.pdb
+ CoreSDK,Include\vulkan\vulkan_extension_inspection.hpp
+ CoreSDK,Lib\VkLayer_khronos_shader_object.lib
+ CoreSDK32,Bin32\VkLayer_khronos_shader_object.dll
+ CoreSDK32,Bin32\VkLayer_khronos_shader_object.json
+ CoreSDK32,Bin32\VkLayer_khronos_shader_object.pdb
I observe that VkLayer_khronos_shader_object.lib
is still being shipped (I suspect it was overlooked in the earlier fix.
I also note that the 32-bit install
target still ships VkLayer_khronos_shader_object
, though it's not supposed to; see the SDK design document at https://docs.google.com/document/d/14HULgqYy4k3-UDRKbUr_jWQcRGX4RGPN05iLoz0jSB0 . In the interest of keeping install control at the repository level, that means this repository must not ship the VkLayer_khronos_shader_object
files in a 32-bit build.
from vulkan-extensionlayer.
I observe that
VkLayer_khronos_shader_object.lib
is still being shipped (I suspect it was overlooked in the earlier fix.
I just checked the build logs from github actions:
https://github.com/KhronosGroup/Vulkan-ExtensionLayer/actions/runs/4690667744/jobs/8314079421
https://github.com/KhronosGroup/Vulkan-ExtensionLayer/actions/runs/4690667744/jobs/8314079208
No .lib
files are being installed. I cannot reproduce that.
I also note that the 32-bit install target still ships VkLayer_khronos_shader_object, though it's not supposed to; see the SDK design document at https://docs.google.com/document/d/14HULgqYy4k3-UDRKbUr_jWQcRGX4RGPN05iLoz0jSB0 . In the interest of keeping install control at the repository level, that means this repository must not ship the VkLayer_khronos_shader_object files in a 32-bit build.
Sure but why?
from vulkan-extensionlayer.
Just had Karen explain to me the rational. I have a new PR up that will remove 32 bit support.
from vulkan-extensionlayer.
Sure but why?
We debated in an SDK planning video meeting the need for 32-bit. Recalling my notes, the general thoughts went (:heavy_plus_sign: marks arguments for 32-bit support, :heavy_minus_sign: marks arguments against):
- ➕ we ship 32-bit for everything else
- ➕ we believe there are 32-bit applications still under active development who cannot or will not make the jump to 64-bit
- ➖ it's unlikely a 32-bit application still in active development would want to completely revise their pipeline and shader structure to use this new object
- ➖ if we ship 32-bit once, we have to ship 32-bit forever
IIRC, we decided to ship 64-bit only for now, and reconsider if and when someone complains.
from vulkan-extensionlayer.
Related Issues (20)
- shader_object_full_draw_state_struct_members.inl: error: use of undeclared identifier 'assert' HOT 5
- v1.3.248 fails to build with libc++
- Manual cloning of `shaderc` needed when building for Android on Windows ?
- decompression: DecompressionTest.DecompressMemory crashes on Android HOT 12
- Cleanup CMake / GHA for this repo HOT 1
- shader object emulation layer documentation - remove/update Android information HOT 1
- [question] It's possible will have support extension layer for VK_EXT_robustness2? HOT 1
- Race condition in shader object layer? HOT 3
- Test failure on AMD 6800 machines HOT 1
- Potential use of pipeline with different shaders than requested
- ShaderObject: `VK_NULL_HANDLE` used instead of correct pipeline
- Bad behaviour of captured `vkEnumerateDeviceExtensionProperties` HOT 3
- shaderObject: possible alignment issues
- Adding support for VK_EXT_dynamic_rendering_unused_attachements in shader objects layer
- Test Failure on a Nvidia 2070 with 32 bit build on Windows 10 with 531.79 driver
- Remove ndk-build HOT 1
- layers incorrectly rewrite extensions list HOT 5
- When using sync2 layer, VK_KHR_synchronization2 extension is reported twice
- Decompression Layer Testing fails on Pixel 7 and Galaxy S23 HOT 11
- [Shader Object] Incorrect structure type reported in pNext chain of device create info HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from vulkan-extensionlayer.