Update the brew workflow

- Remove the `brew install`; the kokoro image already has it, just
  update/upgrade instead.
- Remove `prune`, logs had:
    """
    Error: Unknown command: prune
    """
- Remove `uninstall`, logs had:
    """
    Error: Refusing to uninstall /usr/local/Cellar/cmake/3.16.4 and /usr/local/Cellar/icu4c/64.2
    because they are required by ceres-solver, ffmpeg, harfbuzz, libass and opencv, which are currently installed.
    You can override this and force removal with:
      brew uninstall --ignore-dependencies node icu4c cmake wget
    """
- Skip installing some things since they are already in the base image, logs
  had:
    """
    Warning: gflags 2.2.2 is already installed and up-to-date
    To reinstall 2.2.2, run `brew reinstall gflags`
    Warning: [email protected] 1.1.1g is already installed and up-to-date
    To reinstall 1.1.1g, run `brew reinstall [email protected]`
    Warning: pcre 8.44 is already installed and up-to-date
    To reinstall 8.44, run `brew reinstall pcre`
    """
- Don't install gpg gpg2 as gnupg is already installed, also use gpg instead of
  gpg2 for commands (and update the commands), logs had:
    """
    kokoro/macos/prepare_build_macos_rc: line 44: gpg2: command not found
    kokoro/macos/prepare_build_macos_rc: line 45: gpg2: command not found
    """
- Add env guards to control all the option installs and only request them be
  installed in the cases that need it.  This avoids having to install/update
  the things like ruby when some other tool only needed in some configs is
  install differently and could have conflicts.
- Switch to brew for cocoapods to avoid compat issues on the supporting
  libraries.
10 files changed
tree: a88baae2fac19a1e87d5ed4e491ad1741b5b5917
  1. .github/
  2. benchmarks/
  3. cmake/
  4. conformance/
  5. csharp/
  6. docs/
  7. editors/
  8. examples/
  9. java/
  10. js/
  11. kokoro/
  12. m4/
  13. objectivec/
  14. php/
  15. protoc-artifacts/
  16. python/
  17. ruby/
  18. src/
  19. third_party/
  20. util/
  21. .bazelignore
  22. .gitignore
  23. .gitmodules
  24. .readthedocs.yml
  25. appveyor.bat
  26. appveyor.yml
  27. autogen.sh
  28. BUILD
  29. build_files_updated_unittest.sh
  30. cc_proto_blacklist_test.bzl
  31. CHANGES.txt
  32. compiler_config_setting.bzl
  33. composer.json
  34. configure.ac
  35. CONTRIBUTING.md
  36. CONTRIBUTORS.txt
  37. fix_permissions.sh
  38. generate_changelog.py
  39. generate_descriptor_proto.sh
  40. global.json
  41. LICENSE
  42. Makefile.am
  43. post_process_dist.sh
  44. Protobuf-C++.podspec
  45. protobuf-lite.pc.in
  46. protobuf.bzl
  47. protobuf.pc.in
  48. Protobuf.podspec
  49. protobuf_deps.bzl
  50. README.md
  51. tests.sh
  52. update_compatibility_version.py
  53. update_file_lists.sh
  54. update_version.py
  55. WORKSPACE
README.md

Protocol Buffers - Google's data interchange format

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/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 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:

LanguageSourceUbuntuMacOSWindows
C++ (include C++ runtime and protoc)srcBuild status
Build status
Build status
Build status
Build status
Build status
JavajavaBuild status
Build status
Build status
Build status
PythonpythonBuild status
Build status
Build status
Build status
Build status
Build status
Build status
Build status
Build status
Build status
Build status
Build status
Build status
Build status
Objective-CobjectivecBuild status
Build status
Build status
Build status
C#csharpBuild statusBuild status
Build status
JavaScriptjsBuild statusBuild status
RubyrubyBuild status
Build status
Build status
Build status
Build status
Build status
Build status
Build status
Build status
Build status
Gogolang/protobuf
PHPphpBuild status
Build status
Build status
Build status
Dartdart-lang/protobufBuild Status

Quick Start

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.

Documentation

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

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