| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
| |
See https://github.com/bazelbuild/bazel/issues/2190
Closes #5005.
Change-Id: If665af264a23be0219c75ae087dd25db74d5e386
PiperOrigin-RevId: 192575414
|
|
|
|
|
|
|
| |
third_party/gtest can go away after this.
RELNOTES: None.
PiperOrigin-RevId: 190221581
|
|
|
|
|
|
|
|
| |
If `argument` does not contain `' '` and `'"'` and `escape_backslash` is false (i.e: no escaping needed), `escaped_arg` will allocate memory exactly once only.
Closes #4491.
PiperOrigin-RevId: 186962716
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Windows native {java,py,sh}_binary launcher
now picks up the RUNFILES_MANIFEST_FILE and
RUNFILES_DIR envvars from the environment. This
enables running such binaries even when they are
data-dependencies of other binaries and thus have
no runfiles (manifest or directory) of their own.
See https://github.com/bazelbuild/bazel/issues/4460
Change-Id: I1bc8e30f81b9932ea7c96ded2717ac9d0600403d
PiperOrigin-RevId: 185656004
|
|
|
|
|
|
| |
Closes #4489.
PiperOrigin-RevId: 184532916
|
|
|
|
|
|
|
| |
Fixed https://github.com/bazelbuild/bazel/issues/4408
Change-Id: Id62b25e675822bbed91a448e70bdcb76e722721e
PiperOrigin-RevId: 181591585
|
|
|
|
|
|
|
|
|
|
| |
Make sure the actual binary recieves exactly the same argument passed to
Windows exe launcher.
Fixed https://github.com/bazelbuild/bazel/issues/4001
Change-Id: I5db2d7c2f78de8865abc04a2d5b65d69685d43db
PiperOrigin-RevId: 178610493
|
|
|
|
|
|
|
| |
This will enable an easier transition from checked-in BUILD files to ones generated by copybara.
RELNOTES: None
PiperOrigin-RevId: 177514519
|
|
|
|
|
|
|
|
|
| |
Since src/tools/launcher is Windows specific, it doesn't actually work
on Linux. Here we select a dummy source file for cc targets non-Windows
platform.
Change-Id: I9a6550ea23a3656ad72cb46b9652f154e2fbf44f
PiperOrigin-RevId: 176350180
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add recursive test_suite rules for all tests that
ci.bazel.io runs for Windows, and set the
top-level test_suite as the CI test target.
Doing so shortens the command line and works
around https://github.com/bazelbuild/bazel/issues/3742
I verified that the old set of tests are the same
as the new set.
Change-Id: Id8d5da3f0c03c9b8969a9f8e1e9a3096888365aa
PiperOrigin-RevId: 169242858
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When the classpath is too long, the launcher creates a jar file to pass
the classpath value. This change makes the jar file's name random.
It fixed the bug that when running multiple instances of the same java binary,
they all try to create the same classpath jar file. For example, when
running java_test with shard_count > 1.
Also, we delete the classpath jar file after the program finishes, so
that we don't leave any garbages behind.
Change-Id: I67926b3ef76dcb1806797e977ecaa7c6763c5cf2
PiperOrigin-RevId: 169087032
|
|
|
|
|
|
|
| |
This will help us debug some Launcher errors.
RELNOTES: None
PiperOrigin-RevId: 168354216
|
|
|
|
|
| |
Change-Id: I25795c748fa98b9275ae34ead17fce02a57dc8e4
PiperOrigin-RevId: 166816800
|
|
|
|
|
|
|
| |
Fix https://github.com/bazelbuild/bazel/issues/3620
RELNOTES: None.
PiperOrigin-RevId: 166472158
|
|
|
|
|
|
|
|
|
|
|
| |
Now Bazel build a Windows exe binary to launch JVM for java_binary and
java_test.
The Java native launcher is implemented with the same logic and
functionalities as the original java shell stub script.
Change-Id: Ida40579bce82425f3506f9376b7256aa3edc265e
PiperOrigin-RevId: 166346445
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now Bazel build a Windows exe to launch the python self-extracting zip
file by default, using --windows_exe_launcher=0 to switch back to cmd
wrapper.
The extra zip file with shebang preprended is not built on Windows
anymore, even when using cmd wrapper.
Change-Id: Ic7060326f19ca6e2e73ea8d8211afd1c7618083c
PiperOrigin-RevId: 165707076
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. Extract some funtions into NativeLauncherUtil.java
So that they can also be used by Python and Java launcher.
2. Derive runfiles directory from mainExectuable
yielding "%{name}.cmd.runfiles" or "%{name}.exe.runfiles"
3. Removed bash_main_file key, we can assume the main file is next the
launcher just without .exe suffix.
By doing this, we don't have to worry about passing RunfilesPath or
ExecPath. RunfilesPath has ../ prefix for external file, ExecPath
contians ./bazel-out/... for generated file. If main file is a
generated file from external repository, neither of them are correct.
Change-Id: Ie0c35f6030f6229c28d935d8fb3cb6a8af5af29c
PiperOrigin-RevId: 165699975
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix the path we set in the exe launcher for the
RUNFILES_MANIFEST_FILE path. It now uses forward
slashes because it's to be consumed by the shell
script.
This is a follow-up to commit 837e1b3d4859140d29aaa6bbab8fbb008e6d701e
Change-Id: Id8331cdcf58adb31ed2b60ebbc57022a0bf32438
PiperOrigin-RevId: 164436539
|
|
|
|
|
|
|
|
|
|
|
| |
Fix the exe launcher of sh_binary rules to export
the RUNFILES_MANIFEST_ONLY and
RUNFILES_MANIFEST_FILE environment variables.
Fixes https://github.com/bazelbuild/bazel/issues/3492
Change-Id: I8507565f44c8b59f8218570306375cc083a41e03
PiperOrigin-RevId: 164095286
|
|
The native launcher is implemented based on this design doc:
https://docs.google.com/document/d/1z6Xv95CJYNYNYylcRklA6xBeesNLc54dqXfri0z0e14/edit?usp=sharing
Change-Id: I83bae844f792a587ce0e342a3c0f238b760afeaa
PiperOrigin-RevId: 162736269
|