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.
2295 Commits
201 Branches
346 Tags
254 MiB
 
 
 
 
 
 
Tag: Branch: Tree: 68b8469245
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '68b8469245'
${ noResults }
protobuf/cmake
Joshua Haberman 911a25e738
Passes nearly all tests! 		3 years ago
..
google/protobuf Passes nearly all tests! 3 years ago
BUILD Fixed the CMake build and amalgamation. 3 years ago
CMakeLists.txt Fixed CMakeLists.txt. 3 years ago
README.md Split monolithic BUILD file into many build files. 4 years ago
build_defs.bzl Added a Valgrind test that works for Python! 3 years ago
make_cmakelists.py Call protobuf_deps() ourselves instead of from upb_deps(). 3 years ago
staleness_test.py Update all 2011 dates to 2021. 4 years ago
staleness_test_lib.py Update all 2011 dates to 2021. 4 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.