Most things are redundant (or can't be used in a wasm context) except
1) kernel display name
2) c++ version based on kernel name
3) language (cpp or c I guess)
4) debugger info
Things like env, resource dir and other include paths if any can't be put to use.
There is no xcpp exectuable either (a wasm build would give us xcpp.js, xcpp.wasm, xcpp.data) and we just have an empty placeholder there.
This is the kernel.json file I see while building
xeus-cpp-lite
Most things are redundant (or can't be used in a wasm context) except 1) kernel display name 2) c++ version based on kernel name 3) language (cpp or c I guess) 4) debugger info
Things like env, resource dir and other include paths if any can't be put to use. There is no
xcpp
exectuable either (a wasm build would give us xcpp.js, xcpp.wasm, xcpp.data) and we just have an empty placeholder there.