--- a/hugo/content/building/2.x.y/windows.md Tue Sep 03 22:42:40 2019 -0500
+++ b/hugo/content/building/2.x.y/windows.md Tue Sep 03 22:43:07 2019 -0500
@@ -1,16 +1,22 @@
-date: 2019-09-02T20:44:14-05:00+date: 2019-09-04T02:46:13.000Z + - developer.pidgin.im/wiki/BuildingWinPidgin + - developer.pidgin.im/wiki/BuildingWinPidgin/Pre2.7.0 +lastmod: 2019-09-04T02:55:05.000Z -Note: These instructions are kept current for the development version of `release-2.x.y` branch of Pidgin. You may need to look at an older version of this page in order to build a released version of Pidgin. Alternatively, you may need the instructions for 3.0.0 branch.+Note: These instructions are kept current for the development version of +`release-2.x.y` branch of Pidgin. You may need to look at an older version of +this page in order to build a released version of Pidgin. Alternatively, you +may need the instructions for 3.0.0 branch. ## Set up your build environment
-The Pidgin build system requires a full UNIX shell to run. You can install+The Pidgin build system requires a full Unix shell to run. You can install [Cygwin](https://cygwin.com) or [MSYS2](https://www.msys2.org/) to accomplish
this. However, these instructions are heavily geared towards Cygwin so MSYS
steps may be different and/or missing all together.
@@ -82,12 +88,12 @@
against a development version of a library dependency or to override compiler
-This done is by overriding the various Makefile variables in a `local.mak`+This is done by overriding the various Makefile variables in a `local.mak` file in the `$PIDGIN_DEV_ROOT/pidgin-<version>` directory. This file does not
-Most of the variables that can be overridden with this method are defined in-the [libpurple/win32/global.mak](https://{{< repo pidgin >}}src/release-2.x.y/libpurple/win32/global.mak)+The variables that can be overridden with this method are defined in the +[libpurple/win32/global.mak](https://{{< repo pidgin >}}src/release-2.x.y/libpurple/win32/global.mak) file. For example, to install Pidgin over `c:\Program Files\Pidgin` instead
of `$PIDGIN_DEV_ROOT/pidgin/win32-install-dir`, create a
`$PIDGIN_DEV_ROOT/pidgin/local.mak` containing:
@@ -103,7 +109,9 @@
## Get the Pidgin source code
-The development source is available via mercurial in the `release-2.x.y` branch. See [wiki:UsingPidginMercurial] for more information.+The development source is available via Mercurial in the `release-2.x.y` +branch. See [version control](/development/version-control/) for more If you want to build a release tarball, the instructions in the rest of this
document should work for you, however they are written for the most recent
@@ -119,8 +127,7 @@
Install the MinGW "GCC Version 4.7.2" packages from the
[MinGW site](https://www.mingw.org) by following
-[their instructions](https://www.mingw.org/node/24/revisions/908/view their+[their instructions](https://www.mingw.org/node/24/revisions/908/view). @@ -141,7 +148,8 @@
* [gcc-4.7.2-1-mingw32-src](https://sourceforge.net/projects/mingw/files/MinGW/Base/gcc/Version4/gcc-4.7.2-1/gcc-4.7.2-1-mingw32-src.tar.lzma/download)
* so we can distribute the libssp source since we distribute the binary
-Extract all of the above into the desired location (e.g. `$PIDGIN_DEV_ROOT/win32-dev/mingw-4.7.2`)+Extract all of the above into the desired location (e.g. +`$PIDGIN_DEV_ROOT/win32-dev/mingw-4.7.2`) Prepare a `libssp-src.tar.gz` file containing the libssp sources and licenses:
@@ -153,10 +161,10 @@
-Finally, Set the MinGW gcc's bin directory to be before Cygwin's in your+Finally, set the MinGW gcc's bin directory to be before Cygwin's in your -For Example (You should add the following to your `~/.bashrc` file, which is+For example (You should add the following to your `~/.bashrc` file, which is found in `C:\cygwin\home\YourUsername\` by default):
@@ -168,7 +176,7 @@
Pidgin depends on GTK 2.14.7 (newer runtime versions can be used). The GTK
-All-in-one bundle contains all of GTK+'s dependencies in one zip file. Download+All-in-one bundle contains all of GTK's dependencies in one zip file. Download [gtk+-bundle_2.14.7-20090119_win32.zip](https://ftp.gnome.org/pub/gnome/binaries/win32/gtk+/2.14/gtk+-bundle_2.14.7-20090119_win32.zip)
and extract to `$PIDGIN_DEV_ROOT/win32-dev/gtk_2_0-2.14` (you'll need to create
@@ -180,7 +188,8 @@
You'll need gettext to compile translations. Download
[gettext-tools-0.17.zip](https://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/gettext-tools-0.17.zip)
-and [gettext-runtime-0.17-1.zip](https://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/gettext-runtime-0.17-1.zip).+[gettext-runtime-0.17-1.zip](https://ftp.gnome.org/pub/gnome/binaries/win32/dependencies/gettext-runtime-0.17-1.zip). Extract both to `$PIDGIN_DEV_ROOT/win32-dev/gettext-0.17` (you'll need to
@@ -197,7 +206,8 @@
`pidgin/local.mak` to point to the appropriate perl executable). A good option
is [Strawberry Perl](https://strawberryperl.com/).
-Download the [perl-5.20.1.1.tar.gz](https://data.imfreedom.org/pidgin/win32/perl-5.20.1.1.tar.gz)+[perl-5.20.1.1.tar.gz](https://data.imfreedom.org/pidgin/win32/perl-5.20.1.1.tar.gz) development package and extract to `$PIDGIN_DEV_ROOT/win32-dev` (it creates its
own directory). This is a subset of the full 32-bit strawberry perl zip
containing just the headers, import lib, and source for perl.
@@ -226,7 +236,8 @@
[nss-3.24-nspr-4.12.tar.gz](https://data.imfreedom.org/pidgin/win32/nss-3.24-nspr-4.12.tar.gz)
under `$PIDGIN_DEV_ROOT/win32-dev`.
-**NOTE** NSS/NSPR are built from the upstream sources using [wiki:BuildingWinNSS these instructions].+**NOTE** NSS/NSPR are built from the upstream sources using +[these instructions](buildings-win-nss/). @@ -288,8 +299,8 @@
`$PIDGIN_DEV_ROOT/win32-dev/pidgin-inst-deps-20130214/SHA1Plugin.dll` into
the NSIS `Plugins` directory.
-Finally, you'll need to decide if you would like to sign the executables which-is not necessary for personal use.+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
@@ -299,7 +310,8 @@
as well as the `SIGNCODE_SPC` and `SIGNCODE_PVK` variable to the appropriate
files in your certificate.
-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 verify 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
@@ -351,10 +363,12 @@
It is quite easy to cross compile Pidgin for Windows on a Linux machine.
-To begin, you'll need to install MinGW. On Debian/Ubuntu, this involves installing packages `mingw32`, `mingw32-binutils`, and `mingw32-runtime`. On other distributions, the packages may be named differently.+To begin, you'll need to install MinGW. On Debian/Ubuntu, this involves +installing packages `mingw32`, `mingw32-binutils`, and `mingw32-runtime`. On +other distributions, the packages may be named differently. Set up a build environment as described [above](set-up-your-build-environment).
-Obviously, you already have a bash shell and have just installed the mingw+You should already have a bash shell and have just installed the mingw Create a `local.mak` file in the source directory root to override the
