aboutsummaryrefslogtreecommitdiffhomepage
path: root/examples
Commit message (Collapse)AuthorAge
* Add script for run and upload the benchmark result to bqGravatar Yilun Chong2018-04-10
|
* Add a check_protobuf_required_bazel_version() for use in WORKSPACEsGravatar Fahrzin Hemmati2017-12-04
|
* Fix go example test.Gravatar Feng Xiao2017-09-13
| | | | It needs "-I" flag to find imported file google/protobuf/timestamp.proto
* Add bazel support for examples.Gravatar Feng Xiao2017-09-08
| | | | | | | | The example utilizes native bazel rules (proto_library, cc_proto_library, java_proto_library, java_lite_proto_library) to show how easy it is to build protobuf with bazel's native support. It also makes use of well known types which was not possible until the latest bazel 0.5.4 release and https://github.com/google/protobuf/pull/3594 .
* from __future__ import print_functionGravatar cclauss2017-08-18
| | | The future import is required to support the print(x, end=" ") parameter in Python 2.
* print() function & define raw_input() for Python 3Gravatar cclauss2017-08-18
|
* Add classpath for java example MakefileGravatar king6cong2017-07-31
|
* add protobuf_generate function, allows use of target_sources where availableGravatar Walter Gray2017-06-02
|
* Integrate from internal code base.Gravatar Feng Xiao2016-07-13
|
* Use ExternalProject_Add to build the examples in a stand-alone fashion.Gravatar Walter Gray2016-06-06
|
* CMake project updatesGravatar Konstantin Podsvirov2016-06-04
| | | | | | | | | A series of improvements: - Improved Protobuf module compatibility (disabled by default); - Hide advanced settings; - Added build tree configuration; - Added build of examples.
* Merge pull request #1144 from dongjoon-hyun/remove_redundant_theGravatar Joshua Haberman2016-02-11
|\ | | | | Remove redundant `the`.
| * Remove redundant `the` in comments.Gravatar Dongjoon Hyun2016-02-03
| |
* | Updated python examples to use with.Gravatar Parth Kolekar2016-01-26
|/
* Merge pull request #1052 from tswast/masterGravatar Feng Xiao2015-12-17
|\ | | | | Add region tags to the Go protobuf examples.
| * Improves readability of Go example test.Gravatar Tim Swast2015-12-16
| |
| * Add region tags to the Go protobuf examples.Gravatar Tim Swast2015-12-15
| | | | | | | | | | | | | | | | | | | | | | This will allow us to like to specific snippets of code in the documentation. I plan to create a tutorial similar to the C# tutorial https://developers.google.com/protocol-buffers/docs/csharptutorial Since that tutorial has sections for populating a proto, parsing, and serializing, I made a region for each of these for Go. To make the populating sample more self-contained, I refactor the listing example slightly.
* | Add region tags for protocol buffers tutorials.Gravatar Tim Swast2015-12-01
|/ | | | | | | | | Since these tags might be confusing, added a note that these are not part of the normal protocol buffers syntax. I also linked to the main tutorials page that uses these examples https://developers.google.com/protocol-buffers/docs/tutorials so that anyone who arrived here without going through that info first can get more explanation if they want.
* Add a Go language example.Gravatar Tim Swast2015-11-25
| | | | | | | | | | | | | | | | | | This follows the other examples so that it can be used as a tutorial, such as the ones at: https://developers.google.com/protocol-buffers/docs/tutorials Even though Go generally does not use Makefiles, I added targets for the Go examples to be consistent with the other languages. Edit: Fix Travis run. Change to use $HOME instead of ~. Add protoc to path. GOPATH entry cannot start with shell metacharacter '~': "~/gocode" Edit(2): Fix Go code style to address comments.
* rename persons to peopleGravatar Jan Tattermusch2015-07-20
|
* use Google.Protobuf namespace for C#Gravatar Jan Tattermusch2015-07-20
|
* fixed java exampleGravatar Jan Tattermusch2015-07-20
|
* fix python exampleGravatar Jan Tattermusch2015-07-20
|
* fix C++ exampleGravatar Jan Tattermusch2015-07-20
|
* update addressbook.proto to proto3Gravatar Jan Tattermusch2015-07-20
|
* Make generate_protos.sh Windows-friendly.Gravatar Jon Skeet2015-05-14
| | | | | | | | | | To my surprise, executing generate_protos.sh used the version of Bash installed with Git for Windows by default. After a few modifications to detect the most appropriate protoc to use, this worked pretty simply. This change also: - adds generation of the address book tutorial proto, - fixes the addressbook.proto to specify proto2 explicitly (to avoid a warning from protoc; I don't think we want warnings...) - fixes the addressbook.proto C# namespace (which I thought I'd done before, but apparently hadn't) - includes the regenerated UnittestCustomOptions.cs apart from the DescriptorProtoFIle => Descriptor change
* Don't hard-code the python pathGravatar Tamir Duberstein2015-05-06
|
* Down-integrate from internal branch.Gravatar Feng Xiao2014-10-03
|
* Replace links to code.google.com/protobuf with ↵Gravatar Feng Xiao2014-10-01
| | | | developers.google.com/protocol-buffers
* merge tags/2.6.0 into trunkGravatar jieluo@google.com2014-08-25
|
* change java compiler to only produce one java fileGravatar jieluo@google.com2014-08-07
|
* down integrate to svnGravatar jieluo@google.com2014-07-18
|
* Close resources properly for java tests and examples.Gravatar liujisi@google.com2011-06-07
|
* Allow dependents to use pkg-config to figure out what flags to pass to link ↵Gravatar kenton@google.com2009-08-03
| | | | against protobuf.
* Down-integrate some code from an internal branch. (More to come.)Gravatar kenton@google.com2009-07-24
|
* Make sure examples link properly.Gravatar kenton@google.com2009-05-06
|
* Make Python example output identical to C++ and Java by removing redundantGravatar kenton@google.com2008-10-07
| | | | | spaces.
* Initial checkin.Gravatar temporal2008-07-10