Bitcoin 0.15.1 doesn't build with boost 1.66.
I'm hesitant to apply untested patches to software like Bitcoin.
Instead I'm forcing the boost dependency to version 1.64 (which is the version listed @
45173fa6fc/doc/dependencies.md).
Nothing in applications/altcoins/default.nix was using the boost162 parameter, so I've replaced it with the boost164 parameter.
Upgrade to new version. According to the upstream documentation, this project is
only tested on python3, so I've upgraded the pkg's interpreter as well.
Tested with nix-build and ./result/bin/cryptop
I have also updated the dependencies for bitcoin:
* qt4 is updated to qt5
* miniupnpc 1 is updated to miniupnpc 2
* zeromq dependency has been added to enable ZeroMQ support.
The biggest benefit is that we no longer have to update the registry
package. This means that just about any cargo package can be built by
nix. No longer does `cargo update` need to be feared because it will
update to packages newer then what is available in nixpkgs.
Instead of fetching the cargo registry this bundles all the source code
into a "vendor/" folder.
This also uses the new --frozen and --locked flags which is nice.
Currently cargo-vendor only provides binaries for Linux and
macOS 64-bit. This can be solved by building it for the other
architectures and uploading it somewhere (like the NixOS cache).
This also has the downside that it requires a change to everyone's deps
hash. And if the old one is used because it was cached it will fail to
build as it will attempt to use the old version. For this reason the
attribute has been renamed to `cargoSha256`.
Authors:
* Kevin Cox <kevincox@kevincox.ca>
* Jörg Thalheim <Mic92@users.noreply.github.com>
* zimbatm <zimbatm@zimbatm.com>
This requires some small changes in the stdenv, then working around the
weird choice LLVM made to hardcode @rpath in its install name, and then
lets us remove a ton of annoying workaround hacks in many of our Go
packages. With any luck this will mean less hackery going forward.
