| Commit message (Collapse) | Author | Age |
|
|
|
| |
Split out from https://github.com/bazelbuild/bazel/pull/5439
|
|
|
|
| |
This reverts commit 6fd4e0edd4de22dec9eda13dc0b29214f2ca117e.
|
| |
|
|
|
|
| |
This reverts commit a2cac548616e6e6f433df27146c2971f352a4041.
|
| |
|
|
|
|
| |
Change-Id: I3648aadad5895f80051ada39d0ca862dd437cc58
|
|
|
|
|
|
|
|
|
| |
Update protobuf to @laszlocsomor's fork of protobuf. This is essentially
the development version of protobuf 3.2.0 and windows specific fixes
from laszlo. Those fixes will be merged into protobuf soon:
https://github.com/google/protobuf/pull/2969.
Change-Id: Id88cd7e5b2c27ab74f3ecfa1e127e5a863f2deb3
|
|
|
|
|
|
|
| |
This reverts commit 5235d06159ba6fee412bee261ea7867d061252b0.
Unfortunately, we noticed several build errors / test failures internally due this
change.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update protobuf to @laszlocsomor's fork of protobuf. This is essentially
the development version of protobuf 3.2.0 and windows specific fixes
from laszlo. Those fixes will be merged into protobuf soon:
https://github.com/google/protobuf/pull/2969).
For instructions on how to update protobuf for bazel see
README.bazel.md.
Change-Id: Ic1daafe30270cb6bcc6231e6c94fb670af0475e7
|
|
|
|
| |
This reverts commit ea82aa115794b019472b44d4f94ed902c1217f30.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update protobuf to @laszlocsomor's fork of protobuf. This is essentially
the development version of protobuf 3.2.0 and windows specific fixes
from laszlo. Those fixes will be merged into protobuf soon:
https://github.com/google/protobuf/pull/2969).
For instructions on how to update protobuf for bazel see
README.bazel.md.
Change-Id: I4f663955b0baeea3232b69ce32d9292427f5274a
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 2346f5a01561f695a2b2ba7655359d5020105077.
It breaks bazel build in freebsd[1]. The solution is to patch
https://svnweb.freebsd.org/ports/head/devel/protobuf/files/. I
rolled-back this since the other builds will not automatically start if
Bazel is broken.
[1] http://ci.bazel.io/view/Bazel%20bootstrap%20and%20maintenance/job/Bazel/JAVA_VERSION=1.8,PLATFORM_NAME=freebsd-11/1312/
Change-Id: I7e939a4293d799ab6dd67f93d219d1efdf4cd901
|
|
|
|
|
|
|
| |
with some backports from HEAD
(:java_toolchain, internal_gen_well_known_protos_java)
Change-Id: I54be8809f411ec8cb02203b478f699e1fccb5f62
|
|
|
|
|
|
| |
Also, rename rules in third_party/protobuf/3.0.0/BUILD to match upstream protobuf.
Change-Id: I343982e752722ebb2461fb08e722558cea2f06b9
|
|
|
|
|
|
|
|
|
| |
1. Removed "protobuf" which used to point at the Java proto runtime.
2. Added "protobuf" that points at the C++ proto runtime (protobuf_clib also currently points there)
3. Added "protobuf_java_util" which points at Java proto utils (protobuf-util also currently points there)
4. Removed some aliases which aren't used in Bazel.
Change-Id: If23a9797af8d87fd6df89bf9bad361288f2e0565
|
|
|
|
|
|
| |
to match the name in the upstream protobuf project.
Change-Id: I0ac9612c2151f9b96aca1904b192b5b525d021a2
|
| |
|
|
|
|
|
|
| |
Commit 6d31cb was an internal reorganization of google repository
that should have resulted in no change. Due to a bug in our export
process it deleted several files in third_party.
|
|
|
|
|
| |
PiperOrigin-RevId: 142666783
MOS_MIGRATED_REVID=142666783
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Use proto_lang_toolchain() in java_proto_library, after fixing breakage.
Verified on Jenkins, http://ci.bazel.io/job/Gerrit-bazel-tests/169/
*** Original change description ***
Automated [] rollback of commit a396b070ae36032a973672e11145533621c39edc.
*** Reason for rollback ***
Breaks tests on latest, as proto_lang_toolchain didn't make it into the 0.4.0 release
see http://ci.bazel.io/job/bazel-tests/306/BAZEL_VERSION=latest,PLATFORM_NAME=linux-x86_64/console
*** Original change description ***
Use proto_lang_toolchain() in java_proto_library.
--
MOS_MIGRATED_REVID=138432193
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks tests on latest, as proto_lang_toolchain didn't make it into the 0.4.0 release
see http://ci.bazel.io/job/bazel-tests/306/BAZEL_VERSION=latest,PLATFORM_NAME=linux-x86_64/console
*** Original change description ***
Use proto_lang_toolchain() in java_proto_library.
--
MOS_MIGRATED_REVID=138372522
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138161512
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Windows protoc compiler fixed: https://github.com/bazelbuild/bazel/issues/1856
*** Original change description ***
Automated [] rollback of commit a12aae73ee292fdcb170f4eaeb8939283d05383c.
*** Reason for rollback ***
Breaks Bazel Windows Bootstrap
Fix https://github.com/bazelbuild/bazel/issues/1851
*** Original change description ***
Updates protobuf in bazel to version 3.0.0.
--
MOS_MIGRATED_REVID=134699683
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks Bazel Windows Bootstrap
Fix https://github.com/bazelbuild/bazel/issues/1851
*** Original change description ***
Updates protobuf in bazel to version 3.0.0.
--
MOS_MIGRATED_REVID=134510744
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=134464786
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=129865689
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
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
|