diff options
| author | kali kaneko (leap communications) <kali@leap.se> | 2022-08-16 12:01:04 +0200 |
|---|---|---|
| committer | kali kaneko (leap communications) <kali@leap.se> | 2022-08-16 12:01:04 +0200 |
| commit | 64224bbf2df8ef1229ccc592660be9c200a1d808 (patch) | |
| tree | 64448b70847b55a0c476f7737caf30b61704c0f6 | |
| parent | 505316ad1a11df2bf69d2baf26139e54e7a403fa (diff) | |
[docs] win build tips
| -rw-r--r-- | docs/build-win.rst | 14 |
1 files changed, 11 insertions, 3 deletions
diff --git a/docs/build-win.rst b/docs/build-win.rst index 147e1e3..261767a 100644 --- a/docs/build-win.rst +++ b/docs/build-win.rst @@ -2,21 +2,28 @@ 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). +It's recommended to use bash for windows for compatibility (the version that is distributed with git works well so far). 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`:: +It is useful to source a file with all the needed environment variables:: + + cat ../build-env export PATH="/c/Qt/Qt5/bin/":"/c/Qt/QtIFW-3.2.2/bin":$PATH export WINCERTPASS=certificatepass export VENDOR_PATH=providers export PROVIDER=riseup + +Assuming you have the vendor path in place and correctly configured, all you need to do is `make installer`:: + + source ../build-env make generate # not called by makefile in win, needs fix!! make vendor @@ -24,6 +31,7 @@ Assuming you have the vendor path in place and correctly configured, all you nee make installer + checking signatures ------------------- we should be signing all binaries on a release build. @@ -54,7 +62,7 @@ or all together as:: make package_win_release -make sure to cleanup the build/ and lib/ dirs if you're buildingb for more than +Please make sure to cleanup the build/ and lib/ dirs if you're building for more than one vendor. Uploading installer |