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

shell toolchain, design: including common bintools #5265

laszlocsomor opened this Issue May 25, 2018 · 1 comment


None yet
2 participants
Copy link

laszlocsomor commented May 25, 2018

Description of the problem / feature request:

Design a mechanism to express that a rule executing a shell command depends on certain command line tools.

Feature requests: what underlying problem are you trying to solve with this feature?

Not every machine has Bash installed, and those that do don't always install Bash at the same location, or have another shell interpreter installed. To accommodate all scenarios, I designed how to turn Bash, or broadly speaking, the Shell, into a toolchain. The efforts is tracked as #4319.

However what Bazel treats as "the shell" is more than just the shell interpreter. Bazel assumes that not only Bash is the shell and it's installed at a fixed location, but also that common GNU binutils and other common programs such as "zip" or "grep" are also installed and are on the PATH.

Rules that execute shell commands also expect these tools to exist and be on the PATH. Bazel currently has no way to express that such rules depend on these tools.


This comment has been minimized.

Copy link

laszlocsomor commented Jun 28, 2018

FYI, I don't plan to work on this for the foreseeable future (in the next few months).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment