rust-libp2p/core/regen_structs_proto.sh

#!/bin/sh

# This script regenerates the `src/structs_proto.rs` and `src/keys_proto.rs` files from
# `structs.proto` and `keys.proto`.

sudo docker run --rm -v `pwd`:/usr/code:z -w /usr/code rust /bin/bash -c " \
    apt-get update; \
    apt-get install -y protobuf-compiler; \
    cargo install --version 2.3.0 protobuf-codegen; \
    protoc --rust_out . keys.proto"

sudo chown $USER:$USER keys.rs
mv -f keys.rs ./src/keys_proto.rs
The PeerId is the hash of the protobuf encoding (#276) 2018-06-25 17:56:36 +02:00			`#!/bin/sh`

			# This script regenerates the `src/structs_proto.rs` and `src/keys_proto.rs` files from
			# `structs.proto` and `keys.proto`.

			sudo docker run --rm -v `pwd`:/usr/code:z -w /usr/code rust /bin/bash -c " \
			`apt-get update; \`
			`apt-get install -y protobuf-compiler; \`
Update protobuf to version 2.3.0 (#904) Initially I had hoped that the deprecated `#![allow(clippy)]` would no longer be put into the generated rust files, but -- as of 2019-01-30 -- it still is (see [1] for details). Since we explicitly update the protobuf files I decided to manually edit the generated code and replace this with `#![allow(clippy:all)]`. Hopefully, by the time we do the next upgrade, no such manual tweaking would be necessary anymore. I think the benefit of a less polluted clippy output is worth it this time. [1]: https://github.com/stepancheg/rust-protobuf/pull/332 2019-01-30 16:25:45 +01:00			`cargo install --version 2.3.0 protobuf-codegen; \`
The PeerId is the hash of the protobuf encoding (#276) 2018-06-25 17:56:36 +02:00			`protoc --rust_out . keys.proto"`

Upgrade and unify protobuf version(1.x => 2.0.2) (#283) * Update and unify protobuf version(1.x => 2.0.2) * Update protobuf codegen shell script 2018-07-10 20:07:28 +08:00			`sudo chown $USER:$USER keys.rs`
The PeerId is the hash of the protobuf encoding (#276) 2018-06-25 17:56:36 +02:00			`mv -f keys.rs ./src/keys_proto.rs`