armor-reborn

Armornetwork Reborn

Armor Network

About

Welcome to the repository of Armor. Here you will find source code, instructions, wiki resources, and integration tutorials.

Contents

• Building on Linux 64-bit
• Building on Mac OSX
• Building on Windows
• Building on other platforms

Building on Linux 64-bit

All commands below work on Ubuntu 18.*, other distributions may need different command set.

Building with standard options

Create directory armor somewhere and go there:

$> mkdir armor
$> cd armor

To go futher you have to have a number of packages and utilities. You need at least gcc 5.4.

• build-essential package:

  $armor> sudo apt-get install build-essential
  

• libudev:

  sudo apt-get install libudev-dev
  

• CMake (3.0 or newer):

  $armor> sudo apt-get install cmake
  $armor> cmake --version
  

  If version is too old, follow instructions on the official site.

• Boost (1.65 or newer): We use boost as a header-only library via find_boost package. So, if your system has boost installed and set up, it will be used automatically.

  Note - there is a bug in boost::asio 1.66 that affects armord. Please use either version 1.65 or 1.67+.

  $armor> sudo apt-get install libboost-dev
  

  If the latest boost installed is too old (e.g. for Ubuntu 16.*), then you need to download and unpack boost into the armor/boost folder.

  $armor> wget -c 'https://dl.bintray.com/boostorg/release/1.69.0/source/boost_1_69_0.tar.gz'
  $armor> tar -xzf ./boost_1_69_0.tar.gz
  $armor> rm ./boost_1_69_0.tar.gz
  $armor> mv ./boost_1_69_0/ ./boost/
  

• OpenSSL (1.1.1 or newer): Install OpenSSL to armor/openssl folder. (In below commands use switch linux-x86_64-clang instead of linux-x86_64 if using clang.)

  $armor> git clone --single-branch --branch OpenSSL_1_1_1b --depth 1 https://github.com/openssl/openssl.git
  $armor> cd openssl
  $armor/openssl> ./Configure linux-x86_64 no-shared
  $armor/openssl> make -j8
  $armor/openssl> cd ..
  

• LMDB Source files are referenced via relative paths, so you do not need to separately build it: Please note, we use LMDB only when building 64-bit daemons. For 32-bit daemons SQLite is used instead.

  Difference to official LMDB repository is lifted 2GB database limit if built by MSVC (even of 64-bit machine).

  $armor> git clone https://github.com/Armor-Network/lmdb.git
  $armor> cd lmdb
  $armor\lmdb> last_commit=$(git rev-parse HEAD); cmp -bs <(echo -n $last_commit) <(echo -n 01b1b7dc204abdf3849536979205dc9e3a0e3ece) || echo "Hash of last commit $last_commit is mismatch";
  $armor> cd ..
  

Git-clone (or git-pull) Armor source code in that folder:

$armor> git clone https://github.com/Armor-Network/armor.git
$armor> cd armor
$armor/armor> last_commit=$(git rev-parse HEAD); cmp -bs <(echo -n $last_commit) <(echo -n HASH-OF-LAST-VALID-COMMIT) || echo "Hash of last commit $last_commit is mismatch";
$armor/armor> cd ..

Create build directory inside armor, go there and run CMake and Make:

$armor> mkdir -p armor/build
$armor> cd armor/build
$armor/armor/build> cmake ..
$armor/armor/build> make -j8

Check built binaries by running them from ../bin folder

$armor/armor/build> ../bin/armord -v

Building on Mac OSX

Building with standard options (10.11 El Capitan or newer)

You need command-line tools. Either get XCode from an App Store or run 'xcode-select --install' in terminal and follow instructions. First of all, you need Homebrew.

Then open terminal and install CMake and Boost:

• brew install cmake
• brew install boost

Create directory armor somewhere and go there:

$~/Downloads> mkdir armor
$~/Downloads> cd armor

Git-clone (or git-pull) Armor source code in that folder:

$~/Downloads/armor> git clone https://github.com/Armor-Network/armor.git
$~/Downloads/armor> cd armor
$~/Downloads/armor/armor> last_commit=$(git rev-parse HEAD); cmp -bs <(echo -n $last_commit) <(echo -n HASH-OF-LAST-VALID-COMMIT) || echo "Hash of last commit $last_commit is mismatch";
$~/Downloads/armor/armor> cd ..

Put LMDB source code in armor folder (source files are referenced via relative paths, so you do not need to separately build it):

$~/Downloads/armor> git clone https://github.com/Armor-Network/lmdb.git
$~/Downloads/armor> cd lmdb
$~/Downloads/armor/armor> last_commit=$(git rev-parse HEAD); cmp -bs <(echo -n $last_commit) <(echo -n 01b1b7dc204abdf3849536979205dc9e3a0e3ece) || echo "Hash of last commit $last_commit is mismatch";
$~/Downloads/armor/armor> cd ..

