Google Git
Sign in
flutter / third_party / protobuf / 671e075c5e642627ccbd03cf71226d8d5f2ec897
commit671e075c5e642627ccbd03cf71226d8d5f2ec897[log] [tgz]
authorAdam Cozzette <acozzette@google.com>Thu Feb 23 11:32:16 2017 -0800
committerAdam Cozzette <acozzette@google.com>Wed Mar 01 07:43:11 2017 -0800
tree1ed30b82de5a9e5dcb3d852b47d5f6d75486a261
parent7339fc04c49a055ec0688cd0cb24cf7ea64f7783 [diff]
Use closurebuilder.py in favor of calcdeps.py for compiling JavaScript

There are two motivations for this:
1) calcdeps.py is deprecated and replaced by closurebuilder.py.
2) As part of this I was able to tweak things so that the Closure
compiler does not attempt to examine every .js file in the tree under
js/. This makes it possible to put compatibility tests and related files
in a subdirectory without them getting mixed up with the main .js files
we care about.
4 files changed
tree: 1ed30b82de5a9e5dcb3d852b47d5f6d75486a261
  1. benchmarks/
  2. cmake/
  3. conformance/
  4. csharp/
  5. docs/
  6. editors/
  7. examples/
  8. java/
  9. javanano/
  10. jenkins/
  11. js/
  12. m4/
  13. more_tests/
  14. objectivec/
  15. php/
  16. protoc-artifacts/
  17. python/
  18. ruby/
  19. src/
  20. third_party/
  21. util/
  22. .gitignore
  23. .gitmodules
  24. .travis.yml
  25. appveyor.bat
  26. appveyor.yml
  27. autogen.sh
  28. BUILD
  29. CHANGES.txt
  30. composer.json
  31. configure.ac
  32. CONTRIBUTORS.txt
  33. generate_changelog.py
  34. generate_descriptor_proto.sh
  35. gmock.BUILD
  36. LICENSE
  37. Makefile.am
  38. post_process_dist.sh
  39. protobuf-lite.pc.in
  40. protobuf.bzl
  41. protobuf.pc.in
  42. Protobuf.podspec
  43. README.md
  44. six.BUILD
  45. tests.sh
  46. update_file_lists.sh
  47. WORKSPACE
README.md

Protocol Buffers - Google's data interchange format

Build Status Build status Build Status Build Status Build Status

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:

LanguageSource
C++ (include C++ runtime and protoc)src
Javajava
Pythonpython
Objective-Cobjectivec
C#csharp
JavaNanojavanano
JavaScriptjs
Rubyruby
Gogolang/protobuf
PHPphp

Usage

The complete documentation for Protocol Buffers is available via the web at:

https://developers.google.com/protocol-buffers/