Changes between Version 71 and Version 72 of BuildingWinPidgin

Timestamp:

Feb 24, 2010, 6:38:29 PM (14 years ago)

Author:

datallah

Comment:

Move NSIS compilation instructions into the cross-compiling section

BuildingWinPidgin

@@ -112 +112 @@
   * If you want to build the Pidgin installer, do the following (skip to the `make` command below if you chose to use the Build Environment Fetcher):
     * Download and install [http://nsis.sourceforge.net/Download NSIS]. Include NSIS to your PATH.
-      For information on the NSIS installer, visit the [http://nsis.sourceforge.net NSIS website].[[BR]]
+     *  For information on the NSIS installer, visit the [http://nsis.sourceforge.net NSIS website].[[BR]]
+    * Download [http://prdownloads.sourceforge.net/pidgin/gtk-2.14.7-rev-a-installer.tar.gz?download gtk-2.14.7-rev-a-installer.tar.gz]
+      and extract it to `$PIDGIN_DEV_ROOT/`. From within the new `gtk_installer directory`, run `. build.sh` (this builds the GTK+ runtime installer, which the Pidgin installer will include). **Please see [#CrossCompiling note below] if building on Ubuntu/Debian about modification of the build.sh file.
+    * Download [/static/win32/pidgin-inst-deps-20100223.tar.gz pidgin-inst-deps-20100223.tar.gz] and extract under `$PIDGIN_DEV_ROOT/win32-dev`.
+  * Now you can actually build the installer.[[BR]]
+    There are 3 different installers: "Normal" (with GTK+), "No GTK+" and "Debug".
+    The Makefile targets for these are `installer`, `installer_nogtk`, and `installer_debug` respectively.  To build all 3, use the `installers` target.
+{{{
+$ cd $PIDGIN_DEV_ROOT/pidgin-<version>
+$ make -f Makefile.mingw installers
+}}}
+    When it finishes, your installer(s) should be in `$PIDGIN_DEV_ROOT/pidgin-<version>/`.
+
+== Customizing the Build Environment ==
+  Most people will find that the standard build evironment directory is completely adequate.
+  It is, however, possible to override the locations of the various dependencies and target directories.
+  This is often useful to test against a development version of a library dependency or to override compiler flags.
+
+  This done is by overridding the various Makefile variables in a `local.mak` file in the `$PIDGIN_DEV_ROOT/pidgin-<version>` directory.
+  This file does not exist by default.
+
+  Most of the variables that can be overridden with this method are defined in the [/viewmtn/revision/file/8c0ef1cb63204eeb0e5cda5501300c62d11bf89e/libpurple/win32/global.mak 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:
+{{{
+ #Override the install location
+ PIDGIN_INSTALL_DIR = /cygdrive/c/Program\ Files/Pidgin
+ PURPLE_INSTALL_DIR = /cygdrive/c/Program\ Files/Pidgin
+}}}
+
+  One nice use of the `local.mak` file is for cross compiling, there is an additional example in the [#CrossCompiling section below]. 
+
+== Debugging ==
+  There is a quite good '''Just In Time''' debugger for MinGW: [http://jrfonseca.planetaclix.pt/projects/gnu-win32/software/drmingw/index.html drmingw].
+  You can download it [/static/win32/drmingw.exe here].[[BR]]
+  There is also a version of `gdb` available from MinGW, if you prefer.
+
+== Cross Compiling ==
+  It is quite easy to cross compile Pidgin for Windows on a Linux machine.  Note that cross-compiling does '''''not''''' work properly on Debian Sid on amd64 (also called x86_64 or x64) systems--the most common failure is that the linker will die with a segmentation fault at various points.  You may have differing success or failure on other 64-bit Linux distributions.
+
+  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 [#Themanualway above], skipping steps 1 and 2.
+
+  Create a `local.mak` file in the source directory root to override the Makefile variables - mine looks like this:
+{{{
+SHELL := /bin/bash
+CC := /usr/bin/i586-mingw32msvc-cc
+GMSGFMT := msgfmt
+MAKENSIS := /usr/bin/makensis
+MAKENSISOPT := -
+PERL := /usr/bin/perl
+EXTUTILS := /usr/share/perl/5.8/ExtUtils
+WINDRES := /usr/bin/i586-mingw32msvc-windres
+STRIP := /usr/bin/i586-mingw32msvc-strip
+
+INCLUDE_PATHS := -I$(PIDGIN_TREE_TOP)/../win32-dev/w32api/include
+LIB_PATHS := -L$(PIDGIN_TREE_TOP)/../win32-dev/w32api/lib
+}}}
+
+  If your distribution doesn't include a recent enough win32api, you can download it from the [http://www.mingw.org/ MinGW site], extract it into your `win32-dev` directory, and override the `INCLUDE_PATHS` and `LIB_PATHS` variables in your `local.mak` as I have done.
+
+  If you want to build the installers, you'll need to install [#BuildthePidginInstaller NSIS].  On Debian and Ubuntu, the package name is `nsis`; this will likely be different elsewhere.  In order to build the GTK+ installer as mentioned above, the `build.sh` script referenced above needs to be changed.  The line starting with `makensis.exe` needs to be changed to read:
+{{{
+makensis -V3 -DGTK_VERSION=$gtk_version -DGTK_REVISION=$gtk_revision gtk-installer.nsi
+}}}
+
       NSIS version 2.46 or greater is required to cross-compile.  If compiling NSIS from source, the [http://www.scons.org/ scons] package is a dependency.  This can usually be installed through your linux distribution's package archive.  An example of how to install the NSIS package is given below (Assuming use of the NSIS 2.46 version):
 
-
-
-      .tar.bz2 file contains latest source[[BR]]
-      .zip file contains libraries
+      `.tar.bz2` file contains latest source[[BR]]
+      `.zip` file contains libraries
 {{{
 $ mkdir nsis;cd nsis
@@ -134 +197 @@
       MAKENSIS := /usr/local/bin/makensis  
 
-    * Download [http://prdownloads.sourceforge.net/pidgin/gtk-2.14.7-rev-a-installer.tar.gz?download gtk-2.14.7-rev-a-installer.tar.gz]
-      and extract it to `$PIDGIN_DEV_ROOT/`. From within the new `gtk_installer directory`, run `. build.sh` (this builds the GTK+ runtime installer, which the Pidgin installer will include). **Please see [#CrossCompiling note below] if building on Ubuntu/Debian about modification of the build.sh file.
-    * Download [/static/win32/pidgin-inst-deps-20100223.tar.gz pidgin-inst-deps-20100223.tar.gz] and extract under `$PIDGIN_DEV_ROOT/win32-dev`.
-  * Now you can actually build the installer.[[BR]]
-    There are 3 different installers: "Normal" (with GTK+), "No GTK+" and "Debug".
-    The Makefile targets for these are `installer`, `installer_nogtk`, and `installer_debug` respectively.  To build all 3, use the `installers` target.
-{{{
-$ cd $PIDGIN_DEV_ROOT/pidgin-<version>
-$ make -f Makefile.mingw installers
-}}}
-    When it finishes, your installer(s) should be in `$PIDGIN_DEV_ROOT/pidgin-<version>/`.
-
-== Customizing the Build Environment ==
-  Most people will find that the standard build evironment directory is completely adequate.
-  It is, however, possible to override the locations of the various dependencies and target directories.
-  This is often useful to test against a development version of a library dependency or to override compiler flags.
-
-  This done is by overridding the various Makefile variables in a `local.mak` file in the `$PIDGIN_DEV_ROOT/pidgin-<version>` directory.
-  This file does not exist by default.
-
-  Most of the variables that can be overridden with this method are defined in the [/viewmtn/revision/file/8c0ef1cb63204eeb0e5cda5501300c62d11bf89e/libpurple/win32/global.mak 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:
-{{{
- #Override the install location
- PIDGIN_INSTALL_DIR = /cygdrive/c/Program\ Files/Pidgin
- PURPLE_INSTALL_DIR = /cygdrive/c/Program\ Files/Pidgin
-}}}
-
-  One nice use of the `local.mak` file is for cross compiling, there is an additional example in the [#CrossCompiling section below]. 
-
-== Debugging ==
-  There is a quite good '''Just In Time''' debugger for MinGW: [http://jrfonseca.planetaclix.pt/projects/gnu-win32/software/drmingw/index.html drmingw].
-  You can download it [/static/win32/drmingw.exe here].[[BR]]
-  There is also a version of `gdb` available from MinGW, if you prefer.
-
-== Cross Compiling ==
-  It is quite easy to cross compile Pidgin for Windows on a Linux machine.  Note that cross-compiling does '''''not''''' work properly on Debian Sid on amd64 (also called x86_64 or x64) systems--the most common failure is that the linker will die with a segmentation fault at various points.  You may have differing success or failure on other 64-bit Linux distributions.
-
-  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 [#Themanualway above], skipping steps 1 and 2.
-
-  Create a `local.mak` file in the source directory root to override the Makefile variables - mine looks like this:
-{{{
-SHELL := /bin/bash
-CC := /usr/bin/i586-mingw32msvc-cc
-GMSGFMT := msgfmt
-MAKENSIS := /usr/bin/makensis
-MAKENSISOPT := -
-PERL := /usr/bin/perl
-EXTUTILS := /usr/share/perl/5.8/ExtUtils
-WINDRES := /usr/bin/i586-mingw32msvc-windres
-STRIP := /usr/bin/i586-mingw32msvc-strip
-
-INCLUDE_PATHS := -I$(PIDGIN_TREE_TOP)/../win32-dev/w32api/include
-LIB_PATHS := -L$(PIDGIN_TREE_TOP)/../win32-dev/w32api/lib
-}}}
-
-  If your distribution doesn't include a recent enough win32api, you can download it from the [http://www.mingw.org/ MinGW site], extract it into your `win32-dev` directory, and override the `INCLUDE_PATHS` and `LIB_PATHS` variables in your `local.mak` as I have done.
-
-  If you want to build the installers, you'll need to install [#BuildthePidginInstaller NSIS].  On Debian and Ubuntu, the package name is `nsis`; this will likely be different elsewhere.  In order to build the GTK+ installer as mentioned above, the `build.sh` script referenced above needs to be changed.  The line starting with `makensis.exe` needs to be changed to read:
-{{{
-makensis -V3 -DGTK_VERSION=$gtk_version -DGTK_REVISION=$gtk_revision gtk-installer.nsi
-}}}
 
   Once this is all set up, you should be able to follow the [#BuildPidgin building instructions above].