Install OpenSSL to armor/openssl folder:

$~/Downloads/armor> git clone --single-branch --branch OpenSSL_1_1_1b --depth 1 https://github.com/openssl/openssl.git
$~/Downloads/armor> cd openssl
$~/Downloads/armor/openssl> ./Configure darwin64-x86_64-cc no-shared -mmacosx-version-min=10.11
$~/Downloads/armor/openssl> make -j8
$~/Downloads/armor/openssl> cd ..

Create build directory inside armor, go there and run CMake and Make:

$~/Downloads/armor> mkdir armor/build
$~/Downloads/armor> cd armor/build
$~/Downloads/armor/armor/build> cmake ..
$~/Downloads/armor/armor/build> make -j8

Check built binaries by running them from ../bin folder:

$~/Downloads/armor/armor/build> ../bin/armord -v

Building on Windows

You need Microsoft Visual Studio Community 2017. Download and install it selecting C++, git, cmake integration packages. Run Visual Studio x64 command prompt from start menu.

Create directory armor somewhere:

$C:\> mkdir armor
$C:\> cd armor

Boost (1.65 or newer): We use boost as a header-only library via find_boost package. So, if your system has boost installed and set up, it will be used automatically. If not, you need to download and unpack boost into armor/boost folder.

Git-clone (or git-pull) Armor source code in that folder:

$C:\armor> @git clone https://github.com/Armor-Network/armor.git
$C:\armor> cd armor
$C:\armor\armor> @FOR /F "tokens=*" %a in ('git rev-parse HEAD') do @(SET last_commit=%a)
$C:\armor\armor> @if NOT "%last_commit%" == "HASH-OF-LAST-VALID-COMMIT" echo "Hash of last commit %last_commit% is mismatch";
$C:\armor\armor> cd ..

Put LMDB in the same folder (source files are referenced via relative paths, so you do not need to separately build it):

$C:\armor> git clone https://github.com/Armor-Network/lmdb.git
$C:\armor> cd armor
$C:\armor\armor> @FOR /F "tokens=*" %a in ('git rev-parse HEAD') do @(SET last_commit=%a)
$C:\armor\armor> @if NOT "%last_commit%" == "01b1b7dc204abdf3849536979205dc9e3a0e3ece" echo "Hash of last commit %last_commit% is mismatch";
$C:\armor\armor> cd ..

Download amalgamated SQLite 3 and unpack it into the same folder (source files are referenced via relative paths, so you do not need to separately build it).

You need to build openssl, first install ActivePerl (select "add to PATH" option, then restart console):

$C:\armor> git clone --single-branch --branch OpenSSL_1_1_1b --depth 1 https://github.com/openssl/openssl.git
$C:\armor> cd openssl
$C:\armor\openssl> perl Configure VC-WIN64A no-shared no-asm
$C:\armor\openssl> nmake
$C:\armor\openssl> cd ..

If you want to build 32-bit binaries, you will also need 32-bit build of openssl in separate folder (configuring openssl changes header files, so there is no way to have both 32-bit and 64-bit versions in the same folder):

$C:\armor> git clone --single-branch --branch OpenSSL_1_1_1b --depth 1 https://github.com/openssl/openssl.git openssl32
$C:\armor> cd openssl32
$C:\armor\openssl> perl Configure VC-WIN32 no-shared no-asm
$C:\armor\openssl> nmake
$C:\armor\openssl> cd ..

Now launch Visual Studio, in File menu select Open Folder, select C:\armor\armor folder. Wait until CMake finishes running and Build appears in main menu. Select x64-Debug or x64-Release from standard toolbar, and then Build/Build Solution from the main menu.

Building with options

You can build daemons that use SQLite istead of LMDB on any platform by providing options to CMake. You may need to clean 'build' folder, if you built with default options before, due to cmake aggressive caching.

$armor/build> cmake -DUSE_SQLITE=1 ..
$armor/build> time make -j8

Building on 32-bit x86 platforms, iOS, Android and other ARM platforms

Armor works on 32-bit systems if SQLite is used instead of LMDB (we've experienced lots of problems building and running with lmdb in 32-bit compatibility mode, especially on iOS).

Building source code for iOS, Android, Raspberry PI, etc is possible (we have experimental armord and walletd running on ARM64 iPhone) but requires major skills on your part. TBD

Building on Big-Endian platforms

Currently armor does not work out of the box on any Big-Endian platform, due to some endianess-dependent code. This may be fixed in the future. If you wish to run on Big-Endian platform, please contact us.

Building with parameters

If you want to use tools like clang-tidy, run cmake -DCMAKE_EXPORT_COMPILE_COMMANDS=ON .. instead of cmake ..