-
Notifications
You must be signed in to change notification settings - Fork 2
getting the code and compile
at this moment two good working solutions for access to the goerli testnet in conjunction with parity-ethereum exist.
Source : https://github.com/goerli/parity-goerli
important for me was not to clone the git into local filestructures
but to download a zip as certain "release" version which works fine at the moment.
Once downloaded or cloned the compilation process is about to follow.
To cut a long story short-
i work with ubuntu therefore the dev-env for me are quite easy-
first to install rust with
curl https://sh.rustup.rs -sSf | sh
if needed add an sudo in front of the command and do as told, as understand or as written "there"-
This curl command has to typed into the terminal on the host.
Afterwards some "installation successful" with a version number,
this should be at least rust1.30 or higher-
otherwise the compiler threw errors at my tests-
at the end of the installation of rust a command has to to be typed:
source $HOME/.cargo/env
next are the parity"dev" packets to get:
sudo apt-get install gcc g++ libudev-dev pkg-config file make cmake
and
sudo Perl Yasm
as done so far, good if any errors occor, try it stepwise again- next place to ask for could be the gitter channel.
From now we can do the "job" to compile without any further interruptions.
As you deflated the zip/tgz into a certain directory change afterwards the installations into it.
mine was named for absolute clearness that this is the goerli-dev-bin, as "parity-ethereum-clique"
which is an actual implementation of clique.
now, standing with a blinking coursor in that directory
just a
"cargo build --release"
is to be typed.
Afterwards as anything runs fine, you have a binary named parity within the /target/release subfolder tree, which is fine