cad-editor/.cargo/config.toml

# getrandom 0.3 (pulled by ahash via acadrust) needs this cfg to select its
# browser backend on wasm32-unknown-unknown, alongside its `wasm_js` feature
# (enabled in Cargo.toml for the wasm target). Without it the web build fails
# with "wasm32-unknown-unknown targets are not supported by default".
#
# `-Cstrip=none` overrides the release profile's `strip = true` for the wasm
# target only: stripping removes the `target_features` custom section, so
# `wasm-opt` can no longer see that `bulk-memory` is enabled and rejects the
# module's memory.fill/copy ops ("require bulk memory"). Native release binaries
# stay stripped; only the wasm keeps its feature section.
[target.wasm32-unknown-unknown]
rustflags = ['--cfg', 'getrandom_backend="wasm_js"', '-Cstrip=none']
build(web): restore the wasm build — gate native-only deps off wasm The web build had bit-rotted: native-only features added since it last compiled pulled crates that don't build for wasm32-unknown-unknown. - printpdf (PDF export / printing) → native-only target; the web build gets stub export_pdf / print_wires. It pulls a wasm-incompatible memchr 1.0.2 via lopdf → nom_locate, and the web has no filesystem. - getrandom 0.3 (via ahash via acadrust) → enable its wasm_js feature and add the matching --cfg getrandom_backend rustflag in .cargo/config.toml. - ocs_plugin_api "host" feature (out-of-process plugin runtime: interprocess, libloading, memmap2, rkyv) → native-only target; the web gets the dependency-free manifest/ribbon contract. The host code was already wasm-gated; only the Cargo wiring pulled it in unconditionally. `trunk build --release` succeeds again. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> 2026-06-25 14:11:18 +03:00			`# getrandom 0.3 (pulled by ahash via acadrust) needs this cfg to select its`
			# browser backend on wasm32-unknown-unknown, alongside its `wasm_js` feature
			`# (enabled in Cargo.toml for the wasm target). Without it the web build fails`
			`# with "wasm32-unknown-unknown targets are not supported by default".`
fix(web): keep wasm target_features section so wasm-opt accepts bulk-memory The release profile's strip = true (added in #324) strips the wasm target_features custom section. Without it, wasm-opt can't tell that bulk-memory is enabled and rejects the module's memory.fill/copy ops ("operations require bulk memory"), failing the release web build — the newer Rust toolchain now emits those ops by default. Override strip only for the wasm target with -Cstrip=none, so native release binaries stay stripped while the wasm keeps its feature section. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> 2026-07-10 09:36:43 +03:00			`#`
			# `-Cstrip=none` overrides the release profile's `strip = true` for the wasm
			# target only: stripping removes the `target_features` custom section, so
			# `wasm-opt` can no longer see that `bulk-memory` is enabled and rejects the
			`# module's memory.fill/copy ops ("require bulk memory"). Native release binaries`
			`# stay stripped; only the wasm keeps its feature section.`
build(web): restore the wasm build — gate native-only deps off wasm The web build had bit-rotted: native-only features added since it last compiled pulled crates that don't build for wasm32-unknown-unknown. - printpdf (PDF export / printing) → native-only target; the web build gets stub export_pdf / print_wires. It pulls a wasm-incompatible memchr 1.0.2 via lopdf → nom_locate, and the web has no filesystem. - getrandom 0.3 (via ahash via acadrust) → enable its wasm_js feature and add the matching --cfg getrandom_backend rustflag in .cargo/config.toml. - ocs_plugin_api "host" feature (out-of-process plugin runtime: interprocess, libloading, memmap2, rkyv) → native-only target; the web gets the dependency-free manifest/ribbon contract. The host code was already wasm-gated; only the Cargo wiring pulled it in unconditionally. `trunk build --release` succeeds again. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> 2026-06-25 14:11:18 +03:00			`[target.wasm32-unknown-unknown]`
fix(web): keep wasm target_features section so wasm-opt accepts bulk-memory The release profile's strip = true (added in #324) strips the wasm target_features custom section. Without it, wasm-opt can't tell that bulk-memory is enabled and rejects the module's memory.fill/copy ops ("operations require bulk memory"), failing the release web build — the newer Rust toolchain now emits those ops by default. Override strip only for the wasm target with -Cstrip=none, so native release binaries stay stripped while the wasm keeps its feature section. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> 2026-07-10 09:36:43 +03:00			`rustflags = ['--cfg', 'getrandom_backend="wasm_js"', '-Cstrip=none']`