Chiebot-Mirror
/
protobuf
mirror of https://github.com/protocolbuffers/protobuf.git
8
0
Fork 0
Code Issues Projects Releases Wiki Activity
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.
18179 Commits
197 Branches
346 Tags
251 MiB
 
 
 
 
 
 
Tag: Branch: Tree: 090edb7a77
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '090edb7a77'
${ noResults }
protobuf/upb/cmake
Protobuf Team Bot c7278372b5
Auto-generate files after cl/658038844 		4 months ago
..
google/protobuf Auto-generate files after cl/658038844 4 months ago
BUILD.bazel Add pkg build rules to create a zip of the protobuf rust crate 4 months ago
CMakeLists.txt Auto-generate files after cl/597923328 11 months ago
README.md Move upb-x/ back to upb/ 1 year ago
build_defs.bzl Added new, split upb rules for MiniTables and the C API. 1 year ago
make_cmakelists.py Move utf8_range into the protobuf repo 1 year ago
push_auto_update.sh Move upb-x/ back to upb/ 1 year ago
staleness_test.py Merge the protobuf and upb Bazel repos 1 year ago
staleness_test_lib.py Move upb-x/ back to upb/ 1 year 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.