aboutsummaryrefslogtreecommitdiffhomepage
path: root/grpc.BUILD
Commit message (Collapse)AuthorAge
* Optimize Bazel external dependenciesGravatar Justine Tunney2016-09-21
| | | | | | | | | | | | | | | | | | | | | | This change does the following: - Always use {,new_}http_archive rather than git_repository - Make liberal use of strip_prefix - Clarify licenses() in BUILD files - On POSIX include headers like a normal C/C++ program This change accomplishes the following: - Reduce download size >100MB: The biggest culprit is grpc which has tens of thousands of commits in its GitHub repository. - Reduce disk size >200MB: On disk, grpc takes up 250MB when cloned even though the tarball of the git repo is 3.2MB. By never using git externals, we save on network. - Consume less cpu: Cloning git repositories is much slower than downloading and extracting a tarball. Change: 133895791
* Merge changes from github.Gravatar Martin Wicke2016-09-21
| | | | Change: 133874452
* Add -std=gnu99 build flag to the gRPC++ build target to unbreak TensorFlow ↵Gravatar Kiril Gorovoy2016-09-14
| | | | | | Serving. We can remove it when https://github.com/grpc/grpc/issues/7851 is fixed and incorportated into TensorFlow. Change: 133193927
* Remove unnecessary compiler option from the grpc++_unsecure target.Gravatar Derek Murray2016-08-24
| | | | | | | | This is no longer necessary because we manually delete the C99 source files from this target that appear in the upstream gRPC BUILD file. The gRPC issue for this problem is: https://github.com/grpc/grpc/issues/7851 Change: 131182216
* Upgrade to latest gRPC (1.0.x branch).Gravatar Derek Murray2016-08-23
| | | | Change: 131132846
* Merge changes from github.Gravatar Vijay Vasudevan2016-06-11
| | | | Change: 124644444
* Introduce grpc++ target to grpc.BUILD that TF is currently using.Gravatar Kiril Gorovoy2016-06-07
| | | | Change: 124299122
* Specializes the implementation of the gRPC Master and Worker services.Gravatar Derek Murray2016-06-03
This takes previously generated code, and includes it in the repository. The main advantage of doing this is that we can specialize the deserialization routines for various protobuf types that tend to be large, and thereby avoid the problem where we brush up against the default protobuf limits. Fixes #2233. Change: 124007049