-
Notifications
You must be signed in to change notification settings - Fork 26.3k
Update fbjni and enable PyTorch JNI build #29413
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
Closed
Closed
Conversation
This file contains hidden or 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
Summary: Add a "BUILD_JNI" option that enables building PyTorch JNI bindings and fbjni. This is off by default because it adds a dependency on jni.h. Also update to the latest fbjni so we can inhibit building its tests, because they depend on gtest. Test Plan: - Built on dev server. - Verified that libpytorch_jni links after libtorch when both are built in a parallel build.
dreiss
added a commit
that referenced
this pull request
Nov 7, 2019
Summary: Add a "BUILD_JNI" option that enables building PyTorch JNI bindings and fbjni. This is off by default because it adds a dependency on jni.h. Also update to the latest fbjni so we can inhibit building its tests, because they depend on gtest. Test Plan: - Built on dev server. - Verified that libpytorch_jni links after libtorch when both are built in a parallel build. ghstack-source-id: 589a7f3 Pull Request resolved: #29413
Summary: Add a "BUILD_JNI" option that enables building PyTorch JNI bindings and fbjni. This is off by default because it adds a dependency on jni.h. Also update to the latest fbjni so we can inhibit building its tests, because they depend on gtest. Test Plan: - Built on dev server. - Verified that libpytorch_jni links after libtorch when both are built in a parallel build.
dreiss
added a commit
that referenced
this pull request
Nov 8, 2019
Summary: Add a "BUILD_JNI" option that enables building PyTorch JNI bindings and fbjni. This is off by default because it adds a dependency on jni.h. Also update to the latest fbjni so we can inhibit building its tests, because they depend on gtest. Test Plan: - Built on dev server. - Verified that libpytorch_jni links after libtorch when both are built in a parallel build. ghstack-source-id: 03da950 Pull Request resolved: #29413
IvanKobzarev
approved these changes
Nov 8, 2019
Summary: Add a "BUILD_JNI" option that enables building PyTorch JNI bindings and fbjni. This is off by default because it adds a dependency on jni.h. Also update to the latest fbjni so we can inhibit building its tests, because they depend on gtest. Test Plan: - Built on dev server. - Verified that libpytorch_jni links after libtorch when both are built in a parallel build.
Summary: Add a "BUILD_JNI" option that enables building PyTorch JNI bindings and fbjni. This is off by default because it adds a dependency on jni.h. Also update to the latest fbjni so we can inhibit building its tests, because they depend on gtest. Test Plan: - Built on dev server. - Verified that libpytorch_jni links after libtorch when both are built in a parallel build.
Summary: Add a "BUILD_JNI" option that enables building PyTorch JNI bindings and fbjni. This is off by default because it adds a dependency on jni.h. Also update to the latest fbjni so we can inhibit building its tests, because they depend on gtest. Test Plan: - Built on dev server. - Verified that libpytorch_jni links after libtorch when both are built in a parallel build.
dreiss
added a commit
that referenced
this pull request
Nov 13, 2019
Summary: - Add a "BUILD_JNI" option that enables building PyTorch JNI bindings and fbjni. This is off by default because it adds a dependency on jni.h. - Update to the latest fbjni so we can inhibit building its tests, because they depend on gtest. - Set JAVA_HOME and BUILD_JNI in Linux binary build configurations if we can find jni.h in Docker. Test Plan: - Built on dev server. - Verified that libpytorch_jni links after libtorch when both are built in a parallel build. ghstack-source-id: f9908e1 Pull Request resolved: #29413
Summary: Add a "BUILD_JNI" option that enables building PyTorch JNI bindings and fbjni. This is off by default because it adds a dependency on jni.h. Also update to the latest fbjni so we can inhibit building its tests, because they depend on gtest. Test Plan: - Built on dev server. - Verified that libpytorch_jni links after libtorch when both are built in a parallel build.
dreiss
added a commit
that referenced
this pull request
Nov 14, 2019
Summary: - Add a "BUILD_JNI" option that enables building PyTorch JNI bindings and fbjni. This is off by default because it adds a dependency on jni.h. - Update to the latest fbjni so we can inhibit building its tests, because they depend on gtest. - Set JAVA_HOME and BUILD_JNI in Linux binary build configurations if we can find jni.h in Docker. Test Plan: - Built on dev server. - Verified that libpytorch_jni links after libtorch when both are built in a parallel build. ghstack-source-id: 128c672 Pull Request resolved: #29413
Summary: Add a "BUILD_JNI" option that enables building PyTorch JNI bindings and fbjni. This is off by default because it adds a dependency on jni.h. Also update to the latest fbjni so we can inhibit building its tests, because they depend on gtest. Test Plan: - Built on dev server. - Verified that libpytorch_jni links after libtorch when both are built in a parallel build.
Summary: Add a "BUILD_JNI" option that enables building PyTorch JNI bindings and fbjni. This is off by default because it adds a dependency on jni.h. Also update to the latest fbjni so we can inhibit building its tests, because they depend on gtest. Test Plan: - Built on dev server. - Verified that libpytorch_jni links after libtorch when both are built in a parallel build.
Summary: Add a "BUILD_JNI" option that enables building PyTorch JNI bindings and fbjni. This is off by default because it adds a dependency on jni.h. Also update to the latest fbjni so we can inhibit building its tests, because they depend on gtest. Test Plan: - Built on dev server. - Verified that libpytorch_jni links after libtorch when both are built in a parallel build.
dreiss
added a commit
that referenced
this pull request
Nov 15, 2019
Summary: - Add a "BUILD_JNI" option that enables building PyTorch JNI bindings and fbjni. This is off by default because it adds a dependency on jni.h. - Update to the latest fbjni so we can inhibit building its tests, because they depend on gtest. - Set JAVA_HOME and BUILD_JNI in Linux binary build configurations if we can find jni.h in Docker. Test Plan: - Built on dev server. - Verified that libpytorch_jni links after libtorch when both are built in a parallel build. ghstack-source-id: cafc1e3 Pull Request resolved: #29413
Summary: Add a "BUILD_JNI" option that enables building PyTorch JNI bindings and fbjni. This is off by default because it adds a dependency on jni.h. Also update to the latest fbjni so we can inhibit building its tests, because they depend on gtest. Test Plan: - Built on dev server. - Verified that libpytorch_jni links after libtorch when both are built in a parallel build.
dreiss
added a commit
that referenced
this pull request
Nov 15, 2019
Summary: - Add a "BUILD_JNI" option that enables building PyTorch JNI bindings and fbjni. This is off by default because it adds a dependency on jni.h. - Update to the latest fbjni so we can inhibit building its tests, because they depend on gtest. - Set JAVA_HOME and BUILD_JNI in Linux binary build configurations if we can find jni.h in Docker. Test Plan: - Built on dev server. - Verified that libpytorch_jni links after libtorch when both are built in a parallel build. ghstack-source-id: d411953 Pull Request resolved: #29413
dreiss
added a commit
to dreiss/pytorch
that referenced
this pull request
Nov 15, 2019
Summary: - Add a "BUILD_JNI" option that enables building PyTorch JNI bindings and fbjni. This is off by default because it adds a dependency on jni.h. - Update to the latest fbjni so we can inhibit building its tests, because they depend on gtest. - Set JAVA_HOME and BUILD_JNI in Linux binary build configurations if we can find jni.h in Docker. Test Plan: - Built on dev server. - Verified that libpytorch_jni links after libtorch when both are built in a parallel build. ghstack-source-id: d411953 Pull Request resolved: pytorch#29413
Contributor
Author
|
This landed. |
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.
Stack from ghstack:
Summary:
Add a "BUILD_JNI" option that enables building PyTorch JNI bindings and
fbjni. This is off by default because it adds a dependency on jni.h.
Also update to the latest fbjni so we can inhibit building its tests,
because they depend on gtest.
Test Plan:
in a parallel build.