3 ms·
WebGPU has a (mostly) standardized C API: https://github.com/webgpu-native/webgpu-headers https://github.com/webgpu-native/webgpu-headers
by Encounter 2y ago
WebGPU has a (mostly) standardized C API: https://github.com/webgpu-native/webgpu-headers https://github.com/webgpu-native/webgpu-headers
- westurner 2y agowgpu supports WebGPU: https://github.com/gfx-rs/wgpu https://github.com/gfx-rs/wgpu : > While WebGPU does not support any shading language other than WGSL, we will automatically convert your non-WGSL shaders if you're running on WebGPU.
- dartos 2y agoThat’s just for the shading language
- flohofwoe 2y agoThe Rust wgpu project has an alternative C API which is identical (or at least closely matches, I haven't looked in detail at it yet) the official webgpu.h header. For instance all examples in here are written in C: https://github.com/gfx-rs/wgpu-native/tree/trunk/examples https://github.com/gfx-rs/wgpu-native/tree/trunk/examples There's definitely also people using wgpu from Zig via the C bindings.
- westurner 2y agoI found: shlomnissan/sdl-wasm: https://github.com/shlomnissan/sdl-wasm https://github.com/shlomnissan/sdl-wasm : > A simple example of compiling C/SDL to WebAssembly and binding it to an HTML5 canvas. erik-larsen/emscripten-sdl2-ogles2: https://github.com/erik-larsen/emscripten-sdl2-ogles2 https://github.com/erik-larsen/emscripten-sdl2-ogles2 : > C++/SDL2/OpenGLES2 samples running in the browser via Emscripten IDK how much work there is to migrate these to SDL3? Are there WASM compilation advantages to SDL3 vs SDL2?