| 1 |
This directory contains generated Go wrappers for Bazel cquery result |
| 2 |
protocol buffers defined in https://github.com/bazelbuild/bazel/tree/master/src/main/protobuf. |
| 3 |
|
| 4 |
An attempt was made to use [go_proto_library](https://github.com/bazelbuild/rules_go/blob/master/proto/core.rst#go-proto-library) |
| 5 |
to generate this code at build time, sourcing the embedded_tools dependency, but that |
| 6 |
was never successful. The cause appears to be that the protobufs in Bazel's source |
| 7 |
defined messages of the same name (specifically "Target") which creates a build |
| 8 |
conflict. The command below generates the two Go classes with different package names |
| 9 |
to avoid this conflict - which is what the Bazel generated Java wrapper does. |
| 10 |
|
| 11 |
They were generated as so: |
| 12 |
|
| 13 |
```bash |
| 14 |
BAZEL_DIR=/path/to/bazel/source |
| 15 |
DST_DIR=${PWD}/bazel/exporter/build_proto |
| 16 |
GO_PACKAGE=go.skia.org/skia/bazel/exporter/build_proto |
| 17 |
GO_GEN_CODE_ROOT=${DST_DIR}/go.skia.org/skia/bazel/exporter/build_proto |
| 18 |
|
| 19 |
protoc \ |
| 20 |
--proto_path=${BAZEL_DIR} \ |
| 21 |
--go_out=${DST_DIR} \ |
| 22 |
--go_opt=Msrc/main/protobuf/build.proto=${GO_PACKAGE}/build \ |
| 23 |
--go_opt=Msrc/main/protobuf/analysis_v2.proto=${GO_PACKAGE}/analysis_v2 \ |
| 24 |
${SRC_DIR}/analysis_v2.proto ${SRC_DIR}/build.proto |
| 25 |
``` |
| 26 |
|
| 27 |
The call above writes the generated code to `${DST_DIR}/go.skia.org/skia/bazel/exporter/build_proto` |
| 28 |
which is then moved into `${DST_DIR}/build` and `${DST_DIR}/build`. |