lukechilds
/
ethminer
mirror of https://github.com/lukechilds/ethminer.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
55 Commits
3 Branches
10 Tags
52 MiB
 
 
 
 
 
Tree: e8b2ceeb60
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'e8b2ceeb60'
${ noResults }
Gav Wood e8b2ceeb60
More verification work; compute header ready for mining. 		11 years ago
eth More verification work; compute header ready for mining. 11 years ago
libethereum More verification work; compute header ready for mining. 11 years ago
test More verification work; compute header ready for mining. 11 years ago
.gitignore Removed user project files. 11 years ago
CMakeLists.txt Repotting and big-picture stuff. 11 years ago
CodingStandards.txt More commenting. 11 years ago
LICENSE Initial commit 11 years ago
README.md Move crypto/hash algos over to libcrypto++. 11 years ago
astylerc Coding standards doc. 11 years ago

README.md

ethereum

Ethereum C++ Client.

Gav Wood, 2014.

Dependencies

secp256k1 implementation: https://github.com/sipa/secp256k1.git Expects secp256k1 directory to be in same path as cpp-ethereum.

(NOTE: secp256k1 requires a development installation of the GMP library, libssl and libcrypto++.)

libcrypto++, version 5.6.2 or greater (i.e. with SHA3 support). Because it's so recent, it expects this to be built in a directory libcrypto562 in the same path as cpp-ethereum.

A decent C++11 compiler (I use GNU GCC 4.8.1) and a recent version of Boost (I use version 1.53) and leveldb (I use version 1.9.0).

CMake, version 2.8 or greater.

On Ubuntu:

sudo apt-get install libgmp3-dev libcrypto++-dev libssl-dev libboost-all-dev cmake libleveldb-dev

Building

mkdir /path/to/cpp-ethereum/../cpp-ethereum-build
cd /path/to/cpp-ethereum-build
cmake -DCMAKE_BUILD_TYPE=Debug /path/to/cpp-ethereum
make

Contributing

Please read CodingStandards.txt thoroughly before making alterations to the code base. Please do NOT use an editor that automatically reformats whitespace away from astylerc or the formating guidelines as describled in CodingStandards.txt.