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.
16045 Commits
197 Branches
346 Tags
251 MiB
 
 
 
 
 
 
Tag: Branch: Tree: c20b337221
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'c20b337221'
${ noResults }
protobuf/upb/cmake
Protobuf Team Bot 4b301ad764
Auto-generate files after cl/573375994 		1 year ago
..
google/protobuf Auto-generate files after cl/573375994 1 year ago
BUILD.bazel Reorganize upb file structure 1 year ago
CMakeLists.txt Auto-generate files after cl/569594353 1 year ago
README.md
…
build_defs.bzl Added new, split upb rules for MiniTables and the C API. 1 year ago
make_cmakelists.py Added new, split upb rules for MiniTables and the C API. 1 year ago
push_auto_update.sh
…
staleness_test.py Merge the protobuf and upb Bazel repos 1 year ago
staleness_test_lib.py
…

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.