| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
| |
Also add a helper method to GlobalVariables to
retrieve this path, thus concentrating the
assumptions about the layout of extracted_binaries
in one place.
Change-Id: If172b6f5bf4451845ad89d3d488ef2a2c2e5d286
PiperOrigin-RevId: 158241854
|
|
|
|
|
|
|
|
|
|
|
| |
These changes addresses issues where Windows users have a space in their username. Allows the default output_base path to be used.
Closes #2491.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/2491
PiperOrigin-RevId: 146773331
MOS_MIGRATED_REVID=146773331
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
| |
Assuming that some POSIX-shell be installed as /bin/sh is more
portable than assuming bash being installed as /bin/bash. Also,
not using bash-extensions is generally more portable.
--
Change-Id: I76877bbcd848d78aaa04bab22a38890a02f6b814
Reviewed-on: https://bazel-review.googlesource.com/#/c/3800
MOS_MIGRATED_REVID=124815102
|
|
|
|
|
|
|
| |
The -X option removes UID/GID information from the zip file, which of course is non-hermetic. There is still some weirdness with install_base_key, but I couldn't figure out what that is: the files that are checksummed are always the same and they are in the same order.
--
MOS_MIGRATED_REVID=107484288
|
|
|
|
|
|
|
|
|
| |
embedded tools.
The previous change got the order of the parameters of package-bazel.sh wrong, thus building a non-functional bazel binary.
--
MOS_MIGRATED_REVID=105742752
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Broke bazel on mac
*** Original change description ***
Add a //src:bazel-notools target that is the same as the Bazel binary except without the embedded tools.
Its use requires the addition of a local_workspace(name = "bazel_tools", path=...) to the WORKSPACE file. It is useful if you don't care about the set of embedded tools (because you provide them to Bazel in another way anyway) but you do care about the size of the Bazel binary (it's 16 MB compared to 56 MB with the tools).
--
MOS_MIGRATED_REVID=105553886
|
|
without the embedded tools.
Its use requires the addition of a local_workspace(name = "bazel_tools", path=...) to the WORKSPACE file. It is useful if you don't care about the set of embedded tools (because you provide them to Bazel in another way anyway) but you do care about the size of the Bazel binary (it's 16 MB compared to 56 MB with the tools).
--
MOS_MIGRATED_REVID=105499508
|