commit | c367564763cbe08a9806eda133418893a18376f0 | [log] [tgz] |
---|---|---|
author | Alexandre Frechette <frechette@chromium.org> | Wed Mar 04 17:53:52 2020 |
committer | Commit Bot <commit-bot@chromium.org> | Wed Mar 04 17:53:52 2020 |
tree | 4282c5e9f464752035d4342c37abe8ca43d869b1 | |
parent | e0c33a699313d9666eab288383650ae3c5ef9086 [diff] |
Revert "Adding mojolpm fuzzer." This reverts commit 96b8d308d93e9f014d795ceb20474b6be9f42c12. Reason for revert: Caused compile failures - see https://ci.chromium.org/p/chromium/builders/ci/win32-archive-rel/10808. Original change's description: > Adding mojolpm fuzzer. > > This adds code that generates libprotobuf-mutator based > structure-aware fuzzers as part of the mojom compilation process. > (changes in //mojo). > > It also adds a fuzzer for CodeCacheHost using this framework to demonstrate > how it will be used, and documentation explaining that fuzzer and how to use > this generator to write new fuzzers. (changes in //content/test). > > It finally includes a few changes to typemap and traits files that > were necessary to smooth over some inconsistencies in existing code > using mojo. > > Bug: 941849 > Change-Id: I660a57bd90c0963bd9a0b8608c746cdb767edc98 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1978739 > Commit-Queue: Mark Brand <markbrand@google.com> > Auto-Submit: Mark Brand <markbrand@google.com> > Reviewed-by: Peter Kasting <pkasting@chromium.org> > Reviewed-by: Daniel Cheng <dcheng@chromium.org> > Reviewed-by: Ted Meyer <tmathmeyer@chromium.org> > Reviewed-by: Oliver Chang <ochang@chromium.org> > Reviewed-by: Ken Rockot <rockot@google.com> > Cr-Commit-Position: refs/heads/master@{#746827} TBR=pkasting@chromium.org,dcheng@chromium.org,rockot@google.com,ochang@chromium.org,markbrand@google.com,mpdenton@google.com,tmathmeyer@chromium.org,tmathmeyer@google.com Change-Id: I3b92169e4d15940eda618f83566020a20b58e6ad No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 941849 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2087974 Reviewed-by: Alexandre Frechette <frechette@chromium.org> Commit-Queue: Alexandre Frechette <frechette@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#746844} Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src Cr-Mirrored-Commit: 24dba428a87bf21d853b7fff19741d25ffa6b0f7
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/protocolbuffers/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 | Ubuntu | MacOS | Windows |
---|---|---|---|---|
C++ (include C++ runtime and protoc) | src | |||
Java | java | |||
Python | python | |||
Objective-C | objectivec | |||
C# | csharp | |||
JavaScript | js | |||
Ruby | ruby | |||
Go | golang/protobuf | |||
PHP | php | |||
Dart | dart-lang/protobuf |
The best way to learn how to use protobuf is to follow the tutorials in our developer guide:
https://developers.google.com/protocol-buffers/docs/tutorials
If you want to learn from code examples, take a look at the examples in the examples directory.
The complete documentation for Protocol Buffers is available via the web at: