xctool is preinstalled on the Travis OS X images and it seems to do better with
iOS simulator flake, so use it instead of xcodebuild.

xctool also is less chatty compared to xcodebuild, so it makes the logs a little
easier to read.

Add ObjC build to travis setup

- Add objc for iOS and OS X builds to travis configs.
- Update handing of python install to deal with newer OS X versions.

Stop removing all blank lines in doc comments.

Tweaks to the Mac build script

This fixes issue #832.

Generated code changes in next commit.

Add recursion limit handling to JSON parsing.

include plugin.proto and generated code in protobuf-java

- Support building with Xcode 6.4 or 7.x
- Fix an error in usage info.
- Add a flag to build the core parts of protobuf only.

Added a TODO around a possible change to the tokenizer API, changing PushBack(token) into just Rewind() or something similar.

Move the creation of the "fields by JSON name" dictionary to the descriptor

Created a new exception for JSON failures.

Update the Mac build script to include the conformance tests

This is only thrown directly by JsonTokenizer, but surfaces from JsonParser as well. I've added doc comments to hopefully make everything clear.

The exception is actually thrown by the reader within JsonTokenizer, in anticipation of keeping track of the location within the document, but that change is not within this PR.

- Kick off the conformance tests
- Add missing ignore for something generated by a build on the conformance directory.

Fixes issue #932.

Implement JSON parsing in C#.

Build protoc for host platform to enable cross-compilation.

Add support for POWER Linux

This is necessary to run protoc on the host as a dependency for Android BUILD targets with Bazel.

This includes all the well-known types except Any.
Some aspects are likely to require further work when the details of the JSON parsing expectations are hammered out in more detail. Some of these have "ignored" tests already.

Note that the choice *not* to use Json.NET was made for two reasons:
- Going from 0 dependencies to 1 dependency is a big hit, and there's not much benefit here
- Json.NET parses more leniently than we'd want; accommodating that would be nearly as much work as writing the tokenizer
This only really affects the JsonTokenizer, which could be replaced by Json.NET. The JsonParser code would be about the same length with Json.NET... but I wouldn't be as confident in it.

add warning notes for cc|py_proto_library rules.

Fix compilation errors when built internally.

  1. mathlimits.h must be included before the inclusion of cmath (which
     gtest/gtest.h seems to include).
  2. hash function for StringPiece doesn't work.

Change-Id: I358a25d941a25b10b39fe76780eda41557699811

To mention that the interface may change or be removed when bazel has
support it natively.

Make BytesString.Unsafe internal (which it should have been all along)

Correct spelling

Fix clearing wrapper type fields with reflection.

The nullable value type fields already worked, but the use of the CLR property concealed the difference between string and StringWrapper fields.

Get VS 2015 to use const int definitions

VC++ up to VS 2015 RTM does not require explicit storage allocation for
static const integers declared in classes. VS 2015 Update 1 requires
these storage definitions in some cases. It's unclear exactly what
cases - simple tests work with and without the explicit storage
allocation.

Many previous versions of VC++ have theoretically *allowed* a
definition to supply storage, but tests on VC++ 2013 show that this
doesn't actually work correctly - it leads to duplicate definition
errors in Chromium. So, the change is scoped to VS 2015 only.

This change also updates the generated files to match the new generator.

TL;DR - this change is necessary in order for Chromium to build with
VS 2015 Update 1.

Removed all warnings from the Python/C++ build