-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Windows, native launcher: sh_binary missing data dependencies #3839
Comments
Never mind, this is not a bug in the launcher, but in the example. I'll send a fix. |
One possible fix is to define and use |
This bug directly influences the usability of I'd like Bazel to treat shell scripts as just another language like Python, and to require Bash only if the targets depend on I'm making this P3 for now, because I believe other languages are more important on Windows and the practical limitation with a sub-par support for |
The targets in //examples/shell:* now use the Bash runfiles library in @bazel_tools//tools/bash/runfiles and work on Windows. Fixes bazelbuild#3839
The targets in //examples/shell:* now use the Bash runfiles library in @bazel_tools//tools/bash/runfiles and work on Windows. Also undef the RUNFILES_* envvars in bazel_example_test::test_shell (which builds the shell example project) so that the runfiles library discovers its own runfiles instead of trying (and failing) to use the enclosing test's runfiles (which it shouldn't use, because the test executes "bazel run //examples/shell:bin" so that target's runfiles are independent of the enclosing test's runfiles). Fixes bazelbuild#3839 Fix bazel_example_test: undef RUNFILES_* envvars Change-Id: I44f9bf9b11f7fac0e1c0995a44c2336846dc2bc8
The targets in //examples/shell:* now use the Bash runfiles library in @bazel_tools//tools/bash/runfiles and work on Windows. Also undef the RUNFILES_* envvars in bazel_example_test::test_shell (which builds the shell example project) so that the runfiles library discovers its own runfiles instead of trying (and failing) to use the enclosing test's runfiles (which it shouldn't use, because the test executes "bazel run //examples/shell:bin" so that target's runfiles are independent of the enclosing test's runfiles). Fixes bazelbuild#3839 Change-Id: I44f9bf9b11f7fac0e1c0995a44c2336846dc2bc8
The targets in //examples/shell:* now use the Bash runfiles library in @bazel_tools//tools/bash/runfiles and work on Windows. Also undef the RUNFILES_* envvars in bazel_example_test::test_shell (which builds the shell example project) so that the runfiles library discovers its own runfiles instead of trying (and failing) to use the enclosing test's runfiles (which it shouldn't use, because the test executes "bazel run //examples/shell:bin" so that target's runfiles are independent of the enclosing test's runfiles). Fixes bazelbuild#3839 Closes bazelbuild#5480. Change-Id: I44f9bf9b11f7fac0e1c0995a44c2336846dc2bc8 PiperOrigin-RevId: 202313105
Description of the problem / feature request / question:
When using the native launcher, sh_binary rules miss their data dependencies.
If possible, provide a minimal example to reproduce the problem:
Environment info
Operating System:
Windows 10
Bazel version (output of
bazel info release
):0.6.0
The text was updated successfully, but these errors were encountered: