akovalenko/lnd.xprv
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

build/README: describe how to use make release

Browse Source
This commit is contained in:
Oliver Gugger 2020-04-21 10:20:29 +02:00
parent 317ccb2cc9
commit c08ddad22e
No known key found for this signature in database
GPG Key ID: 8E4256593F177720
1 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
build/release/README.md
View File

@ -19,8 +19,7 @@ the release binaries following these steps:
1. `git clone https://github.com/lightningnetwork/lnd.git` 1. `git clone https://github.com/lightningnetwork/lnd.git`
2. `cd lnd` 2. `cd lnd`
3. `./build/release/release.sh <TAG> # <TAG> is the name of the next 3. `make release tag=<TAG> # <TAG> is the name of the next release/tag`
release/tag`
This will then create a directory of the form `lnd-<TAG>` containing archives This will then create a directory of the form `lnd-<TAG>` containing archives
of the release binaries for each supported operating system and architecture, of the release binaries for each supported operating system and architecture,
@ -64,7 +63,7 @@ and `go` (matching the same version used in the release):
release with `git checkout <TAG>`. release with `git checkout <TAG>`.
7. Proceed to verify the tag with `git verify-tag <TAG>` and compile the 7. Proceed to verify the tag with `git verify-tag <TAG>` and compile the
binaries from source for the intended operating system and architecture with binaries from source for the intended operating system and architecture with
`LNDBUILDSYS=OS-ARCH ./build/release/release.sh <TAG>`. `make release sys=OS-ARCH tag=<TAG>`.
8. Extract the archive found in the `lnd-<TAG>` directory created by the 8. Extract the archive found in the `lnd-<TAG>` directory created by the
release script and recompute the `SHA256` hash of the release binaries (lnd release script and recompute the `SHA256` hash of the release binaries (lnd
and lncli) with `shasum -a 256 <filename>`. These should match __exactly__ and lncli) with `shasum -a 256 <filename>`. These should match __exactly__