Development

Releases

Statically compiled releases are built by travis-ci with --features update to allow notify-hook self update.
If you want to fork this project and continue building/self-updating with your github releases, you'll need
to enable the notify-hook repository in your travis-ci account and then update the update function
to point to your forked github repository.

If you prefer to build locally, there are two options:

If your build and target architectures are identical, you can get away with a simple cargo build --release. Note, this requires
libssl-dev to be installed in your build environment, and openssl installed on your target.

If you want to build static releases, like those built by travis-ci, you can use the build-release.py script.
This script requires docker and cross to be installed to produce statically compiled binaries. By default,
artifacts will be produced for i686 and x86_64. This can be tweaked in the TARGETS list of build-release.py.