AuroraMiddleware/protobuf
1
0
Fork 0
Code Issues 1 Pull Requests Projects Releases Wiki Activity
e56d6936f3
protobuf/WORKSPACE

69 lines
2.0 KiB
Python
Raw Normal View History

bazel: Add proto_library rules for well known types. Fixes #2763 Adds a proto_library rule for each well known type proto: $ bazel query "filter(\".*_proto$\", \"...\")" //:wrappers_proto //:timestamp_proto //:struct_proto //:field_mask_proto //:empty_proto //:duration_proto //:compiler_plugin_proto //:descriptor_proto //:api_proto //:type_proto //:source_context_proto //:any_proto Bazel users can reference these proto_library rules for their own language specific rules i.e. java_proto_library( name = "any_java_proto", deps = ["@com_google_protobuf//:any_proto"], ) Also set the workspace name to "com_google_protobuf", as proto_library rules reference protobuf that way.
2017-09-05 15:15:10 +00:00
workspace(name = "com_google_protobuf")
Add Bazel config for zlib support (#5389) * Add Bazel config for optional zlib support * Add hard dependency on zlib * Remove unused config_setting
2018-12-11 19:58:26 +00:00
[bazel] Update gtest and deprecate //external:{gtest,gtest_main} (#7237) This change updates the gtest-version used by Bazel. Also, `//external:{gtest,gtest_main}` is deprecated so we can remove some of the uses of the discouraged `bind` function. RELNOTES[bazel]: Starting with Protobuf 3.13.0, building and running Protobuf tests requires `@com_google_googletest//:{gtest,gtest_main}` instead of `//external:{gtest,gtest_main}`. Use `--@com_google_protobuf//:incompatible_use_com_google_googletest=true` to verify your workspace is not affected by this change.
2020-03-02 23:15:22 +00:00
load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
[bazel] Add fixes for --incompatible_load_{cc,java,proto}_rules_from_bzl (Part 2) This change adds the required loads to examples and zlib. For full compatibility with --incompatible_load_{cc,java,proto}_rules_from_bzl, we will need to roll gtest to a newer version.
2019-07-26 11:14:19 +00:00
local_repository(
name = "com_google_protobuf_examples",
path = "examples",
)
[bazel] Update gtest and deprecate //external:{gtest,gtest_main} (#7237) This change updates the gtest-version used by Bazel. Also, `//external:{gtest,gtest_main}` is deprecated so we can remove some of the uses of the discouraged `bind` function. RELNOTES[bazel]: Starting with Protobuf 3.13.0, building and running Protobuf tests requires `@com_google_googletest//:{gtest,gtest_main}` instead of `//external:{gtest,gtest_main}`. Use `--@com_google_protobuf//:incompatible_use_com_google_googletest=true` to verify your workspace is not affected by this change.
2020-03-02 23:15:22 +00:00
http_archive(
name = "com_google_googletest",
sha256 = "9dc9157a9a1551ec7a7e43daea9a694a0bb5fb8bec81235d8a1e6ef64c716dcb",
strip_prefix = "googletest-release-1.10.0",
urls = [
"https://mirror.bazel.build/github.com/google/googletest/archive/release-1.10.0.tar.gz",
"https://github.com/google/googletest/archive/release-1.10.0.tar.gz",
],
[bazel] Load python rules from @rules_python
2019-08-06 19:12:06 +00:00
)
Restrict visibility and add target for C++ benchmark
2021-03-14 09:58:03 +00:00
http_archive(
name = "com_github_google_benchmark",
sha256 = "2a778d821997df7d8646c9c59b8edb9a573a6e04c534c01892a40aa524a7b68c",
strip_prefix = "benchmark-bf585a2789e30585b4e3ce6baf11ef2750b54677",
urls = [
"https://github.com/google/benchmark/archive/bf585a2789e30585b4e3ce6baf11ef2750b54677.zip",
],
)
create importable function for defining zlib
2019-02-26 18:07:55 +00:00
# Load common dependencies.
Align dependency handling with Bazel best practices (#9165) This commit removes the use of bind() since that function goes against Bazel best practices: https://docs.bazel.build/versions/main/external.html#repository-rules-1 The bind() function basically maps a dependency into //external, but there is no good reason to do this. By mapping dependencies into //external and relying on this in our own BUILD files, we're forcing projects that depend on us to do the same. The one bind() call that I did leave in place was //:python_headers. This one seems to be doing something complicated I don't fully understand, and I don't want to risk breaking it. This change also moves our list of required Maven artifacts into a constant in protobuf_deps.bzl. This way, projects that depend on us can refer to this list when they invoke maven_install() and automatically pull in all the necesary dependencies. This fixes #9132.
2021-10-28 17:34:54 +00:00
load("//:protobuf_deps.bzl", "PROTOBUF_MAVEN_ARTIFACTS", "protobuf_deps")
create importable function for defining zlib
2019-02-26 18:07:55 +00:00
protobuf_deps()
bazel: Add proto_library rules for well known types. Fixes #2763 Adds a proto_library rule for each well known type proto: $ bazel query "filter(\".*_proto$\", \"...\")" //:wrappers_proto //:timestamp_proto //:struct_proto //:field_mask_proto //:empty_proto //:duration_proto //:compiler_plugin_proto //:descriptor_proto //:api_proto //:type_proto //:source_context_proto //:any_proto Bazel users can reference these proto_library rules for their own language specific rules i.e. java_proto_library( name = "any_java_proto", deps = ["@com_google_protobuf//:any_proto"], ) Also set the workspace name to "com_google_protobuf", as proto_library rules reference protobuf that way.
2017-09-05 15:15:10 +00:00
Enable tests for bazel build. Change-Id: I63ed5fb58a45e098f2fd1fa457a219148de030bd
2015-06-18 23:45:27 +00:00
bind(
Remove hack for building Python support with Bazel. This change makes use of new imports attribute for Bazel's Python rules, which enable adding directories to the PYTHONPATH. This allows us to remove the hack for building protobuf's Python support with Bazel and now allows projects to include protobuf using a Bazel external repository rather than requiring it to be imported directly into the source tree as //google/protobuf. This change also updates the protobuf BUILD file to use a named repository, @python//, for including Python headers rather than //util/python. This allows projects to specify their own package for Python headers when including protobuf with an external repository. Fixes #1230
2016-02-12 02:11:10 +00:00
name = "python_headers",
actual = "//util/python:python_headers",
Enable tests for bazel build. Change-Id: I63ed5fb58a45e098f2fd1fa457a219148de030bd
2015-06-18 23:45:27 +00:00
)
Bazel powered Java testing (#8506) * Protobuf Java/Core Tests running w/ Bazel. Also integrates rules_jvm_external and migrates existing maven deps in place. * Add test_suite target that maps to rule name. * Lite tests passing in Bazel * util tests passing with Bazel. * Add conformance and build testing to //java:core * Cleanup bzl style and lock down access to failure lists. * Adding Java Lite conformance tests. * rm newline * parameterize conformance_test This makes usage of failure lists more explicit. * restrict visibility more for newly added libs and fix formatting. * fix formatting and visibility. * move testing.bzl to an internal package. * fix file formatting. * moving conformance_test to internal.bzl
2021-04-20 18:36:32 +00:00
load("@rules_jvm_external//:defs.bzl", "maven_install")
Add jsr305 dependency for Bazel
2021-10-12 22:37:40 +00:00
Align dependency handling with Bazel best practices (#9165) This commit removes the use of bind() since that function goes against Bazel best practices: https://docs.bazel.build/versions/main/external.html#repository-rules-1 The bind() function basically maps a dependency into //external, but there is no good reason to do this. By mapping dependencies into //external and relying on this in our own BUILD files, we're forcing projects that depend on us to do the same. The one bind() call that I did leave in place was //:python_headers. This one seems to be doing something complicated I don't fully understand, and I don't want to risk breaking it. This change also moves our list of required Maven artifacts into a constant in protobuf_deps.bzl. This way, projects that depend on us can refer to this list when they invoke maven_install() and automatically pull in all the necesary dependencies. This fixes #9132.
2021-10-28 17:34:54 +00:00
maven_install(
artifacts = PROTOBUF_MAVEN_ARTIFACTS,
# For updating instructions, see:
# https://github.com/bazelbuild/rules_jvm_external#updating-maven_installjson
maven_install_json = "//:maven_install.json",
Bazel powered Java testing (#8506) * Protobuf Java/Core Tests running w/ Bazel. Also integrates rules_jvm_external and migrates existing maven deps in place. * Add test_suite target that maps to rule name. * Lite tests passing in Bazel * util tests passing with Bazel. * Add conformance and build testing to //java:core * Cleanup bzl style and lock down access to failure lists. * Adding Java Lite conformance tests. * rm newline * parameterize conformance_test This makes usage of failure lists more explicit. * restrict visibility more for newly added libs and fix formatting. * fix formatting and visibility. * move testing.bzl to an internal package. * fix file formatting. * moving conformance_test to internal.bzl
2021-04-20 18:36:32 +00:00
repositories = [
Migrate from maven_jar to jvm_maven_import_external to prepare for Bazel 2.0
2019-12-02 17:35:00 +00:00
"https://repo1.maven.org/maven2",
rely on only HTTPS mirrors for maven. (#8526)
2021-04-22 19:12:41 +00:00
"https://repo.maven.apache.org/maven2",
Migrate from maven_jar to jvm_maven_import_external to prepare for Bazel 2.0
2019-12-02 17:35:00 +00:00
],
add java/util support based on java/util/pom.xml
2016-03-11 01:50:25 +00:00
)
ensure maven deps are pinned for reproducibility. (#8523) * ensure maven deps are pinned for reproducibility. * adding update docs.
2021-04-21 23:26:05 +00:00
load("@maven//:defs.bzl", "pinned_maven_install")
Bazel: Add dependency to error_prone_annotations Recently dependency to error_prone_annotations was added to the code, but only Maven build tool chain was updated. Closes #5795.
2019-03-03 20:57:33 +00:00
Align dependency handling with Bazel best practices (#9165) This commit removes the use of bind() since that function goes against Bazel best practices: https://docs.bazel.build/versions/main/external.html#repository-rules-1 The bind() function basically maps a dependency into //external, but there is no good reason to do this. By mapping dependencies into //external and relying on this in our own BUILD files, we're forcing projects that depend on us to do the same. The one bind() call that I did leave in place was //:python_headers. This one seems to be doing something complicated I don't fully understand, and I don't want to risk breaking it. This change also moves our list of required Maven artifacts into a constant in protobuf_deps.bzl. This way, projects that depend on us can refer to this list when they invoke maven_install() and automatically pull in all the necesary dependencies. This fixes #9132.
2021-10-28 17:34:54 +00:00
pinned_maven_install()
[bazel] Fix blacklisted_protos in cc_toolchain and add test (#7075)
2020-01-15 18:27:35 +00:00
updating GSON and Guava to more recent versions (#8524)
2021-04-22 01:05:18 +00:00
# For `cc_proto_blacklist_test` and `build_test`.
[bazel] Fix blacklisted_protos in cc_toolchain and add test (#7075)
2020-01-15 18:27:35 +00:00
load("@bazel_skylib//:workspace.bzl", "bazel_skylib_workspace")
Align dependency handling with Bazel best practices (#9165) This commit removes the use of bind() since that function goes against Bazel best practices: https://docs.bazel.build/versions/main/external.html#repository-rules-1 The bind() function basically maps a dependency into //external, but there is no good reason to do this. By mapping dependencies into //external and relying on this in our own BUILD files, we're forcing projects that depend on us to do the same. The one bind() call that I did leave in place was //:python_headers. This one seems to be doing something complicated I don't fully understand, and I don't want to risk breaking it. This change also moves our list of required Maven artifacts into a constant in protobuf_deps.bzl. This way, projects that depend on us can refer to this list when they invoke maven_install() and automatically pull in all the necesary dependencies. This fixes #9132.
2021-10-28 17:34:54 +00:00
[bazel] Fix blacklisted_protos in cc_toolchain and add test (#7075)
2020-01-15 18:27:35 +00:00
bazel_skylib_workspace()
Creates a protoc release zip (#9188) * Creates a protoc release zip Mimics what we're doing manually today but powered by Bazel. * don't special case this. * Addressing feedback. * adding comment about _cc_toolchain
2021-11-04 22:57:29 +00:00
load("@rules_pkg//:deps.bzl", "rules_pkg_dependencies")
rules_pkg_dependencies()
Adding kotlin bazel tests
2022-01-12 21:54:30 +00:00
# For `kt_jvm_library`
load("@io_bazel_rules_kotlin//kotlin:repositories.bzl", "kotlin_repositories")
kotlin_repositories()
load("@io_bazel_rules_kotlin//kotlin:core.bzl", "kt_register_toolchains")
kt_register_toolchains()
Reference in New Issue Copy Permalink