Google Git
Sign in
pigweed / third_party / github / protocolbuffers / protobuf / 297449aaf4b3fabb29a75ba3912af12e27fdefd9
commit297449aaf4b3fabb29a75ba3912af12e27fdefd9[log] [tgz]
authorThomas Van Lenten <thomasvl@google.com>Mon Oct 03 11:20:54 2016 -0400
committerThomas Van Lenten <thomasvl@google.com>Mon Oct 03 13:24:24 2016 -0400
treea657e8036dc9f18f288f3e5bc4fcbbe8e789c477
parent350d49449bcabb491f1fb05e3ac2a91717c9ef04 [diff]
Update the ObjC projects for Xcode 8

- Let Xcode 8 update settings on the projects/schemes.
- Migrate Swift tests to Swift 3 syntax.
- Update the build/test script:
  - Require Xcode 8 (because of the Swift 3 requirement for tests)
  - Update the devices to what Xcode 8 has (8.x simulator seem to fail even
    though they can be downloaded in Xcode 8)
- Update the travis images to ones with Xcode 8.
9 files changed
tree: a657e8036dc9f18f288f3e5bc4fcbbe8e789c477
  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. phpunit.xml
  39. post_process_dist.sh
  40. protobuf-lite.pc.in
  41. protobuf.bzl
  42. protobuf.pc.in
  43. Protobuf.podspec
  44. README.md
  45. six.BUILD
  46. tests.sh
  47. update_file_lists.sh
  48. WORKSPACE
README.md

Protocol Buffers - Google's data interchange format

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/