-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
deno-gyp #1654
Comments
You mean GN, right? We don't use GYP here. There was a discussion about native modules during September-November or so but turned out unconclusive, but I definitely would like this support, the question is: how? |
I personally think a big selling point is message-passing FFI like Ryan talked about in JSConf rather than having deno deal with the whole toolchain like Node has to |
I'm open to suggestions. Native extensions are difficult and insecure. Maybe we can do something with WASM. For the time being we have our arms full just making the basic modules work. |
WASM would be ideal for some use cases, it certainly would be secure. Additional external bindings though would be a problem, but that is the security problem with native extensions. |
wasm sounds like an excellent extension point except for where additional system APIs are required. |
@benjamingr ye, but my issue was especially for system apis such as OpenCL, CUDA, TensorFlow etc |
indeed - let's move the discussion to #296 |
#654 is also related. Just want to link them together. |
Idea: add something like
node-gyp
for native modules.The text was updated successfully, but these errors were encountered: