Skip to content
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

Is it possible to use a manifest-path to a file not named "Cargo.toml" #686

Closed
AmitPr opened this issue Nov 16, 2021 · 3 comments
Closed
Labels
upstream Upstream issue

Comments

@AmitPr
Copy link

AmitPr commented Nov 16, 2021

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?

@messense
Copy link
Member

Can you make cargo build --manifest-path py_Cargo.toml work? (AFAIK it's not working) If not maturin also can't do it.

@messense messense added the question Further information is requested label Nov 17, 2021
@messense
Copy link
Member

messense commented Nov 17, 2021

rust-lang/cargo#6690

I encourage you to comment on the upstream cargo issue so it may get fixed someday.

@messense messense added upstream Upstream issue and removed question Further information is requested labels Nov 17, 2021
@AmitPr
Copy link
Author

AmitPr commented Nov 17, 2021

I see, not super familiar with rust yet :)
Thanks for the info!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
upstream Upstream issue
Projects
None yet
Development

No branches or pull requests

2 participants