| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
src/main/java/com/google/devtools/build/lib/exec/SymlinkTreeHelper.java:
enable --windows_compatible flag on Windows to make build-runfiles.exe work.
scritps/bootstrap/compile.sh:
--windows_compatible will also be passed to a dummy build-runfiles.exe defined in complie.sh.
Which is actully a batch script, modify it to make it work.
-----
With the changes above, we are able to build bazel with bazel. But when you try to
run ./compile.sh compile /path/to/bazel again without clean up tmp directory, it will fail with
a permission deny error. The reason seems to be that you can't use build-runfile.exe to build the
same hard link twice, still trying to solve that.
--
Change-Id: I93340b1ba9fa415f6db963b106e264799e33ede3
Reviewed-on: https://bazel-review.googlesource.com/#/c/3334
MOS_MIGRATED_REVID=119751076
|
|
|
|
|
|
| |
It's not our code, so we can't do much about them.
Change-Id: If068995e494a398d2c8d05ba428c4d36dbc0e6a3
|
|
|
|
|
|
|
|
|
|
|
|
| |
The immmediate reason for this change is that we also need to add gRPC support to the proto rules, and we don't want to also support gRPC in a half-baked way.
This makes the Bazel binary much smaller and avoid giving false signals that we (for now) support protobuf compilation. The protobuf rules are only for compiling Bazel itself.
RELNOTES[INC]: Bazel does not embed protocol buffer-related rules anymore.
--
MOS_MIGRATED_REVID=119516246
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119255585
|
|
|
|
|
|
|
| |
Information in README.md about the statically linked x86_64 binary and the src/ directory got lost due to a snafu with updating the tree from the Google-internal version.
--
MOS_MIGRATED_REVID=119250383
|
|
|
|
|
|
| |
Let's at least keep versions consistent within one third-party library.
Change-Id: I707fc6cd90dcc21e354ea91439417ffe3c9827a4
|
|
|
|
| |
Change-Id: I9fac9d265ae9f1691be4dbb4b3bef6f35872b5ee
|
|
|
|
|
|
| |
Actually, it's a bit more files than strictly necessary, but it's easier to maintain this way.
Change-Id: I22bba190940c1695f491cd28c7a7a95018d77bb1
|
|
|
|
|
|
|
|
|
| |
protoc-mingw.exe dumps core for whatever reason, and these seem to work at least well enough for compile.sh . protoc-mingw.exe was apparently introduced due to a 1024-character path limit, but that doesn't break the continuous build.
Fixes #1101.
--
MOS_MIGRATED_REVID=118667728
|
|
|
|
|
|
|
| |
I didn't verify that this is the right thing, but it sure compiles. That's not a very high bar for Python rules, though.
--
MOS_MIGRATED_REVID=117543822
|
|
|
|
|
|
|
| |
//third_party/protobuf.
--
MOS_MIGRATED_REVID=117336377
|
| |
|
| |
|
|
|
|
| |
48ebb29a8ec118bf6b9ee39f6be42b57321c099a to third_party/protobuf.
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=114324917
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=114115200
|
|
|
|
|
|
|
|
|
| |
Native protoc-windows.exe fails to support paths longer that 1024
characters.
Needed for #276.
RELNOTES: None.
|
| |
|
|
|
|
|
|
|
| |
--
Change-Id: Ia70ca1b8482e10bc1ac91799aa238f8613e5c824
Reviewed-on: https://bazel-review.googlesource.com/#/c/1801
MOS_MIGRATED_REVID=100476467
|
| |
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=95640440
|
| |
|
|
--
MOE_MIGRATED_REVID=85702957
|