-
Notifications
You must be signed in to change notification settings - Fork 104
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
building rust-cpython #165
Comments
looks like you need to specify edit: if there's a spot in the rules_rust documentation would have helped, definitely open a PR. The docs can use some work. |
yes, that is it. Thanks. pyo3 works now, cpyhon example fails with
|
|
That would be better opened as an issue in rules_rust if it doesn't actually work with python. That being said, bazel-out/k8-fastbuild-.../bin is a part of bazel's building and sandboxing process, so you may need post processing steps to use a library without bazel's knowledge. |
yes, i made it work by some
|
Hopefully this will make it clear that the 2018 edition needs to be explicitly specified. This caught me by surprise initially, and seems to have popped up in a few other areas. See google/cargo-raze#165
Not off hand. That looks to be a specific issue related to the usage of rust_cpython macro, which I'm not familiar with. |
the problem is I can build the code with cargo, but not with bazel. |
yes, they do, I explicitly avoided running the |
Hopefully this will make it clear that the 2018 edition needs to be explicitly specified. This caught me by surprise initially, and seems to have popped up in a few other areas. See google/cargo-raze#165 See also #335 for discussion on edition defaults from this PR.
updating one of the dependencies ( |
i am trying to build pyo3 and rust-cpython with bazel (https://github.com/ali5h/bazel_rust_python).
I finally got it to a state the crates can be built, but the main code cannot. Need help making this work. Currently on the sample repo posted above this happens for cpython sample:
Similarly for pyo3:
I am afraid i am missing something obvious here, bc errors are similar.
The text was updated successfully, but these errors were encountered: