protobuf/util/python/BUILD.bazel

load("@rules_cc//cc:defs.bzl", "cc_library")

exports_files(["BUILD.bazel"])

# This is a placeholder for python headers. Projects needing to use
# fast cpp protos in protobuf's python interface should build with
# --define=use_fast_cpp_protos=true, and in addition, provide
# //external:python_headers dependency that in turn provides Python.h.
#
# Projects that include protobuf using a Bazel external repository will need to
# add a workspace rule to their WORKSPACE files to add an external workspace
# that includes the Python headers. For example, the protobuf WORKSPACE file
# includes the following local_repository rule that points to this directory:
#
# new_local_repository(
#   name = "python_headers",
#   path = __workspace_dir__ + "/util/python",
# )
cc_library(
    name = "python_headers",
    visibility = ["//visibility:public"],
)
[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			`load("@rules_cc//cc:defs.bzl", "cc_library")`

Rename all BUILD files to BUILD.bazel (#9892) This avoids conflicting names in a couple of cases. 1. Within google, we want to sync files but not name them BUILD (since the structure doesn't match). 2. On case-insensitive filesystems, `build` may be used for a build directory. Naming `BUILD.bazel` avoids potentioal conflicts. 2022-04-30 00:57:55 +00:00			`exports_files(["BUILD.bazel"])`
Add source distribution packaging rules (#9835) This change adds `rules_pkg`-based targets that will produce source distribution archives, similar to `make dist`. These rules produce nearly the same outputs as `make dist`. However, there are some differences and caveats: 1. The outputs do not contain vendored googletest sources. 2. You have to run `autogen.sh` before `blaze build pkg:all`. This produces several autotools-related files directly into the source tree. 3. The output .zip files do not have a directory prefix like `protobuf-3.20.1-rc-1` (this will be addressed after [Substitute package variables in `pkg_zip#package_dir`. bazelbuild/rules_pkg#577](https://github.com/bazelbuild/rules_pkg/pull/577); the tar files do have this prefix, though.) 4. One file is missing from the archives, which is produced during the `make` build: benchmarks/gogo/cpp_no_group/cpp_benchmark.cc 5. In several places, I have explicitly excluded some files that are not in the autotools distribution outputs. I think most of those files should probably be included, but for now, I'm aiming for parity with `make dist`. These are marked with comments, so it should be easy to clean them up later. 2022-04-22 23:58:16 +00:00
Added util/python/BUILD to provide //util/python:python_headers dependency for building use_fast_cpp_protos 2015-12-08 17:51:14 +00:00			`# This is a placeholder for python headers. Projects needing to use`
			`# fast cpp protos in protobuf's python interface should build with`
			`# --define=use_fast_cpp_protos=true, and in addition, provide`
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			`# //external:python_headers dependency that in turn provides Python.h.`
			`#`
			`# Projects that include protobuf using a Bazel external repository will need to`
			`# add a workspace rule to their WORKSPACE files to add an external workspace`
			`# that includes the Python headers. For example, the protobuf WORKSPACE file`
			`# includes the following local_repository rule that points to this directory:`
			`#`
			`# new_local_repository(`
Change "python" to "python_headers" in comment (#6046) Following the instructions as is does not work, the new_local_repository rule needs to be called "python_headers" 2019-07-15 23:40:57 +00:00			`# name = "python_headers",`
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			`# path = __workspace_dir__ + "/util/python",`
			`# )`
Added util/python/BUILD to provide //util/python:python_headers dependency for building use_fast_cpp_protos 2015-12-08 17:51:14 +00:00			`cc_library(`
			`name = "python_headers",`
			`visibility = ["//visibility:public"],`
			`)`