pidgin/nest

Update how to build the installer

2 months ago, Gary Kramlich
9368cfdb3564
Parents b1b5ffddaf91
Children cd87c95d31ba
Update how to build the installer

* Added notes on how to install the nsis inetc plugin
* Updated signing to only include osslsigncode

Testing Done:
Ran locally via `npm run hugo:server`

Reviewed at https://reviews.imfreedom.org/r/594/
--- a/hugo/content/development/building/2.x.y/windows.md Fri Apr 02 23:57:54 2021 -0500
+++ b/hugo/content/development/building/2.x.y/windows.md Mon Apr 05 22:21:32 2021 -0500
@@ -288,39 +288,41 @@
If you would like to build the Pidgin installer, you'll need to setup
[NSIS](https://nsis.sourceforge.io/Download). Once you have installed
-NSIS, please make sure that it is in your shell's `PATH`.
+NSIS, please make sure that it is in your shell's `PATH`. Note if you're
+building with msys2 you can just run `pacman -S mingw-w64-i686-nsis` to
+install it.
Next you'll need to download the
-[nsisunz plugin](https://nsis.sourceforge.io/Nsisunz_plug-in),
-and extract `nsisunz.dll` into the `Plugins` directory of your NSIS
-installation.
-
-You'll also need to install the `SHA1Plugin` from
-`$PIDGIN_DEV_ROOT/win32-dev/pidgin-inst-deps-20130214/SHA1Plugin.dll` into
-the NSIS `Plugins` directory.
+[nsis inetc plugin](https://github.com/DigitalMediaServer/NSIS-INetC-plugin)
+and extract `x86-unicode/INetC.dll` to the `Plugins/unicode` directory of your
+NSIS installation.
Finally, you'll need to decide if you would like to sign the executables though
this is not necessary for personal use.
-To sign the executables, you'll need to get an appropriate code signing
-certificate by downloading and installing
-[Mono](https://www.mono-project.com/Download). In your `local.mak` file (see
-[customizing](#customizing) above), define the `MONO_SIGNCODE` variable to the
-fully qualified path to the `signcode` batch file in the Mono `bin` directory,
-as well as the `SIGNCODE_SPC` and `SIGNCODE_PVK` variable to the appropriate
-files in your certificate.
+To sign the executables, you need to get an appropriate code signing
+certificate and then install
+[osslsigncode](https://github.com/mtrojnar/osslsigncode). If you're using
+msys2 this can be installed with `pacman -S mingw-w64-i686-osslsigncode`.
+In your `local.mak` file (see [customizing](#customizing) above), define the
+`OSSLSIGNCODE` variable to the fully qualified path to the `signcode`
+executable. You'll also need to assign the `SIGNCODE_SPC` and
+`SIGNCODE_PVK` variables to the appropriate files in your certificate. If you
+just have a `pfx` file, you'll need to extract the certificate and key to the
+`spc` and `pvk` files. You can find documentation to do so
+[here](https://support.comodo.com/index.php?/comodo/Knowledgebase/Article/View/548/7/).
-Also, you'll need a PGP key to verify add pgp signatures to the files. GnuPG
-is the primary PGP client most people use. You can read more
+Also, you'll need a PGP key to add pgp signatures to the files. GnuPG is the
+primary PGP client most people use. You can read more
[here](https://www.gnupg.org/gph/en/manual/c14.html).
Once you have everything setup your `local.mak` should look something like the
following:
```
-MONO_SIGNCODE=/cygdrive/c/Program\ Files\ \(x86\)/Mono-2.10.8/bin/signcode
-SIGNCODE_SPC=c:\\Path\\to\\authenticode.spc
-SIGNCODE_PVK=c:\\Path\\to\\authenticode.pvk
+OSSLSIGNCODE=/mingw32/bin/osslsigncode.exe
+SIGNCODE_SPC=/home/user/sekrets/authenticode.spc
+SIGNCODE_PVK=/home/user/sekrets/authenticode.pvk
#Set up gpg to use a separate keyring
GPG_SIGN=gpg --no-default-keyring --secret-keyring /path/to/secring.gpg
```
@@ -330,7 +332,7 @@
```
#Disable Signing
-MONO_SIGNCODE=echo ***Bypassing signcode***
+OSSLSIGNCODE=echo ***Bypassing signcode***
GPG_SIGN=echo ***Bypassing gpg***
```