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
1 file changed
tree: 05f73a1c5922d90d8bf7190786b59a3c9616192b
  1. benchmarks/
  2. cmake/
  3. conformance/
  4. csharp/
  5. docs/
  6. editors/
  7. examples/
  8. java/
  9. javanano/
  10. jenkins/
  11. js/
  12. kokoro/
  13. m4/
  14. objectivec/
  15. patches/
  16. php/
  17. protoc-artifacts/
  18. python/
  19. ruby/
  20. src/
  21. third_party/
  22. util/
  23. .gitignore
  24. .gitmodules
  25. .travis.yml
  26. __init__.py
  27. appveyor.bat
  28. appveyor.yml
  29. autogen.sh
  30. BUILD
  31. BUILD.gn
  32. CHANGES.txt
  33. composer.json
  34. configure.ac
  35. CONTRIBUTORS.txt
  36. DEPS
  37. generate_changelog.py
  38. generate_descriptor_proto.sh
  39. gmock.BUILD
  40. LICENSE
  41. Makefile.am
  42. mirclient.cc
  43. mirclient.map
  44. OWNERS
  45. post_process_dist.sh
  46. proto_library.gni
  47. protobuf-lite.pc.in
  48. protobuf.bzl
  49. protobuf.pc.in
  50. Protobuf.podspec
  51. README.chromium
  52. README.md
  53. six.BUILD
  54. tests.sh
  55. update_file_lists.sh
  56. WORKSPACE
README.md

Protocol Buffers - Google's data interchange format

Build Status Build status Build Status Build Status Build Status

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

LanguageSource
C++ (include C++ runtime and protoc)src
Javajava
Pythonpython
Objective-Cobjectivec
C#csharp
JavaNanojavanano
JavaScriptjs
Rubyruby
Gogolang/protobuf
PHPphp
Dartdart-lang/protobuf

Usage

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

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