sessamekesh / iggpu Goto Github PK

This more naturally follows how WebGPU does things, and should be the preferred pattern.

Cannot do this until Emscripten supports wgpuDeviceCreateRenderPipelineAsync method.

... I suspect it won't be hard to implement that method myself, so I'm leaving this little note to do it. It might be hard. We'll see.

Embind methods to give std::string parameters, but AppBase::Create expects a c-string.

Instead, either:

• Pass along std::string the whole way, or
• Create a copy of the c-string that is passed along and deleted in final callback.

C-strings referencing values that are cleaned up on the stack (e.g. a std::string parameter for a create_app embind method) end up pointing to garbage and ruining canvas reference stuff.

Dawn has a bunch of useful utility methods that are specific to Dawn here: https://dawn.googlesource.com/dawn/+/refs/heads/main/src/dawn/utils/

iggpu is meant to be an abstraction over Dawn (native) or WebGPU for cross-platform builds including WASM targets.

Most of these are things that existed in pre-isolation iggpu versions (sanctify-game, sanctify-min projects) but I just haven't brought over yet. The Dawn implementations are generally similar, even without igcore::PodVector etc. types from previous iggpu iterations.

Especially helpful methods to bring over (or at least something similar):

• CreateBufferFromData
  • Also add a templated override that takes std::vector and auto-infers size
  • And include an optional parameter for "label"
• MakePipelineLayout and similar for MakeBindGroupLayout
  • Maybe something fancier with an initializer list input instead of an already constructed std::vector to allow you to do fancy initializer magic - per previous iggpu.

Of the WebGPU utilities, I think this is the only one that actually makes sense to move over. InstanceBuffer is nice and I use it all the time, but it's clunky and not sufficiently generally useful for this library.