commit | dbc5c0eba9820ccbcd62b9b6e50803561fbde811 | [log] [tgz] |
---|---|---|
author | Mitch Rudominer <rudominer@chromium.org> | Sat Jun 03 00:06:43 2017 -0700 |
committer | Mitch Rudominer <rudominer@chromium.org> | Fri Jun 09 17:05:09 2017 -0700 |
tree | 874f5ba577ce1652a4d15c4a66ad51c8b7d48b05 | |
parent | d6470abef1ca76c40e6da3b4445b7c32f1d0e2e3 [diff] |
Adds BUILD.gn file for protobufs. This is a first cut of the BUILD.gn file. So far I have protoc compiling successfully. I have not yet tried to use protoc and so this may change in a later CL. I haven't yet created a target that uses a compiled_action() to trigger the build of protoc. For now I have created a target called "protoc_host_build" that invokes the "protoc" target and specifies the host toolchain. We may chose to remove this later. I found I needed to edit a C++ file that is used during the build. The file embed.cc generates a C++ file called "well_known_types_embed.cc" that is used by protoc when generating .js files. But embed.cc writes its generated output to std::cout and the bazel file redirects std out to "well_known_types_embed.cc". Wheras the Bazel file used a "genrule" I used a "compiled_action". But compiled_action doesn't offer a way to redirect the std out from the process being invoked so instead I changed the process to take a flag specifying the output. Change-Id: I21b07564ac1bbdaa4286e787debd003cc9f53917
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/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 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 | php |
Dart | dart-lang/protobuf |
The complete documentation for Protocol Buffers is available via the web at: