| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
This is in preparation for placing it in a local repository of its own.
The goal is to make proto_library depend on @com_google_protobuf//:protoc by default instead of //third_party/protobuf:protoc.
This, in turn, will allow easier set-up for proto_library: just download a protobuf distro and point at it from their WORKSPACE.
Change-Id: I1b1ec61a414a765843553c84a179a6768956180a
|
| |
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 141322619
MOS_MIGRATED_REVID=141322619
|
|
|
|
|
|
|
|
|
|
| |
Fixes compilation on FreeBSD
--
Change-Id: Iedaa9e08615b8a52fae6f19c867d419938a08411
Reviewed-on: https://cr.bazel.build/7591
PiperOrigin-RevId: 140838599
MOS_MIGRATED_REVID=140838599
|
|
|
|
|
|
|
|
|
| |
java_xxx_proto_library rules now look for toolchains in the external repo @com_google_protobuf_xxx//:xxx_toolchain
This still requires getting protobuf's GitHub repository to build with Bazel.
--
MOS_MIGRATED_REVID=140420903
|
|
|
|
|
|
| |
...as we build protoc from source now.
Change-Id: Ib9662345cf98af9b90da7422658796ee4937e1ce
|
|
|
|
|
|
|
|
|
|
| |
Use the provided sources to build the protoc binary instead of
using the committed binaries.
--
Change-Id: I3df01e9f400e3cebbd1fe3ce74c6142c93c58b6c
Reviewed-on: https://cr.bazel.build/6732
MOS_MIGRATED_REVID=140192644
|
|
|
|
|
|
|
| |
Fixes #2119 and related bootstrap breakage.
Change-Id: I7ca5b9f509e182780f3486c22bf30da3d4104f15
RELNOTES: None.
|
|
|
|
|
|
|
| |
preparation of removing the older one from //third_party/protobuf.
--
MOS_MIGRATED_REVID=140023015
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** 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
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=137500893
|
|
|
|
|
|
|
|
|
|
|
| |
The "protobuf_python" target references a "protobuf_python_srcs" target in its deps, which does not exist, causing a build error when I tried to run "bazel build //src/main/...":
ERROR: /Users/philwo/src/bazel/third_party/protobuf/3.0.0/BUILD:70:1: in deps attribute of py_library rule //third_party/protobuf/3.0.0:protobuf_python: rule '//third_party/protobuf/3.0.0:protobuf_python_srcs' does not exist. Since this rule was created by the macro 'py_proto_library', the error might have been caused by the macro implementation in /Users/philwo/src/bazel/third_party/protobuf/protobuf.bzl:256:12.
I think the "python_srcs" target should actually be called "protobuf_python_srcs". With that change, the build works.
--
MOS_MIGRATED_REVID=136467485
|
|
|
|
|
|
|
|
|
|
|
| |
We have added support for Linux s390x platform in Bazel.
Closes #1891.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/1891
MOS_MIGRATED_REVID=135777047
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** 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
|
|
|
|
|
|
|
|
|
|
|
| |
This allows us to roll forward
https://github.com/bazelbuild/bazel/commit/a12aae73ee292fdcb170f4eaeb8939283d05383c
which was rolled back by commit
https://github.com/bazelbuild/bazel/commit/0d36f410370ed99cbd57359d7444269faec134f8
Fixes https://github.com/bazelbuild/bazel/issues/1856
RELNOTES: Update protoc-3.0.0-mingw.exe to a working (statically linked) binary
|
|
|
|
|
|
|
|
|
| |
See https://github.com/bazelbuild/bazel/issues/1856
Slightly reformat (prettify) the page too.
--
MOS_MIGRATED_REVID=134649252
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** 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=133842785
|
|
|
|
| |
Change-Id: Ia0d5aebdf5d24da8aadecc51fd8ffdefa063d993
|
|
|
|
|
|
|
|
|
|
|
| |
- Remove mention of non-existent proto compiler
- Add info about updating protobuf.bzl and BUILD files
Fixes https://github.com/bazelbuild/bazel/pull/1769#issuecomment-247966248
Fixes https://github.com/bazelbuild/bazel/issues/1790
--
MOS_MIGRATED_REVID=133572313
|
|
|
|
| |
Change-Id: I59fd0ff2059abb16ccb23403736efe2d955038f4
|
|
|
|
| |
Change-Id: I2119ce7cdce68c2732653fa0152abf0150d17ac0
|
|
|
|
| |
Change-Id: I91f5b85852cabff0da8b1c68bf432596d7dc341d
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=129865689
|
|
|
|
| |
Change-Id: I1505726ca66ab578cf29d2dc6018a2ff1e2ccaaf
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|