Chiebot-Mirror/protobuf - protobuf - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
Marcel Hlopko	5814f6c977	Generate C++ thunks for Rust protos In this CL I'd like to call existing C++ Protobuf API from the V0 Rust API. Since parts of the C++ API are defined inline and using (obviously) C++ name mangling, we need to create a "thunks.cc" file that: 1) Generates code for C++ API function we use from Rust 2) Exposes these functions without any name mangling (meaning using `extern "C"`) In this CL we add Bazel logic to generate "thunks" file, compile it, and propagate its object to linking. We also add logic to protoc to generate this "thunks" file. The protoc logic is rather rudimentary still. I hope to focus on protoc code quality in my followup work on V0 Rust API using C++ kernel. PiperOrigin-RevId: 523479839	2 years ago
Marcel Hlopko	d9a8622fac	Enable bzl visibility for Protobuf Rust rules PiperOrigin-RevId: 520319698	2 years ago
Jakob Buchgraber	dbf97258bd	Enable support for rust_upb_proto_library and rust_cc_proto_library within the same build PiperOrigin-RevId: 520314976	2 years ago
Jakob Buchgraber	7802b93442	Fix build errors in Protobuf Rust PiperOrigin-RevId: 518619271	2 years ago
Marcel Hlopko	aaa338b285	Configure build for the C++ backend PiperOrigin-RevId: 517429571	2 years ago
Marcel Hlopko	ab9f1ab58a	Configure the build for the Rust UPB backend In this CL we're adding the barebones infrastructure to generate Rust proto messages using UPB as a backend. The API is what we call a V0, not yet production-quality, not yet rigorously designed, just something to enable parallel work. The interesting part of switching backend between UPB and C++ will come in a followup. PiperOrigin-RevId: 517089760	2 years ago
Marcel Hlopko	26af540a7a	Add support for proto dependencies to rust_proto_library PiperOrigin-RevId: 514719215	2 years ago
Marcel Hlopko	3dc546daff	Implement a minimal, internal, experimental rust_proto_library rule. The internal design is consistent with other <lang>_proto_library rules. rust_proto_library attaches rust_proto_library_aspect on its `deps` attribute. The aspect traverses the dependency, and when it visits proto_library (detected by ProtoInfo provider) it registers 2 actions: 1) to run protoc with Rust backend to emit gencode 2) to compile the gencode using Rustc Action (2) gets the Rust proto runtime as an input as well. Coming in a followup is support and test coverage for proto_library.deps. PiperOrigin-RevId: 514521285	2 years ago