Mac OS X Build Instructions and Notes

This guide will show you how to build neobytesd (headless client) for OSX.

Notes

Tested on OS X 10.7 through 10.11 on 64-bit Intel processors only.
All of the commands should be executed in a Terminal application. The built-in one is located in /Applications/Utilities.

Preparation

You need to install Xcode with all the options checked so that the compiler and everything is available in /usr not just /Developer. Xcode should be available on your OS X installation media, but if not, you can get the current version from https://developer.apple.com/xcode/. If you install Xcode 4.3 or later, you'll need to install its command line tools. This can be done in Xcode > Preferences > Downloads > Components and generally must be re-done or updated every time Xcode is updated.

You will also need to install Homebrew in order to install library dependencies.

The installation of the actual dependencies is covered in the instructions sections below.

Instructions: Homebrew

Install dependencies using Homebrew

brew install autoconf automake berkeley-db4 libtool boost miniupnpc openssl pkg-config protobuf libevent

NOTE: Building with Qt4 is still supported, however, could result in a broken UI. As such, building with Qt5 is recommended. Qt5 5.7 requires C++11 which NeoBytes Core doesn't fully support yet, Qt5 5.6.2 has some other issues, so make sure to install Qt version < 5.6.2 (5.6.1-1 is recommended). brew install https://raw.githubusercontent.com/Homebrew/homebrew-core/e6d954bab88e89c5582498157077756900865070/Formula/qt5.rb

Building NeoBytes Core

Clone the GitHub tree to get the source code and go into the directory.

 git clone https://github.com/neobytes-project/neobytes.git
 cd neobytes

Build NeoBytes Core: This will configure and build the headless neobytes binaries as well as the gui (if Qt is found). You can disable the gui build by passing --without-gui to configure.
```
./autogen.sh
./configure
make
```
It is also a good idea to build and run the unit tests:
```
make check
```
(Optional) You can also install neobytesd to your path:
```
make install
```

Use Qt Creator as IDE

You can use Qt Creator as IDE, for debugging and for manipulating forms, etc. Download Qt Creator from https://www.qt.io/download/. Download the "community edition" and only install Qt Creator (uncheck the rest during the installation process).

Make sure you installed everything through Homebrew mentioned above
Do a proper ./configure --enable-debug
In Qt Creator do "New Project" -> Import Project -> Import Existing Project
Enter "neobytes-qt" as project name, enter src/qt as location
Leave the file selection as it is
Confirm the "summary page"
In the "Projects" tab select "Manage Kits..."
Select the default "Desktop" kit and select "Clang (x86 64bit in /usr/bin)" as compiler
Select LLDB as debugger (you might need to set the path to your installation)
Start debugging with Qt Creator

Creating a release build

You can ignore this section if you are building neobytesd for your own use.

neobytesd/neobytes-cli binaries are not included in the NeoBytes-Qt.app bundle.

If you are building neobytesd or NeoBytes Core for others, your build machine should be set up as follows for maximum compatibility:

All dependencies should be compiled with these flags:

-mmacosx-version-min=10.7 -arch x86_64 -isysroot $(xcode-select --print-path)/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.7.sdk

Once dependencies are compiled, see doc/release-process.md for how the NeoBytes Core bundle is packaged and signed to create the .dmg disk image that is distributed.

Running

It's now available at ./neobytesd, provided that you are still in the src directory. We have to first create the RPC configuration file, though.

Run ./neobytesd to get the filename where it should be put, or just try these commands:

echo -e "rpcuser=neobytesrpc\nrpcpassword=$(xxd -l 16 -p /dev/urandom)" > "/Users/${USER}/Library/Application Support/NeoBytesCore/neobytes.conf"
chmod 600 "/Users/${USER}/Library/Application Support/NeoBytesCore/neobytes.conf"

The next time you run it, it will start downloading the blockchain, but it won't output anything while it's doing this. This process may take several hours; you can monitor its process by looking at the debug.log file, like this:

tail -f $HOME/Library/Application\ Support/NeoBytesCore/debug.log

Other commands:

./neobytesd -daemon # to start the neobytes daemon.
./neobytes-cli --help  # for a list of command-line options.
./neobytes-cli help    # When the daemon is running, to get a list of RPC commands

4.8 KiB Raw Blame History