-
Notifications
You must be signed in to change notification settings - Fork 251
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose access to reflection data #22
Comments
This will be the major feature in version 0.4. Thanks for reporting! |
Is there any progress or plan on this issue? Or should I use something like #45 for now? |
The code review of #45 is not finished. Waiting for a change from author. I'll contact him for a revision. |
No news from @sunnypchen, right? 😞 |
I added reflection features to my ShaderConductor fork. It's for SPIRV-Cross. It's very specific to what I need for the MonoGame shader compiler, but it might still be helpful. After all most projects will probably have somewhat similar reflection requirements. |
A preliminary dxil reflection is added in 063c0ea |
Is your feature request related to a problem? Please describe.
With the current API it is not possible to get reflection data from built shaders.
Describe the solution you'd like
A way of accessing the SPIRV-Cross reflection data (if SPIRV-Cross is used) and DXC reflection data.
Additional context
There is an example of how to get DXC reflection data in their tests here, but looks like it's Windows only. SPIRV-Cross has a wiki page for their reflection API.
The text was updated successfully, but these errors were encountered: