Changes between Version 8 and Version 9 of BuildingWinPidgin/3.0.0

Timestamp:

Sep 25, 2016, 9:45:20 PM (7 years ago)

Author:

Maiku

Comment:

Update Windows build instructions for modern Pidgin 3

BuildingWinPidgin/3.0.0

@@ -15 +15 @@
   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`, `mingw32-runtime`, `mingw32-cross-pkg-config`. On other distributions, the packages may be named differently.
+  '''''Until it's merged, this guide relies on the branch from [https://bitbucket.org/pidgin/main/pull-requests/136/windows-build-fixes/diff PR 136]'''''
 
-  When compiling from hg, you'll need to generate `configure` script:
+  To begin, you'll need to install MinGW. On !Debian/Ubuntu, this involves installing packages `mingw-w64` and `mingw-w64-tools`. On other distributions, the packages may be named differently.
+
+  Next, you need to set up a MinGW development directory and populate it with all of the Pidgin dependencies. Start by defining that in an environment variable. The exactly location can be changed to fit your filesystem:
+{{{
+export WIN_DEV_DIR=${HOME}/win32-dev/
+}}}
+
+  Actually fetch the dependencies using the [https://bitbucket.org/snippets/CMaiku/pon5L/pidgin-for-windows-bootstrap-script bootstrap script]:
+{{{
+wget -nv -P"$WIN_DEV_DIR" "https://bitbucket.org/%21api/2.0/snippets/CMaiku/pon5L/9318f8fcc219fb123174a2a777a1c58a1da8ba3f/files/pidgin-bootstrap.sh"
+chmod +x "${WIN_DEV_DIR}/pidgin-bootstrap.sh"
+${WIN_DEV_DIR}/pidgin-bootstrap.sh
+}}}
+
+  When compiling from hg, you'll need to generate a `configure` script:
 {{{
 NOCONFIGURE=indeed ./autogen.sh
@@ -24 +38 @@
   Set up pkgconfig (this may vary, depending on Linux distribution):
 {{{
-export PKG_CONFIG_PATH=/usr/i686-w64-mingw32/sys-root/mingw/lib/pkgconfig:\
-                       /usr/i686-w64-mingw32/sys-root/mingw/share/pkgconfig
-export PKG_CONFIG=/usr/bin/i686-w64-mingw32-pkg-config
+export PKG_CONFIG="/usr/bin/i686-w64-mingw32-pkg-config --define-prefix=${WIN_DEV_DIR}"
+export PKG_CONFIG_PATH="${WIN_DEV_DIR}/lib/pkgconfig"
 }}}
 
-  Run configure with cross-compile option. You may choose FHS or classic directory layout (default is classic). For now (when installer is missing), FHS will be easier to install and run. Then - build it.
+  Run configure with the cross-compile option. You may choose FHS or classic directory layout (default is classic). For now (when installer is missing), FHS will be easier to install and run. The rest of this script assumes you're using FHS. The actual compiler used in the CC environment variable may vary depending on Linux distribution. Unfortunately this override is needed to bypass an [http://mingw.org/wiki/HOWTO_Sneak_GCC_Switches_Past_Libtool issue with libtool].
 {{{
-./configure --host=i686-w64-mingw32 --with-win32-dirs=<fhs|classic>
+CC="i686-w64-mingw32-gcc -static-libgcc" ./configure --host=i686-w64-mingw32 --with-win32-dirs=<fhs|classic> --disable-vv --prefix=/ CFLAGS="-I${WIN_DEV_DIR}/include/"
+}}}
+
+  Then build it.
+{{{
 make
 }}}
 
-  At last, install Pidgin, Finch and its dependencies.
+  At last, install Pidgin, Finch and its dependencies. It can be installed anywhere, but it needs dependencies which are, according to this guide, already in `${WIN_DEV_DIR}`. So for simplicity, this guide installs it there.
 {{{
-make DESTDIR=/path/to/install-dir install
-cd /path/to/install-dir
-cd usr/local # it may depend on your configured $prefix
-wget https://pidgin.im/~twasilczyk/win32/gtk-runtime-2.24.18.0.zip
-unzip gtk-runtime-2.24.18.0.zip
-cp -r Gtk/* .
-rm -rf Gtk gtk-runtime-2.24.18.0.zip
+make DESTDIR=${WIN_DEV_DIR} install
 }}}
 
+  Now you're done. `${WIN_DEV_DIR}` can be copied to a Windows machine and run as is (`${WIN_DEV_DIR}/bin/pidgin.exe`). However, see below regarding TLS certificates.
+
+=== TLS Certificates ===
+  Pidgin 3 uses Gio for its TLS certificates, which by default uses Certificate Authorities from `${WIN_DEV_DIR}/ssl/certs/ca-bundle.crt`. Because of the way the dependencies are fetched, currently this file is empty. There are three methods to resolve this:
+
+  Populate the file by running p11-kit from the cross compiling host:
+{{{
+p11-kit extract --format=pem-bundle --filter=ca-anchors --overwrite --purpose server-auth ${WIN_DEV_DIR}/ssl/certs/ca-bundle.crt
+}}}
+
+  OR run it from Windows (run from `${WIN_DEV_DIR}`):
+{{{
+bin\p11-kit.exe extract --format=pem-bundle --filter=ca-anchors --overwrite --purpose server-auth ssl\certs\ca-bundle.crt
+}}}
+
+  OR bypass the file and use the alternate Gio TLS Backend by setting the environment variable:
+{{{
+set GIO_USE_TLS=gnutls-pkcs11
+}}}
 
 == Compiling directly on Windows with Cygwin (the hard way) ==