| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\
| |
| | |
Basic Proto2 support for Ruby gem
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This change only adds basic proto2 support without advanced features
like extensions, custom options, maps, etc.
The protoc binary now generates ruby code for proto2 syntax.
However, for now, it is restricted to proto2 files without advanced features
like extensions, in which case it still errors out.
This change also modifies the DSL to add proto messages to the DescriptorPool.
There is a new DSL Builder#add_file to create a new FileDescriptor. With this,
the generated ruby DSL looks something like:
Google::Protobuf::DescriptorPool.generated_pool.build do
add_file "test.proto" do
add_message "foo" do
optional :val, :int32, 1
end
end
end
|
| |/
|
|
|
| |
This should put an end to all of the reports of unit test failures on
Windows machines.
|
| |
|
|
|
| |
This brings us more into line with other langauges, and makes it more
obvious when we are requiring protobuf generated code.
|
| |
|
|
| |
This includes all internal changes from around May 20 to now.
|
| | |
|
| |
|
|
|
| |
put built libraries. This directory hides the one that contains
ruby_generated_code.proto and ruby_generated_code.rb.
|
| |
|
|
| |
src/google/compiler/ruby depend on these two files, but they were missed in language distributions other than ruby
|
| | |
|
|
|
- A golden-file test that ensures protoc produces known-valid output.
- A Ruby test that loads that golden file and ensures it actually works
with the extension.
This split strategy allows us to test end-to-end without needing to
integrate the Ruby gem build system and the protoc build system. This is
desirable because we do not want a gem build/install to depend on
building protoc, and we do not want building protoc to depend on
building and testing the gem.
|
