tree: 201af0db8e618e58b18125d36a27d71b6b77649e [path history] [tgz]
  1. address_sorting/
  2. android/
  3. cares/
  4. objective_c/
  5. py/
  6. rake-compiler-dock/
  7. toolchains/
  8. upb/
  9. xxhash/
  11. BUILD
  12. constantly.BUILD
  13. cython.BUILD
  14. enum34.BUILD
  15. futures.BUILD
  16. incremental.BUILD
  17. libprotobuf_mutator.BUILD
  18. libuv.BUILD
  19. protobuf.patch
  20. protoc-gen-validate.patch
  22. rules_python.patch
  23. six.BUILD
  24. twisted.BUILD
  25. yaml.BUILD
  26. zlib.BUILD
  27. zope_interface.BUILD

Third-party libraries

gRPC depends on several third-party libraries, their source code is available (usually as a git submodule) in this directory.

Guidelines on updating submodules

  • IMPORTANT: whenever possible, try to only update to a stable release of a library (= not to master / random commit). Depending on unreleased revisions makes gRPC installation harder for users, as it forces them to always build the dependency from source and prevents them from using more convenient installation channels (linux packages, package managers etc.)

  • bazel BUILD uses a different dependency model - whenever updating a submodule, also update the revision in grpc_deps.bzl so that bazel and non-bazel builds stay in sync (this is actually enforced by a sanity check in some cases)

Considerations when adding a new third-party dependency

  • gRPC C++ needs to stay buildable/installable even if the submodules are not present (e.g. the tar.gz archive with gRPC doesn't contain the submodules), assuming that the dependencies are already installed. This is a requirement for being able to provide a reasonable install process (e.g. using cmake) and to support package managers for gRPC C++.

  • Adding a new dependency is a lot of work (both for us and for the users). We currently support multiple build systems (BAZEL, cmake, make, ...) so adding a new dependency usually requires updates in multiple build systems (often not trivial). The installation process also needs to continue to work (we do have distrib tests to test many of the possible installation scenarios, but they are not perfect). Adding a new dependency also usually affects the installation instructions that need to be updated. Also keep in mind that adding a new dependency can be quite disruptive for the users and community - it means that all users will need to update their projects accordingly (for C++ projects often non-trivial) and the community-provided C++ packages (e.g. vcpkg) will need to be updated as well.

Checklist for adding a new third-party dependency


  • [ ] Make sure you understand the hidden costs of adding a dependency (see section above) and that you understand the complexities of updating the build files. Maintenance of the build files isn't for free, so expect to be involved in maintenance tasks, cleanup and support (e.g resolving user bugs) of the build files in the future.

  • [ ] Once your change is ready, start an adhoc run of artifact - packages - distribtests flow and make sure everything passes (for technical reasons, not all the distribtests can run on each PR automatically).

  • [ ] Check the impact of the new dependency on the size of our distribution packages (compare BEFORE and AFTER) and post the comparison on your PR (it should not be approved without checking the impact sizes of packages first). The package sizes AFTER can be obtained from the adhoc package build from bullet point above.

Instructions for updating dependencies

Usually the process is

  1. update the submodule to selected commit (see guidance above)
  2. update the dependency in grpc_deps.bzl to the same commit
  3. update tools/run_tests/sanity/ to make the sanity test pass
  4. (when needed) run tools/buildgen/ to regenerate the generated files
  5. populate the bazel download mirror by running bazel/

Updating some dependencies requires extra care.

Updating third_party/abseil-cpp

  • Two additional steps should be done before running above.
    • Running src/abseil-cpp/
    • Updating abseil_version = scripts in templates/gRPC-C++.podspec.template and templates/gRPC-Core.podspec.template.
  • You can see an example of previous upgrade.

Updating third_party/boringssl-with-bazel

  • Update the third_party/boringssl-with-bazel submodule to the latest main-with-bazel branch
git submodule update --init      # just to start in a clean state
cd third_party/boringssl-with-bazel
git fetch origin   # fetch what's new in the boringssl repository
git checkout origin/main-with-bazel  # checkout the current state of main-with-bazel branch in the boringssl repo
# Note the latest commit SHA on main-with-bazel branch
cd ../..   # go back to grpc repo root
git status   #  will show that there are new commits in third_party/boringssl-with-bazel
git add  third_party/boringssl-with-bazel     # we actually want to update the changes to the submodule
git commit -m "update submodule boringssl-with-bazel with origin/main-with-bazel"   # commit
  • Update boringssl dependency in bazel/grpc_deps.bzl to the same commit SHA as main-with-bazel branch

    • Update http_archive(name = "boringssl", section by updating the sha in strip_prefix and urls fields.
    • Also, set sha256 field to "" as the existing value is not valid. This will be added later once we know what that value is.
  • Update tools/run_tests/sanity/ with the same commit

  • Commit these changes git commit -m "update boringssl dependency to main-with-bazel commit SHA"

  • Run tools/buildgen/ to regenerate the generated files

    • Because sha256 in bazel/grpc_deps.bzl was left empty, you will get a DEBUG msg like this one:
      Rule 'boringssl' indicated that a canonical reproducible form can be obtained by modifying arguments sha256 = "SHA value"
    • Commit the regenrated files git commit -m "regenerate files"
    • Update bazel/grpc_deps.bzl with the SHA value shown in the above debug msg. Commit again git commit -m "Updated sha256"
  • Run tools/distrib/

    • Commit again git commit -m "generate boringssl prefix headers"
  • Increment the boringssl podspec version number in templates/src/objective-c/BoringSSL-GRPC.podspec.template and templates/gRPC-Core.podspec.template. example

    • Commit again git commit -m "Increment podspec version"
  • Run tools/buildgen/ (yes, again)

    • Commit again git commit -m "Second regeneration"
  • Create a PR with all the above commits.

  • Run bazel/ to update GCS mirror.

Updating third_party/protobuf

See http://go/grpc-third-party-protobuf-update-instructions (internal only)

Updating third_party/envoy-api

Apart from the above steps, please perform the following two steps to generate the Python xds-protos package:

  1. Bump the version in the tools/distrib/python/xds_protos/;
  2. Run tools/distrib/python/xds_protos/ to upload the built wheel.

Updating third_party/upb

Since upb is vendored in the gRPC repo, you cannot use submodule to update it. Please follow the steps below.

  1. Update third_party/upb directory by running
    • export GRPC_ROOT=~/git/grpc
    • wget
    • rm -rf $GRPC_ROOT/third_party/upb
    • unzip -d $GRPC_ROOT/third_party
    • mv $GRPC_ROOT/third_party/upb-main $GRPC_ROOT/third_party/upb
  2. Update the dependency in grpc_deps.bzl to the same commit
  3. Populate the bazel download mirror by running bazel/
  4. Update src/upb/ for newly added or removed upb files
  5. Run tools/buildgen/ to regenerate the generated files
  6. Run tools/codegen/core/ to regenerate upb files.

Updating third_party/xxhash

TODO( revisit LICENSE instructions if upstream splits library and CLI.

The upstream xxhash repository contains a bunch of files that we don't want, so we employ a rather manual update flow to pick up just the bits we care about:

git remote add xxhash
git fetch xxhash
git show xxhash/dev:xxhash.h > third_party/xxhash/xxhash.h
git show xxhash/dev:LICENSE | sed -nE '/^-+$/q;p' > third_party/xxhash/LICENSE