| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | Make it easier for tools/bazel wrapper script to find bazel-real |  Dan Fabulich | 2016-12-02 |
| | | | | | | | | | | | | | | | | | | The launcher script uses "exec -a" to launch the wrapper, but if the wrapper script is itself a Bash script, Bash will set "$0" to be the path to the wrapper script, not the path to the launcher script. To work around this, we've been having our wrapper script search the user's PATH environment variable for bazel-real, but that doesn't work well with the IntelliJ plugin for Bazel, which may not use the expected PATH environment. -- Change-Id: I402ad29d5b809be8e687e217e19c03e7ac3eb972 Reviewed-on: https://cr.bazel.build/7550 PiperOrigin-RevId: 140851992 MOS_MIGRATED_REVID=140851992 | ||
| * | Replace #!/bin/bash -eu with #!/bin/bash and "set -eu". Otherwise, the "-eu" ↵ |  Philipp Wollermann | 2016-06-21 |
| | | | | | | | | | | is not picked up when you run the scripts manually using "bash script.sh". This is also in our shell style guide: "Executables must start with #!/bin/bash and a minimum number of flags. Use set to set shell options so that calling your script as bash <script_name> does not break its functionality." -- MOS_MIGRATED_REVID=125450962 | ||
| * | Create a wrapper script which looks for an executable in the workspace |  Brian Silverman | 2016-01-20 |
| This executable in the workspace can be another Bazel binary whose version will change with the code it's next to, or a shell script which downloads a fixed version from some location. RELNOTES: A tools/bazel script in the workspace will be executed as an opportunity to use a fixed version of Bazel (not implemented for the homebrew recipe yet). Fixes #521 -- Change-Id: Id06177d9c2b259cd9d6fd62edb5abe541342dd05 Reviewed-on: https://bazel-review.googlesource.com/2620 MOS_MIGRATED_REVID=112477232 | |||
 |
index : bazel | |
| a fast, scalable, multi-language and extensible build system |
| aboutsummaryrefslogtreecommitdiffhomepage |