commit | fdcf7c808165493ea6e99da06b5a1bfe6c5ef3d5 | [log] [tgz] |
---|---|---|
author | Joel Galenson <jgalenson@google.com> | Thu Oct 28 13:57:06 2021 -0700 |
committer | Joel Galenson <jgalenson@google.com> | Thu Oct 28 14:02:04 2021 -0700 |
tree | 20d23f98afdddc14045d4d2c40896f389a5b7592 | |
parent | dafb9684c423543957a43185916251d0a88a5376 [diff] |
Remove deprecated file. This readme talked about updating the version number, but this is now handled by cargo2android.py and the cargo_pkg_version field in the Android.bp file. It also warns about rerunning cargo2android.py and verifying changes caused by build.rs, but that's true for other crates, so this doesn't seem required, although it could potentially still have value. Test: None Change-Id: I3fe74b3acd40b80fca4e1cc71e7067daf872d99f
This crate contains protobuf code generator and a protoc-gen-rust
protoc
plugin.
protoc-gen-rust
implements standard protobuf protoc
plugin conventions.
Probably you do not want to use it directly in Rust environment, there are easier to use alternatives:
build.rs
of your project which requires only protoc
in $PATH
but not protoc-gen-rust
.protoc
binary(Note protoc
can be invoked programmatically with protoc crate)
protoc
binary.On OS X Homebrew can be used:
brew install protobuf
On Ubuntu, protobuf-compiler
package can be installed:
apt-get install protobuf-compiler
Protobuf is needed only for code generation, rust-protobuf
runtime does not use protobuf
library.
protoc-gen-rust
program (which is protoc
plugin)It can be installed either from source or with cargo install protobuf
command.
protoc-gen-rust
to $PATHIf you installed it with cargo, it should be
PATH="$HOME/.cargo/bin:$PATH"
protoc --rust_out . foo.proto
This will generate .rs files in current directory.