aboutsummaryrefslogtreecommitdiff
path: root/COMPILING.md
AgeCommit message (Collapse)Author
2018-01-11COMPILING.md: Added note for IntelliJ building (#3958)Ryan Michela
2018-01-05Upgrade to Protobuf 3.5.1 and Protoc 3.5.1-1. (#3921)Kun Zhang
protoc-3.5.0-linux-x86_64 introduced GLIBC_2.14 dependency and broke gRPC release process (https://github.com/google/protobuf/issues/4138). 3.5.1-1 is the proper re-build.
2017-11-30all: update to proto 3.5.0Carl Mastrangelo
2017-08-25all: update to proto 3.4.0Carl Mastrangelo
2017-05-23all: bump to proto 3.3.1Carl Mastrangelo
2017-02-07all: update to protobuf 3.2.0Carl Mastrangelo
2016-11-01Bump protobuf to 3.1.0Eric Anderson
Also removed warnings about protoc version matching runtime, since this is no longer supposed to be a problem (starting with 3.0.0-beta-4) and all our tests ran fine when using protoc 3.0.2 with protobuf runtime 3.1.0. Fixes #2316
2016-09-29all: Bump protobuf to 3.0.2, to fix protoc in CIEric Anderson
protoc no longer builds in 3.0.0 because auto-download of the gmock zip now fails. 3.0.2 has a fix to autogen: https://github.com/google/protobuf/commit/bba446bbf2ac7b0b9923d4eb07d5acd0665a8cf0 All that was strictly necessary was to update .travis.yml and buildscripts/, but it helps our sanity to keep the rest of the protobuf versions in sync. Lite is left on its existing version, because it did not see a bump of neither the java library nor the protoc plugin.
2016-07-29Update protobuf to 3.0.0Eric Anderson
Fixes #2086
2016-06-28Bump protobuf dependency to 3.0.0-beta-3Eric Anderson
This allows us to play with zero-copy and proto3 support for lite. Unfortunately, it introduced some warnings, so deprecated warnings are now ignored for benchmarks and interop-testing.
2016-01-27Upgrade to protobuf-3.0.0-beta-2 and protobuf-nano-3.0.0-alpha-5Kun Zhang
Update option name that disables protobuf tests.
2015-09-24Update Windows building instructions for proto3b1Eric Anderson
2015-08-31Upgrade to protobuf-3.0.0-beta-1Kun Zhang
2015-08-14Split compiling instructions out of README.mdEric Anderson
The compilation instructions are long and scary, and they distract from other documentation in the README. Most users don't need them, so by moving the instructions out we improve the ease of use of the document.