-
Notifications
You must be signed in to change notification settings - Fork 428
Moving runtime bindings into their own crate #382
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
Conversation
Currently the runtime bindings live inside of tensorflow-sys, which includes several packages for building tensorflow. These packages aren't needed for the runtime bindings at all, and this seems like the logical way to separate the two.
Hi @adamcrume , could I get some feedback on this when you get a chance? Thanks. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
RELEASING.md needs to be updated.
${cmd} | ||
|
||
echo "link! {\n$(cat src/runtime_linking/c_api.rs)" > src/runtime_linking/c_api.rs | ||
echo } >> src/runtime_linking/c_api.rs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All the runtime bits should be removed from tensorflow-sys/generate_bindgen_rs.sh.
Sorry for the delay! |
- RELEASING.md now has info about the new tensorflow-sys-runtime crate. - Additional info in the tensorflow-sys-runtime README.md showing how to use it. - Adding the version to tensorflow-sys-runtime in the main Cargo.toml - Removing runtime linking bindgen calls from tensorflow-sys/generate_bindgen_rs.sh
@adamcrume Thanks for the review. I've updated the PR with the requested changes, let me know if there's anything else. |
Thanks! |
@adamcrume Great, thanks for that. Any idea when I can expect a new version to be pushed to crates.io? |
The runtime bindings have no use for the the build-dependencies of tensorflow-sys, nor the build.rs. So to avoid pulling in those dependencies, and hopefully to keep things cleaner, I'd like to move them into their own crate.