Skip to content

Conversation

@dreiss
Copy link
Contributor

@dreiss dreiss commented Nov 7, 2019

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:

  • 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 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
@dreiss dreiss requested review from IvanKobzarev and kostmo November 7, 2019 22:19
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
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
@dreiss
Copy link
Contributor Author

dreiss commented Dec 5, 2019

This landed.

@dreiss dreiss closed this Dec 5, 2019
@facebook-github-bot facebook-github-bot deleted the gh/dreiss/15/head branch January 4, 2020 15:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants