| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
| |
WindowsJniLoader.loadJniForTesting is just a
special case of what WindowsJniLoader.loadJni
already does, so we can just use the latter.
--
PiperOrigin-RevId: 144224388
MOS_MIGRATED_REVID=144224388
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is the behavior of the UnixJniLoader. In order to do that, this
change also moved the runfiles support on Windows in its own library
that the WindowsJniLoader can use to load the JNI library from tests.
Also add the JNI library on Windows to all test that use the JNI library
on Unix.
Fixes #2300.
--
Change-Id: I2eb9207c3aa310d95912a48f64f676957c47cd34
Reviewed-on: https://cr.bazel.build/8045
PiperOrigin-RevId: 143114397
MOS_MIGRATED_REVID=143114397
|
|
|
|
|
|
|
| |
We should really do something about the mess that is loading our JNI libraries -- io.bazel.EnableJNI is mentioned eight times in the code in various diverse contexts. This change is not the right place to do it, though.
--
MOS_MIGRATED_REVID=126570481
|
|
|
|
|
|
|
| |
sane Java API for now)
--
MOS_MIGRATED_REVID=126306559
|
|
Tested by hacking in a call to a JNI method into BatchMain.java .
--
Change-Id: I77b0731fa6b81f8cbc80cf2a31d427764fad6ad1
Reviewed-on: https://bazel-review.googlesource.com/#/c/3908/
MOS_MIGRATED_REVID=125955521
|