| commit | 63f324a9937b2fb562ea551f93d1d38740032bc3 | [log] [tgz] |
|---|---|---|
| author | Joshua Haberman <[email protected]> | Wed Aug 14 22:41:37 2019 +0100 |
| committer | Paul Yang <[email protected]> | Wed Aug 14 14:41:37 2019 -0700 |
| tree | 0b112397d5149ac5b1e47b825e298bc4b9f08dac | |
| parent | 402c28a321fce010ad0b9f99010a78890cae7f34 [diff] |
Roll forward Ruby upb changes now that protobuf Ruby build is fixed (#5866) * Rolled forward again with "Updated upb from defcleanup branch..." Revert "Revert "Updated upb from defcleanup branch and modified Ruby to use it (#5539)" (#5848)" This reverts commit 1568deab40db055a79fa415d21547eaffbd56d57. * A few more merge fixes. * Updated for defcleanup2 branch. * Fixed upb to define upb_decode(). * Fixed names of nested messages. * Revert submodule. * Set -std=gnu90 and fixed warnings/errors. Some of our Kokoro tests seem to run with this level of warnings, and the source strives to be gnu90 compatible. Enforcing it for every build removes the possibility of some errors showing up in Kokoro/Travis tests only. * Fixed remaining warnings with gnu90 mode. I tried to match warning flags with what Ruby appears to do in our Kokoro tests. * Initialize values registered by rb_gc_register_address(). * Fixed subtle GC bug. We need to initialize this marked value before creating the instance. * Truly fix the GC bug. * Updated upb for mktime() fix. * Removed XOPEN_SOURCE as we are not using strptime(). * Removed fixed tests from the conformance failure list for Ruby. * Fixed memory error related to oneof def names. * Picked up new upb changes re: JSON printing. * Uncomment concurrent decoding test.
Copyright 2008 Google Inc.
https://developers.google.com/protocol-buffers/
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.
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/protocolbuffers/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:
https://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 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 | Ubuntu | MacOS | Windows |
|---|---|---|---|---|
| C++ (include C++ runtime and protoc) | src |    |   | |
| Java | java |     | ||
| Python | python |               |    |  |
| Objective-C | objectivec |     | ||
| C# | csharp |  |  | |
| JavaScript | js |  |  | |
| Ruby | ruby |      |      | |
| Go | golang/protobuf | |||
| PHP | php |   |   | |
| Dart | dart-lang/protobuf |  |
The best way to learn how to use protobuf is to follow the tutorials in our developer guide:
https://developers.google.com/protocol-buffers/docs/tutorials
If you want to learn from code examples, take a look at the examples in the examples directory.
The complete documentation for Protocol Buffers is available via the web at: