FFI & C header parsing

[KaruroChori]

One of the ways in which vs is expected to work, is to pass one or more libraries as part of the application definition.
Those will be dynamically linked, and vs provides a runtime to express their UI.
Clearly this mode of operation is unsafe, so specific policy restrictions might prevent that.

Implementation-wise, this implies:

• dl with dlopen and dlsym to handle symbols.
• an FFI library so that calls can be constructed at runtime. libffi is the one I picked
• runtime support in the different backends to glue together types with the FFI library, to be implemented
• something able to parse the C header files into an intermediate form so that I can use that information in each backend.

The last point is the one which is totally unresolved.
Ideally it should be a library able to parse C headers, including the pre-processor stage, and return some kind of usable data structure (ast, whatever) to be used by all the backends.
Any idea would be very appreciated.

[KaruroChori]

For my future reference, but no answer yet.

• libffi
• How txiki.js does it, sadly in JS code https://github.com/saghul/txiki.js/blob/master/src/js/stdlib/ffi/ffiutils.js and the runtime implementation for qjs https://github.com/saghul/txiki.js/blob/master/src/mod_ffi.c
• We could try to externally generate and use https://clang.llvm.org/docs/IntroductionToTheClangAST.html?
• Or repurpose https://github.com/tree-sitter/tree-sitter-c/tree/master/examples since treesitter is already a dependency of the project