build system updates

README-mac.md

@@ -22,13 +22,12 @@ brew tap discoteq/discoteq; brew install flock autoconf autogen automake gcc@6 b
 Get all that installed, then run:
 
 ```shell
-git clone https://github.com/VerusCoin/VerusCoin.git
-cd VerusCoin
+git clone https://github.com/MyHush/hush3
+cd hush3
 ./zcutil/build-mac.sh
-./zcutil/fetch-params.sh
 ```
 
-To build a distributable version of VerusCoin then run the makeReleaseMac.sh script after building. This will fix the dependency references and move the komodod and komodo-cli binaries to the kmd/mac/verus-cli directory along with the 6 libraries required for it to work properly.
+To build a distributable version of Hush then run the makeReleaseMac.sh script after building. This will fix the dependency references and move the komodod and komodo-cli binaries to the kmd/mac/verus-cli directory along with the 6 libraries required for it to work properly.
 
 When you are done building, you need to create `Komodo.conf` the Mac way. 
 

doc/man/verus-cli/linux/README.txt

@@ -1,13 +0,0 @@
-VerusCoin Command Line Tools v0.4.0c
-
-Contents:
-komodod - VerusCoin's enhanced Komodo daemon
-komodo-cli - VerusCoin's Komodo command line utility
-verus - wrapper for komodo-cli that applies the command to the VRSC coin
-verusd - wrapper for komodod that sets the VerusCoin parameters to defaults properly
-
-The first time on a new system you will need to run ./fetch-params before using komodod or verusd.
-
-Run ./verusd to launch komodod, and use verus to run commands such as:
-./verus stop
-Which signals komodod (if it is running) to stop running.

doc/man/verus-cli/mac/README.txt

@@ -1,17 +0,0 @@
-VerusCoin Command Line Tools v0.4.0c
-Contents:
-komodod - VerusCoin's enhanced Komodo daemon.
-komodo-cli - VerusCoin's enhanced Komodo command line utility.
-verus - wrapper for komodo-cli that applies the command to the VRSC coin
-verusd - wrapper for komodod that sets the VerusCoin parameters to defaults properly
-fetch_params.sh - utility to download the zcash parameters needed to start the VerusCoin command line tools and scripts
-lib*.dylib - assorted dynamic libraries, dependencies needed by fetch-params.sh, komodod and/or komodo-cli
-
-Command line tools are run from the terminal. You can launch the terminal on a Mac by using the Finder, selecting Applications and from that select Utilities, finally selecting Terminal from the Utilities folder.
-You will need to switch to the directory you extracted the verus-cl into. If you extracted it in the Download folder then the change directory command is
-cd ~/Downloads/verus-cli
-The first time on a new system you will need to run ./fetch-params before using komodod or verusd.
-
-Run ./verusd to launch komodod, and use verus to run commands such as:
-./verus stop
-Which signals komodod (if it is running) to stop running.

doc/man/verus-cli/windows/README.txt

@@ -1,21 +0,0 @@
-VerusCoin Command Line Tools v0.4.0c
-Contents:
-komodod.exe - VerusCoin's enhanced Komodo daemon
-komodo-cli.exe - VerusCoin's Komodo command line utility
-verus.bat - wrapper for komodo-cli that applies the command to the VRSC coin
-verusd.bat - wrapper for komodod that sets the VerusCoin parameters to defaults properly
-
-You need to run a command prompt, for example hit <Ctrl><Esc> and type cmd<Enter>
-From the command prompt change to the directory where you installed verus-cli. If you downloaded the file to your Downloads directory and extracted it there then the change directory command is
-cd \Users\MyName\Downloads\verus-cli
-From this directory you can run the Verus command line utilities.
-The first time on a new system you will need to run fetch-params before using komodod.exe or verusd.
-Many anti-virus products interfere with the VerusCoin tool's ability to open ports and will need to be configured to allow what the scanner says is unsafe behavior.
-Extreme cases can result in the virus scanner deleting Agama.exe or moving it to "protect" the system. You will to add the executables to a whitelist and re-extract the verus-cli-windows.zip file if that happens.
-Run verusd.bat to launch komodod, and use verus.bat to run commands such as:
-verus.bat stop
-Which signals komodod.exe (if it is running) to stop running.
-
-Note that if you pass in command line options to verus.bat or verusd.bat that include an = like -ac_veruspos=50 you must surround it with double quotes like this:
-verusd.bat "-ac_veruspos=50"
-Otherwise Windows will drop the = and pass the two values in as separate command line options.

makeReleaseMac.sh

@@ -1,12 +1,16 @@
-#!/bin/sh
+#!/bin/bash
+# Copyright ? various authors too lazy to put a copyright header
+# Copyright 2019 The Hush Developers
 
 PACKAGE_DIR="$@"
 mkdir ${PACKAGE_DIR}
+echo "Created ${PACKAGE_DIR}"
 
 binaries=("komodo-cli" "komodod")
 alllibs=()
 for binary in "${binaries[@]}";
 do
+    echo "Processing binary ${binary}"
     # do the work in the destination directory
     cp src/${binary} ${PACKAGE_DIR}
     # find the dylibs to copy for komodod
@@ -20,6 +24,7 @@ libraries=("libgcc_s.1.dylib" "libgomp.1.dylib" "libidn2.0.dylib" "libstdc++.6.d
 
 for binary in "${libraries[@]}";
 do
+    echo "Processing binary ${binary}"
     # find the dylibs to copy for komodod
     DYLIBS=`otool -L ${PACKAGE_DIR}/${binary} | grep "/usr/local" | awk -F' ' '{ print $1 }'`
     echo "copying ${DYLIBS} to ${PACKAGE_DIR}"
@@ -31,6 +36,7 @@ indirectlibraries=("libintl.8.dylib" "libunistring.2.dylib")
 
 for binary in "${indirectlibraries[@]}";
 do
+    echo "Processing binary ${binary}"
     # Need to undo this for the dylibs when we are done
     chmod 755 src/${binary}
     # find the dylibs to copy for komodod
@@ -42,6 +48,7 @@ done
 
 for binary in "${binaries[@]}";
 do
+    echo "Processing binary ${binary}"
     # modify komodod to point to dylibs
     echo "modifying ${binary} to use local libraries"
     for dylib in "${alllibs[@]}"
@@ -54,6 +61,7 @@ done
 
 for binary in "${libraries[@]}";
 do
+    echo "Processing binary ${binary}"
     # modify libraries to point to dylibs
     echo "modifying ${binary} to use local libraries"
     for dylib in "${alllibs[@]}"