You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I'm working on a project that needs bindings both for python and for WASM. Because of this, I believe the easiest way to have the two different build systems work is to have two Cargo.toml files, one for bindings using PyO3 (py_Cargo.toml) and one using wasm-pack(wasm_Cargo.toml).
I was wondering whether it's possible then, to have maturin use this py_Cargo.toml file instead of looking for a Cargo.toml. I've tried:
maturin develop -m py_Cargo.toml
💥 maturin failed
Caused by: Cargo metadata failed. Does your crate compile with `cargo build`?
Caused by: `cargo metadata` exited with an error: error: the manifest-path must be a path to a Cargo.toml file
Am I missing something?
The text was updated successfully, but these errors were encountered:
Hi,
I'm working on a project that needs bindings both for python and for WASM. Because of this, I believe the easiest way to have the two different build systems work is to have two
Cargo.toml
files, one for bindings usingPyO3
(py_Cargo.toml
) and one usingwasm-pack
(wasm_Cargo.toml
).I was wondering whether it's possible then, to have
maturin
use thispy_Cargo.toml
file instead of looking for aCargo.toml
. I've tried:Am I missing something?
The text was updated successfully, but these errors were encountered: