Make the protobuf directory match closer to upstream

Remove the outputs of the configure script that are not upstream,
they don't need to be checked in.

Restore .travis.yml, it doesn't hurt to have it and removing it
causes conflicts.

Remove gtest directory, it's not part of the protobuf git repository
and we aren't using it.

Remove the util directory, it's not part of the protobuf git repository
and we aren't using it.

Relands I1d718e9d5fa4fa4bf83419f2bf82f501b29af99e restoring build.gradle
to fix unbundled gradle builds.

Bug: 117607748
Test: m checkbuild
Change-Id: I686e6ab844c96f019f91ea618db124f38b412875
207 files changed
tree: c6efd4099d63806180b2310de5c9ea81c2f1e26e
  1. .gitignore
  2. .travis.yml
  3. Android.bp
  4. Android.mk
  5. BUILD
  6. CHANGES.txt
  7. CONTRIBUTORS.txt
  8. CleanSpec.mk
  9. LICENSE
  10. MODULE_LICENSE_APACHE2
  11. Makefile.am
  12. NOTICE
  13. Protobuf.podspec
  14. README.android
  15. README.md
  16. README.version
  17. WORKSPACE
  18. android/
  19. appveyor.bat
  20. appveyor.yml
  21. autogen.sh
  22. benchmarks/
  23. build.gradle
  24. cmake/
  25. config/
  26. configure.ac
  27. conformance/
  28. csharp/
  29. docs/
  30. editors/
  31. examples/
  32. generate_descriptor_proto.sh
  33. gmock.BUILD
  34. java/
  35. javamicro/
  36. javanano/
  37. jenkins/
  38. js/
  39. m4/
  40. more_tests/
  41. objectivec/
  42. php/
  43. post_process_dist.sh
  44. protobuf-lite.pc.in
  45. protobuf.bzl
  46. protobuf.pc.in
  47. protoc-artifacts/
  48. python/
  49. ruby/
  50. six.BUILD
  51. src/
  52. tests.sh
  53. update_file_lists.sh
  54. util/
README.md

Protocol Buffers - Google's data interchange format

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
PHPTBD

Usage

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

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