protobuf

Commit Graph

Author	SHA1	Message	Date
Protobuf Team Bot	e2c4d0f27e	Automated Code Change PiperOrigin-RevId: 650549584	8 months ago
Joshua Haberman	bcde8d4b54	Generate one source file per message/enum/extension on Android/iOS. The functionality is enabled when the proto_one_output_per_message option used by C++ Lite is enabled. This mirrors the behavior of C++ lite protos. PiperOrigin-RevId: 642327960	9 months ago
Protobuf Team Bot	3dd89a457e	Automated rollback of commit `638ee8f654`. PiperOrigin-RevId: 640749918	10 months ago
Joshua Haberman	638ee8f654	Generate one source file per message/enum/extension on Android/iOS. The functionality is enabled when the `proto_one_output_per_message` option used by C++ Lite is enabled. This mirrors the behavior of C++ lite protos. PiperOrigin-RevId: 640592937	10 months ago
Protobuf Team Bot	21d75f861c	Remove references to rules_proto They are not needed after the rules are move into protobuf repo. Except for the reference to toolchain type, which is currently in rules_proto and can be moved after the implementation is moved into protobuf repo. PiperOrigin-RevId: 622176865	12 months ago
Protobuf Team Bot	d7f032ad15	Move private definitions out of //bazel This is needed to make protobuf/bazel package minimal for other proto rules. Keep 4 public bzl files in upb/bazel. They end up under protobuf/bazel, and they are legitimately used by other repositories. Move upb_proto_library_internal/* under bazel/private. Those are utilities used in the rules. Moving them one level deeper makes protobuf/bazel package clean for other rules. Move build_defs.bzl and amalgamation under /upb/bazel. Those are utilities used in the build. Move lua.BUILD and python* uner /python/dist. Those are used in the WORKSPACE dependency setup. PiperOrigin-RevId: 621442236	12 months ago
Protobuf Team Bot	83ec410d30	Internal change PiperOrigin-RevId: 619377672	12 months ago
Joshua Haberman	2c7193b810	Migrated upb rules to use proto_common. PiperOrigin-RevId: 568943311	2 years ago
Adam Cozzette	501ececd39	Reorganize upb file structure This change moves almost everything in the `upb/` directory up one level, so that for example `upb/upb/generated_code_support.h` becomes just `upb/generated_code_support.h`. The only exceptions I made to this were that I left `upb/cmake` and `upb/BUILD` where they are, mostly because that avoids conflict with other files and the current locations seem reasonable for now. The `python/` directory is a little bit of a challenge because we had to merge the existing directory there with `upb/python/`. I made `upb/python/BUILD` into the BUILD file for the merged directory, and it effectively loads the contents of the other BUILD file via `python/build_targets.bzl`, but I plan to clean this up soon. PiperOrigin-RevId: 568651768	2 years ago
Sandy Zhang	81068e8e8c	Internal change PiperOrigin-RevId: 566426899	2 years ago
Joshua Haberman	0fbe525095	#include foo.upb_minitable.h instead of having foo.upb.h forward-declare MiniTables. PiperOrigin-RevId: 565767975	2 years ago
Joshua Haberman	0a4c8cbd8d	Optimized google3 build by not including the empty .upb.c file. Unfortunately in OSS with Bazel it appears that we must include this empty file, otherwise we get compile errors. More info in: b/300637173 PiperOrigin-RevId: 565699708	2 years ago
Joshua Haberman	2b87999fc1	Added new, split upb rules for MiniTables and the C API. The new rules are: - `upb_minitable_proto_library()`: contains the MiniTables only - `upb_c_proto_library()`: Contains the C API. Depends on the MiniTables This involved splitting upb code generation into two separate aspects, one for MiniTables and one for the C API. PiperOrigin-RevId: 565518070	2 years ago
Joshua Haberman	6c121f5b14	Refactored `upb_proto*_library()` rules to make future splitting of rules easier. This is in preparation for splitting MiniTables out of `upb_c_proto_library()`. PiperOrigin-RevId: 565059826	2 years ago

6 Commits (910f62779fa86a3a1f653d0d34bb7d24e42f64be)