commit | 0d59e0f080d3d17c52e27e47225311f48882595b | [log] [tgz] |
---|---|---|
author | Bruce Dawson <brucedawson@chromium.org> | Wed Jan 31 21:33:08 2018 |
committer | Commit Bot <commit-bot@chromium.org> | Wed Jan 31 21:33:08 2018 |
tree | 05f73a1c5922d90d8bf7190786b59a3c9616192b | |
parent | e73d07eea630d30b6cf08e1b9f1c8bbf4ff89ccd [diff] |
Revert "Disable incremental linking for some tools" This reverts commit 1942fd8a7fe9fc609f51ef1fbff210ba5f356415. Reason for revert: This was a hack that attempted to fix random link failures. This hack ultimately didn't work because the crashes we were seeing were due to a kernel bug, not a linker bug. Original change's description: > Disable incremental linking for some tools > > We occasionally get build crashes because binaries (usually protoc.exe, > but others as well) are generated incorrectly. The symptom is that the > incremental linking thunks contain all zeroes instead of a branch > instruction, leading to crashes, usually access violations. This is > presumed to be a bug in the MSVC++ incremental linker. > > This turns off incremental linking for four of the binaries that hit > this issue most frequently, and some of their neighbors. These binaries > are all small enough that incremental linking is not important so there > is no real downside to making this change. > > Testing over the weekend shows that this error, or something very like > it, can happen even with incremental linking disabled. I hope that this > will reduce the frequency of the failures and there is no downside so > I'm going to proceed and see if it helps. > > Bug: 644525 > Cq-Include-Trybots: master.tryserver.chromium.android:android_cronet_tester;master.tryserver.chromium.mac:ios-simulator-cronet > Change-Id: I0a9b33b0ad8335868e8e6f227f9a21e5ddeff6e4 > Reviewed-on: https://chromium-review.googlesource.com/777764 > Commit-Queue: Bruce Dawson <brucedawson@chromium.org> > Reviewed-by: John Abd-El-Malek <jam@chromium.org> > Cr-Commit-Position: refs/heads/master@{#517990} TBR=jam@chromium.org,brucedawson@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 644525 Change-Id: Ib822f0850cdffe7cdf0112aac5c45a2200b63adf Cq-Include-Trybots: master.tryserver.chromium.android:android_cronet_tester;master.tryserver.chromium.mac:ios-simulator-cronet Reviewed-on: https://chromium-review.googlesource.com/894448 Reviewed-by: Bruce Dawson <brucedawson@chromium.org> Reviewed-by: John Abd-El-Malek <jam@chromium.org> Commit-Queue: Bruce Dawson <brucedawson@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#533419} Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src Cr-Mirrored-Commit: 7f063158562d2516620386721deb1339a3160e19
Copyright 2008 Google Inc.
https://developers.google.com/protocol-buffers/
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.
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:
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 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:
Language | Source |
---|---|
C++ (include C++ runtime and protoc) | src |
Java | java |
Python | python |
Objective-C | objectivec |
C# | csharp |
JavaNano | javanano |
JavaScript | js |
Ruby | ruby |
Go | golang/protobuf |
PHP | php |
Dart | dart-lang/protobuf |
The complete documentation for Protocol Buffers is available via the web at: