Protocol Buffers - Google's data interchange format (grpc依赖) https://developers.google.com/protocol-buffers/
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Protobuf Team Bot f7e25ebfd1 Auto-generate CMake file lists after PR #1401 1 year ago
..
google/protobuf Auto-generate CMake file lists after PR #1401 1 year ago
BUILD.bazel Split mini_descriptor into its own directory 1 year ago
CMakeLists.txt Auto-generate CMake file lists 1 year ago
README.md Split monolithic BUILD file into many build files. 4 years ago
build_defs.bzl Add a tag so that we can differentiate staleness tests 2 years ago
make_cmakelists.py Split the JSON rules out of the main BUILD file and removed obsolete forwarding headers 1 year ago
push_auto_update.sh No-op change to trigger cmake regen 1 year ago
staleness_test.py Rename generated_file_staleness_test() to just staleness_test() 2 years ago
staleness_test_lib.py Update staleness_test() error message to include diff 2 years ago

README.md

upb CMake build (EXPERIMENTAL)

upb's CMake support is experimental. The core library builds successfully under CMake, and this is verified by the Bazel tests in this directory. However there is no support for building the upb compiler or for generating .upb.c/upb.h files. This means upb's CMake support is incomplete at best, unless your application is intended to be purely reflective.

If you find this CMake setup useful in its current state, please consider filing an issue so we know. If you have suggestions for how it could be more useful (and particularly if you can contribute some code for it) please feel free to file an issue for that too. Do keep in mind that upb does not currently provide any ABI stability, so we want to avoid providing a shared library.

The CMakeLists.txt is generated from the Bazel BUILD files using the Python scripts in this directory. We want to avoid having two separate sources of truth that both need to be updated when a file is added or removed.

This directory also contains some generated files that would be created on the fly during a Bazel build. These are automaticaly kept in sync by the Bazel test //cmake:test_generated_files.