Replies: 1 comment 1 reply
-
Depends on how portable you want your binary to be. If all you need is something that runs on the machine it was built on, I attempted to document this at https://gregoryszorc.com/docs/pyoxidizer/0.22.0/pyoxidizer_rust_generic_embedding.html. You may want to have a look at the CI jobs that build the |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
My aim is to embed python into a Rust app and have the Rust app manage its lifecycle. Ideally, I'd like the python interpreter to run in a separate process/thread and communicate back with the main rust program, and I'd like to include some of my custom python code. I'm assuming this is all possible.
With that in mind, I've used
cargo new
to create a new Hello World application, and I've addedpyembed
to mycargo.toml
. But now I'm a little confused as to what the workflow should be. Should I be usingcargo build
, orpyoxidizer build
to build the file?Beta Was this translation helpful? Give feedback.
All reactions