Windows: make builds easier by using a matching dir structure
Now the entire distro/windows/ dir contents can be copied into a staging dir during release prep. Signed-off-by: Josh Cepek <josh.cepek@usa.net>
This commit is contained in:
parent
dc2e6dc7dc
commit
d5516d5f5d
@ -34,14 +34,9 @@ Windows Build Extras
|
|||||||
Windows has additional build steps to provide a suitable POSIX environment.
|
Windows has additional build steps to provide a suitable POSIX environment.
|
||||||
Starting with a basic build dir from earlier, proceed as follows.
|
Starting with a basic build dir from earlier, proceed as follows.
|
||||||
|
|
||||||
1. Copy the following files/dirs into the target dir. Unless specified, all
|
1. Copy everything from `distro/windows/` into the target dir root. Make sure
|
||||||
source files or referenced dirs go into the root of the target dir. Take care
|
that text files follow the Windows EOL convention (CR+LF) -- a git checkout
|
||||||
that txt/bat files follow Windows EOL convention (CR+LF.)
|
of the source project on Windows generally does this for you already.
|
||||||
|
|
||||||
* `distro/windows/EasyRSA Start.bat`
|
|
||||||
* `distro/windows/doc/README-Windows.txt`
|
|
||||||
* `distro/windows/bin/`
|
|
||||||
* `distro/windows/Licensing/`
|
|
||||||
|
|
||||||
2. Convert the .md readme/doc files into html for easier viewing by Windows
|
2. Convert the .md readme/doc files into html for easier viewing by Windows
|
||||||
clients. One option using the python3 `markdown` module is:
|
clients. One option using the python3 `markdown` module is:
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user