update depends docs
This commit is contained in:
@@ -1,4 +1,4 @@
|
||||
### Usage
|
||||
### Hush Dependencies
|
||||
|
||||
To build dependencies for the current arch+OS:
|
||||
|
||||
@@ -13,7 +13,7 @@ For example:
|
||||
make HOST=x86_64-w64-mingw32 -j4
|
||||
|
||||
A prefix will be generated that's suitable for plugging into Bitcoin's
|
||||
configure. In the above example, a dir named x86_64-w64-mingw32 will be
|
||||
configure. In the above example, a dir named `x86_64-w64-mingw32` will be
|
||||
created. To use it for Bitcoin:
|
||||
|
||||
./configure --prefix=`pwd`/depends/x86_64-w64-mingw32
|
||||
|
||||
@@ -1,4 +1,9 @@
|
||||
This is a system of building and caching dependencies necessary for building Bitcoin.
|
||||
# Hush Build System
|
||||
|
||||
This build systems was originally inherited from Bitcoin and now has various
|
||||
customatizations inherited from Zcash and Komodo, with our own additional changes.
|
||||
|
||||
This is a system of building and caching dependencies necessary for building Hush.
|
||||
There are several features that make it different from most similar systems:
|
||||
|
||||
### It is designed to be builder and host agnostic
|
||||
@@ -6,7 +11,7 @@ There are several features that make it different from most similar systems:
|
||||
In theory, binaries for any target OS/architecture can be created, from a
|
||||
builder running any OS/architecture. In practice, build-side tools must be
|
||||
specified when the defaults don't fit, and packages must be amended to work
|
||||
on new hosts. For now, a build architecture of x86_64 is assumed, either on
|
||||
on new hosts. For now, a build architecture of `x86_64` is assumed, either on
|
||||
Linux or OSX.
|
||||
|
||||
### No reliance on timestamps
|
||||
|
||||
Reference in New Issue
Block a user