Skip to content

Latest commit

 

History

History
executable file
·
136 lines (96 loc) · 4.47 KB

README.md

File metadata and controls

executable file
·
136 lines (96 loc) · 4.47 KB

DOWNLOAD

Useful links

Cryply Core integration/staging tree

  • Copyright (c) 2017- Cryply Core Developers
  • Copyright (c) 2009-2017 Bitcoin Core Developers
  • Copyright (c) 2013-2017 Dash Developers (DarkGravityWave3)
  • Copyright (c) 2014-2018 Alexander Peslyak (YesPoWer Original)

How to build console wallet on Ubuntu 16.04

sudo apt-get -y install build-essential
sudo apt-get -y install libtool autotools-dev autoconf
sudo apt-get -y install libssl-dev
sudo apt-get -y install libboost-all-dev
sudo apt-get -y install pkg-config
sudo add-apt-repository ppa:bitcoin/bitcoin
sudo apt-get update
sudo apt-get -y install libdb4.8-dev
sudo apt-get -y install libdb4.8++-dev

git clone https://github.com/cryply/cryply-wallet.git cryply
cd cryply
./autogen.sh
./configure --enable-upnp-default --without-gui --disable-tests
make && make install

How to build QT wallet on Ubuntu 16.04

sudo apt-get update
sudo apt-get install -y build-essential libtool autotools-dev autoconf  
sudo apt-get install -y libssl-dev libboost-all-dev pkg-config
sudo apt-get install -y curl git unzip libssl-dev vim wget

sudo apt-get install -y libqrencode-dev libprotobuf-dev protobuf-compiler
sudo apt-get install -y libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools

cd ~
wget http://download.oracle.com/berkeley-db/db-4.8.30.zip
unzip db-4.8.30.zip
cd db-4.8.30/build_unix/
../dist/configure --prefix=/usr/local --enable-cxx
make && make install

cd ~
git clone https://github.com/cryply/cryply-wallet.git cryply
cd cryply
./autogen.sh
./configure --enable-upnp-default --disable-tests
make && make install

ls -la src/qt/ |grep cryply

Development tips and tricks

compiling for debugging

Run configure with the --enable-debug option, then make. Or run configure with CXXFLAGS="-g -ggdb -O0" or whatever debug flags you need.

debug.log

If the code is behaving strangely, take a look in the debug.log file in the data directory; error and debugging message are written there.

The -debug=... command-line option controls debugging; running with just -debug will turn on all categories (and give you a very large debug.log file).

The Qt code routes qDebug() output to debug.log under category "qt": run with -debug=qt to see it.

testnet and regtest modes

Run with the -testnet option to run with "play bitcoins" on the test network, if you are testing multi-machine code that needs to operate across the internet.

If you are testing something that can run on one machine, run with the -regtest option. In regression test mode blocks can be created on-demand; see qa/rpc-tests/ for tests that run in -regest mode.

DEBUG_LOCKORDER

Bitcoin Core is a multithreaded application, and deadlocks or other multithreading bugs can be very difficult to track down. Compiling with -DDEBUG_LOCKORDER (configure CXXFLAGS="-DDEBUG_LOCKORDER -g") inserts run-time checks to keep track of what locks are held, and adds warning to the debug.log file if inconsistencies are detected.

License

Cryply Core is released under the terms of the MIT license. See COPYING for more information or see http://opensource.org/licenses/MIT.