Use ffi-napi, ref-napi, and related Node.js NAPI packages #11
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Since this package both executes and generates code which uses `ref`/`ffi`/`ffi-*` packages, they are added both as developer and peer dependencies.
> Represents a type that was referred to using an elaborated type keyword, e.g., `struct S`, or via a qualified name, e.g.,` N::M::type`, or both. - Supporting Elaborated types allows for a greatly expanded library generation. - Relies on corresponding support in `node-libclang`. See - https://clang.llvm.org/doxygen/classclang_1_1ElaboratedType.html - https://github.com/tjfontaine/node-libclang - https://github.com/joelpurra/node-libclang/tree/support-elaborated-type
- Support for the elaborated type requires the corresponding support in `libclang`. - If/when the patch gets merged in the upstream `libclang`, the version should be reverted. See - https://github.com/tjfontaine/node-libclang - https://github.com/joelpurra/node-libclang/tree/support-elaborated-type
- The original `ffi`, `ref`, and `ref-*` packages are outdated and unmaintained. - Fixes build/compatibility problems with Node.js v12+. - Uses `node-ffi-napi`. - Uses the dependency injection (DI, `-di` suffix) versions of `ref-*` with `ref-napi`. - Tested with Node.js v10 and v12, the currently supported LTS versions. See - https://github.com/node-ffi-napi - https://github.com/nodejs/Release
- Relies on corresponding support in `node-libclang`. See - https://github.com/tjfontaine/node-libclang - https://github.com/joelpurra/node-libclang/tree/ffi-napi
|
Forked and fixed quite a few more things, might help someone: https://github.com/node-ffi-packager/node-ffi-generate |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Forked and fixed quite a few more things: https://github.com/node-ffi-packager/node-ffi-generate
Note: includes commits from previous pull-requests. Should be merged to
masterone by one, but wanted to showcase the stepwise progress and allow for feedback.ffi,ref, andref-*packages are outdated and unmaintained.node-ffi-napi.-disuffix) versions ofref-*withref-napi.See