3 ms·
I'm more interested in how this was automatically generated rather than in the end product itself.
by 4ad 14y ago
I'm more interested in how this was automatically generated rather than in the end product itself.
- olalonde 14y agoPossibly with https://github.com/tjfontaine/node-libclang https://github.com/tjfontaine/node-libclang. I'm actually working on a node module that will automatically parse header files using libclang and make native dynamic libraries available with no configuration required on the end of the developer. It will eventually be part of https://github.com/olalonde/better-require https://github.com/olalonde/better-require if you're interested.
- xdenser 14y agoHow about pure JS PEG generated parser instead of clang? https://github.com/xdenser/node-ffiCparser https://github.com/xdenser/node-ffiCparser though that is not finished yet
- olalonde 14y agoAn didn't know about this, looks great. Would you be interested in helping me write an add-on for better-require? Anyways, I'll try it out and see how it works out.
- Benvie 14y agoThe actual code generator I haven't published because it was kind of a pile of crap. I created bindings to libclang as well here but haven't finished rewriting a more generalized code generator from it https://github.com/Benvie/node-clang/blob/master/bindings.js https://github.com/Benvie/node-clang/blob/master/bindings.js