@crossbind/core-embind-rust 2.0.0-beta.62 → 2.0.0-beta.63

package/README.md

@@ -2,7 +2,7 @@
 
 Rust **producer** for the crossbind embind registration protocol. Write an idiomatic Rust
 struct, register it, and it surfaces in JS as a real class - on web through emscripten's
-embind, on mobile through [`@crossbind/core-embind-jsi`](../core-embind-jsi) - **with no
+embind, on mobile through [`@crossbind/core-embind-jsi`](../embind-jsi) - **with no
 generated C++ wrapper and no cbindgen header**. The Rust side talks straight to the
 registration ABI that both hosts already consume.
 
@@ -92,7 +92,8 @@ On import the toolchain synthesizes a self-contained bridge crate under
 `<project>/.crossbind/rust-bridges/<name>/` (the user file is embedded via `#[path] mod user;` -
 no copy) plus a `counter.rs.d.ts` next to the source for full editor typing. The native builds
 bundle every app-local surface into ONE super staticlib (`rust-bridges/_app_super`) and link it
-into the app lib (iOS: merged into the force_loaded react-native-crossbind.a; Android: whole-archive).
+into the app lib (iOS: merged into the force_loaded react-native-crossbind.a; Android and Node.js
+addons: whole-archive, on Windows through its keep symbol).
 
 App-local surfaces can use UPSTREAM crates directly - the C++-style model where the app writes
 its own thin surface over a linked library and no crossbind package is involved. Declare the crates
@@ -165,7 +166,10 @@ constructor share one object), and is linked lazily with that symbol pinned
 (iOS `-Wl,-u,_crossbind_keep_<lib>`, Android `-Wl,--undefined=crossbind_keep_<lib>`) - the registration
 object is pulled, libstd stays lazy and deduplicates. Manual-bindings crates (no keep symbol)
 still fall back to force_load/whole-archive and are therefore safe only as the app's single
-Rust archive.
+Rust archive. On Windows the super staticlib links lazily too: two crates in it may import one
+DLL through raw-dylib (std and getrandom both import `ProcessPrng`), and lld cannot load the
+repeated import tables whole. There the link pins `crossbind_keep_crossbind_app_super()`, which
+reaches the keep symbol each app bridge exports; the super builds every bridge as one object.
 
 Web specifics: wasm-ld's `-u` does NOT pull archive members, so the wasm link pins keep symbols
 with `-Wl,--export=crossbind_keep_<lib>` instead; and any Rust archive in the link makes `buildWasm`

package/crate/src/lib.rs

@@ -173,7 +173,9 @@ macro_rules! bindings {
             }
             #[used]
             #[cfg_attr(target_vendor = "apple", link_section = "__DATA,__mod_init_func")]
-            #[cfg_attr(not(target_vendor = "apple"), link_section = ".init_array")]
+            // The Windows CRT runs no .init_array; it calls what .CRT$XCU holds when the DLL loads.
+            #[cfg_attr(windows, link_section = ".CRT$XCU")]
+            #[cfg_attr(not(any(target_vendor = "apple", windows)), link_section = ".init_array")]
             static __CROSSBIND_EMBIND_CTOR: extern "C" fn() = __crossbind_embind_ctor;
         };
     };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@crossbind/core-embind-rust",
-  "version": "2.0.0-beta.62",
+  "version": "2.0.0-beta.63",
   "description": "Rust producer for the crossbind embind registration protocol - bind Rust structs as classes reachable from JS on web (embind) and mobile (embind-jsi). Research/spike stage.",
   "homepage": "https://github.com/crossbind/crossbind/tree/main/core/embind-rust#readme",
   "repository": {