Crates.io | napi_sym |
lib.rs | napi_sym |
version | 0.107.0 |
source | src |
created_at | 2022-10-05 14:14:40.004197 |
updated_at | 2024-11-10 04:48:31.110025 |
description | proc macro for writing N-API symbols |
homepage | |
repository | https://github.com/denoland/deno |
max_upload_size | |
id | 680558 |
size | 8,188 |
A proc_macro for Deno's Node-API implementation. It does the following things:
#[no_mangle]
and rewrites it as
unsafe extern "C" $name
.symbol_exports.json
.deno_napi::Result
to raw napi_result
.use deno_napi::napi_value;
use deno_napi::Env;
use deno_napi::Error;
use deno_napi::Result;
#[napi_sym::napi_sym]
fn napi_get_boolean(
env: *mut Env,
value: bool,
result: *mut napi_value,
) -> Result {
let _env: &mut Env = env.as_mut().ok_or(Error::InvalidArg)?;
// *result = ...
Ok(())
}
symbol_exports.json
A file containing the symbols that need to be put into the executable's dynamic symbol table at link-time.
This is done using /DEF:
on Windows, -exported_symbol,_
on macOS and
--export-dynamic-symbol=
on Linux. See cli/build.rs
.
On Windows, you need to generate the .def
file by running
tools/napi/generate_symbols_lists.js
.