forked from cheng/wallet
246ff54e6c
preparatory to making it actually accessible
46 lines
1.5 KiB
Markdown
46 lines
1.5 KiB
Markdown
---
|
||
title: Download and build on windows
|
||
...
|
||
You will need an up to date edition of Visual Studio, Git-Bash for
|
||
windows, and Pandoc
|
||
|
||
In a Git bash command prompt, `cd` to the directory where you intend to
|
||
install the source code.
|
||
|
||
```bash
|
||
git clone --recursive git@cpal.pw:~/wallet
|
||
```
|
||
|
||
Then launch the visual studio X64 native tools command prompt. `cd` to the
|
||
wallet directory that was just created
|
||
|
||
```DOS
|
||
winConfigure
|
||
```
|
||
|
||
If all goes well, `winConfigure.bat` will call `"%ProgramFiles%"\Git\git-bash winConfigure.sh`
|
||
to launch `winConfigure.sh` in the bash command prompt,
|
||
`winConfigure.sh` will configure the libraries to be built, then
|
||
`winConfigure.bat` will call `msbuild`, which is Microsoft’s equivalent to
|
||
`make` on steroids, `msbuild` will then build the libraries, and finally build
|
||
and launch the wallet with the unit test flag set to perform and display the
|
||
unit test. To rebuild the wallet after you have changed something, use
|
||
Visual Studio.
|
||
|
||
To rebuild the html files after changing the markdown files, call the bash
|
||
script `mkdocs.sh`, which calls Pandoc.
|
||
|
||
If something goes wrong, and it is not obvious what went wrong, go back
|
||
to the git-bash command prompt and try `./winConfigure.sh`
|
||
|
||
Pandoc needs to be available from the git-bash command prompt to build
|
||
html documentation from the markdown documentation. It gets called
|
||
from `mkdocs.sh`. It normally is available if you have installed Pandoc.
|
||
|
||
Git-bash needs to be available from native tools command prompt. If
|
||
installed, it normally is as
|
||
|
||
```DOS
|
||
"%ProgramFiles%"\Git\git-bash
|
||
```
|