be0d7f6664
As bazel folks are looking at getting auto generation of module maps going and the importing of sources files causes issues there. We were only do it to hack around some of the apple linker behaviors around objc classes and categories, but even that isn't complete and CocoaPods was already doing -ObjC, and developers not using pods could have still needed it to ensure everything was linked anyways; so drop the hack of importing sources. |
||
|---|---|---|
| benchmarks | ||
| cmake | ||
| conformance | ||
| csharp | ||
| docs | ||
| editors | ||
| examples | ||
| java | ||
| javanano | ||
| jenkins | ||
| js | ||
| m4 | ||
| more_tests | ||
| objectivec | ||
| php | ||
| protoc-artifacts | ||
| python | ||
| ruby | ||
| src | ||
| util/python | ||
| .gitignore | ||
| .travis.yml | ||
| appveyor.bat | ||
| appveyor.yml | ||
| autogen.sh | ||
| BUILD | ||
| CHANGES.txt | ||
| configure.ac | ||
| CONTRIBUTORS.txt | ||
| generate_descriptor_proto.sh | ||
| gmock.BUILD | ||
| LICENSE | ||
| Makefile.am | ||
| post_process_dist.sh | ||
| protobuf-lite.pc.in | ||
| protobuf.bzl | ||
| protobuf.pc.in | ||
| Protobuf.podspec | ||
| README.md | ||
| six.BUILD | ||
| tests.sh | ||
| update_file_lists.sh | ||
| WORKSPACE | ||
Protocol Buffers - Google's data interchange format
Copyright 2008 Google Inc.
https://developers.google.com/protocol-buffers/
Overview
Protocol Buffers (a.k.a., protobuf) are Google's language-neutral, platform-neutral, extensible mechanism for serializing structured data. You can find protobuf's documentation on the Google Developers site.
This README file contains protobuf installation instructions. To install protobuf, you need to install the protocol compiler (used to compile .proto files) and the protobuf runtime for your chosen programming language.
Protocol Compiler Installation
The protocol compiler is written in C++. If you are using C++, please follow the C++ Installation Instructions to install protoc along with the C++ runtime.
For non-C++ users, the simplest way to install the protocol compiler is to download a pre-built binary from our release page:
https://github.com/google/protobuf/releases
In the downloads section of each release, you can find pre-built binaries in zip packages: protoc-$VERSION-$PLATFORM.zip. It contains the protoc binary as well as a set of standard .proto files distributed along with protobuf.
If you are looking for an old version that is not available in the release page, check out the maven repo here:
http://repo1.maven.org/maven2/com/google/protobuf/protoc/
These pre-built binaries are only provided for released versions. If you want to use the github master version at HEAD, or you need to modify protobuf code, or you are using C++, it's recommended to build your own protoc binary from source.
If you would like to build protoc binary from source, see the C++ Installation Instructions.
Protobuf Runtime Installation
Protobuf supports several different programming languages. For each programming language, you can find instructions in the corresponding source directory about how to install protobuf runtime for that specific language:
| Language | Source |
|---|---|
| C++ (include C++ runtime and protoc) | src |
| Java | java |
| Python | python |
| Objective-C | objectivec |
| C# | csharp |
| JavaNano | javanano |
| JavaScript | js |
| Ruby | ruby |
| Go | golang/protobuf |
| PHP | TBD |
Usage
The complete documentation for Protocol Buffers is available via the web at:
https://developers.google.com/protocol-buffers/