-
-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invalid Windows .dll #67
Comments
so you did get this working with linux? the ffi function should be reworked soon to expect a buffer, instead of Go freeing the output. either 1) dll never worked or 2) buffer needs to be implemented i haven't tested the windows dll because Bun does not yet support windows |
They released experimental Bun build for Windows along with
|
I compiled valid |
I'm going to look into the Windows DLL myself soon and figure out why GitHub Actions is causing problems. Also, I will likely implement a child process / worker implementation for Node on the r6-dissect npm package. Node FFI just looks a little buggy and slow. |
Thanks for the scripts, I will consider your changes when I look into the release workflow |
Consider koffi FFI library. new (require("worker_threads").Worker)(`
require("fs").writeFileSync("./test/dump.json",
require("koffi")
.load("./lib/libr6dissect-windows-amd64.dll")
.cdecl("dissect_read", "str", ["str"])
("./test/Match-2023-09-23_12-03-31-55-R07.rec")
)`,
{ eval: true }
) Not working: new (require("worker_threads").Worker)(`
require("fs").writeFileSync("./test/dump.json",
require("ffi-napi")
.Library("./lib/libr6dissect-windows-amd64.dll",
{ dissect_read: ["string", ["string"]] }
).dissect_read("./test/Match-2023-09-23_12-03-31-55-R07.rec")
)`,
{ eval: true }
) |
Describe the bug
Something is wrong with Windows
.dll
. I'm trying to portr6-dissect-bun
to Node.js withnode-ffi-napi
.It gives a V8 failure:
node
:16.14.1
ffi-napi
:4.0.3
To Reproduce
Steps to reproduce the behavior:
libr6dissect.dll
Expected behavior
It should work the same as
libr6dissect.so
The text was updated successfully, but these errors were encountered: