diff options
| author | kali kaneko (leap communications) <kali@leap.se> | 2021-03-05 12:35:45 +0100 |
|---|---|---|
| committer | kali kaneko (leap communications) <kali@leap.se> | 2021-03-05 12:35:45 +0100 |
| commit | 9d9da92cb0ce64600664a24a6b7b07f2edba51eb (patch) | |
| tree | 4d98b95212626360b5f811d54ed3702ab68871ab /docs/build.windows.rst | |
| parent | 5c4a4b792a4c724e5cdeeebb854868b8ee1c4cfd (diff) | |
[docs] rename docs for coherence
Diffstat (limited to 'docs/build.windows.rst')
| -rw-r--r-- | docs/build.windows.rst | 57 |
1 files changed, 0 insertions, 57 deletions
diff --git a/docs/build.windows.rst b/docs/build.windows.rst deleted file mode 100644 index 1e65c27..0000000 --- a/docs/build.windows.rst +++ /dev/null @@ -1,57 +0,0 @@ -windows build -============= - -The build currently expects MINGW64 environment, on a native windows host. -A cross-compiling procedure (at least for the application binaries) should be possible in the near future, using mxe. (There's already some support for it in `gui/build.sh`). - -You should instal: make, wget, as well as a recent Qt5 version (for instance, with chocolatey: choco install make && choco install wget). - -(In order to avoid makefiles, you are welcome to submit a port of the build scripts using powershell or cscript - see the build.wsf script in openvpn-build for inspiration). - -For the installer, install QtIFW for windows (tested with version 3.2.2). - -Assuming you have the vendor path in place and correctly configured, all you need to do is `make installer`:: - - export PATH="/c/Qt/Qt5/bin/":"/c/Qt/QtIFW-3.2.2/bin":$PATH - export VENDOR_PATH=providers - export PROVIDER=riseup - make generate # FIXME this is not called in win - make vendor && make installer - -If you're doing a final release:: - - export RELEASE=yes - - -checking signatures -------------------- -we should be signing all binaries on a release build. - -to check the binaries have proper signatures, you can use the sigcheck -utilities, part of the sysinternals suite: - -https://docs.microsoft.com/en-us/sysinternals/downloads/sysinternals-suite - -unzip and place sigcheck.exe somewhere in your path. - -make sure to pass -accepteula parameter on some manual run so that it does not -ask again. - -adding metadata to binaries ---------------------------- - -the steps to do release signatures are:: - - make build - make dosign - make installer - make sign_installer - -or all together as:: - - make package_win_release - - -unreviewed notes ----------------- -see comment about patching dlls and windeployqt not being needed anymore https://stackoverflow.com/a/61910592 |