-
Notifications
You must be signed in to change notification settings - Fork 6.1k
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
[skia] missing webgpu headers when enabling dawn #35606
Comments
Are these headers a public dependency, i.e. needed to use dawn with skia? |
I think we'd need a dawn dependency first. If I understand well, dawn is a webgpu implementation. So maybe we'd webgpu-header first. When I wrote this issue I didn't understand well all these new graphic stack layers. I think dawn and webgpu are very interesting as a simple cross platform gpu solution. |
Maybe if you are able to target vulkan/d3d/metal then there is no need for dawn. |
I face similar difficulties... What I can say is that skia is a difficult port from a vcpkg POV. skia and its vendored dawn use gn which helps to mitigate some problems of vendored dependencies. And so the skia port still uses a lot of vendored dependencies which should be de-vendored for vcpkg. Which is hard to do, with moving versions and local customizations. |
I totally get you, similar troubles with tensorflow I gess. |
tensorflow is worse: It is building a lot of stuff also for host tools. It is close to impossible to sort this out correctly in particular for MSVC which needs a different runtime for debug... I considered rewriting that port from scratch, transferring utility functions from skia for devendoring what is already available. |
Is your feature request related to a problem? Please describe.
Currently, it is possible to enable dawn for skia, but we don't have the corresponding headers used for webgpu.
Proposed solution
Would it be possible to ship the web gpu headers used to compile dawn?
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: