Refactoring native builds and Java binding generation #521
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…tensorflow-platform.
Also refresh protos
* Exclude generation of JavaCPP bindings depending on TSL * Skip C++-API dependent method * Use official 2.15 Windows C build
This improves determinism and makes the gradients be computed correctly for unclear reasons. (#520) Co-authored-by: Nicolas Feybesse (nfeybesse@users.noreply.github.com)
|
Merged, thank you all! And let's being a new era for TensorFlow Java 🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As part of a everlasting initiative, we are moving out of building TensorFlow natively using Bazel to downloading the official builds being distributed in the Python wheels.
As we shuffled things around, we took an opportunity as well to facilitate the TensorFlow upgrades and the generation of all the Java bindings, including protos and ops.
This releases introduces a few breaking changes, the major one being that the classified JARs containing the native binaries is now
tensorflow-core-native, andtensorflow-core-apinow becoming a pure Java API.Version is updated to
1.0.0-SNAPSHOTas we are targeting this codebase to become the first official release of TensorFlow Java (1.0.0) in a very near future.