Changes between Version 9 and Version 10 of BuildingWinPidgin

Timestamp:

May 14, 2007, 3:32:46 PM (17 years ago)

Author:

datallah

Comment:

Use "$PIDGIN_DEV_ROOT" instead of "~" to prevent confusion, Add note about not using paths with spaces.

BuildingWinPidgin

@@ -25 +25 @@
      Specifically, you will need `gcc-core 3.4.2`, `binutils 2.15.91`, `mingw-runtime 3.9` and `win32api 3.9` (or newer). Note that a bug with the MinGW site causes win32api 3.9 to not appear. You'll need to grab it from their [http://sourceforge.net/project/showfiles.php?group_id=2435 Sourceforge page].[[BR]]
      You will need to set MinGW's bin directory before Cygwin's in your PATH.[[BR]]
-     For Example (You can add the following to `~/.bash_login`):
+     For Example (You can add the following to your `~/.bashrc` file (create the file if it doesn't exist yet)):
 {{{
   export PATH=/cygdrive/c/MinGW/bin:$PATH
@@ -31 +31 @@
      You do not want to use any of Cygwin's build tools, with one exception; you need to use Cygwin's make utility. If typing `which make` produces MinGW's make utility, then just rename the `make.exe` in the MinGW bin directory to something else so that cygwin's make utility will be used instead. This shouldn't be a problem with recent versions of MinGW.
 
-  3. The following instructions were written under the assumption that you checkout Pidgin from monotone to `~/pidgin` and that you install all of Pidgin's build dependencies under `~/win32-dev` (the point being that the pidgin source root and `win32-dev` directories should be on the same level).[[BR]]
-     This can be overridden by creating a `local.mak` file in the `~/pidgin` directory and overriding the various Makefile variables.[[BR]]
-     People are sometimes confused about the directory structure, so here is an example:
+  3. The following instructions were written under the assumption that you checkout Pidgin from monotone to `$PIDGIN_DEV_ROOT/pidgin` and that you install all of Pidgin's build dependencies under `$PIDGIN_DEV_ROOT/win32-dev` (the point being that the pidgin source root and `win32-dev` directories should be on the same level).[[BR]]
+     This can be overridden by creating a `local.mak` file in the `$PIDGIN_DEV_ROOT/pidgin` directory and overriding the various Makefile variables.[[BR]]
+     People are sometimes confused about the directory structure, so here is an example (`$PIDGIN_DEV_ROOT` is `c:/development` in this example):
 {{{
 C:\development\pidgin_dev
@@ -42 +42 @@
 C:\development\pidgin_dev\win32-dev\gtk_2_0\include\libintl.h
 }}}
-     [[BR]]**TODO: post example local.mak
+     ** Note: You should avoid using a `$PIDGIN_DEV_ROOT` path that contains spaces as that can cause unnecessary complications.
+     [[BR]]** TODO: post example local.mak
 
 == Install Pidgin's build dependencies ==
@@ -50 +51 @@
   Pidgin depends on GTK+ 2.6.10 (newer runtime versions can be used, but building against newer headers will prevent Win98/ME compatibility).
   For your convenience, we have included all of GTK's dependencies in one tarball.
-  Extract [http://prdownloads.sourceforge.net/pidgin/gtk-dev-2.6.10-rev-a.tar.gz?download gtk-dev-2.6.10-rev-a.tar.gz] within `~/win32-dev`.[[BR]]
+  Extract [http://prdownloads.sourceforge.net/pidgin/gtk-dev-2.6.10-rev-a.tar.gz?download gtk-dev-2.6.10-rev-a.tar.gz] within `$PIDGIN_DEV_ROOT/win32-dev`.[[BR]]
   If you wish to run Pidgin from the `win32-install-dir` directory once it is built, you will need to make sure that you have installed the GTK+ runtime, and make sure that its bin dir is in your PATH.[[BR]]
   Visit the [http://www.gtk.org GTK+ website] for official binary and source releases.
@@ -60 +61 @@
   Install Perl 5.8 for Windows (I use [http://www.activestate.com/Products/ActivePerl/ ActivePerl]), to `C:\Perl`.
   If you install Perl anywhere else, you will need to override the `PERL` and `EXTUTILS` variables in your `pidgin/local.mak` file.
-  You will also need to install [/static/win32/perl582.tar.gz perl582.tar.gz] under `~/win32-dev` (Containing headers and import lib for mingw gcc).
+  You will also need to install [/static/win32/perl582.tar.gz perl582.tar.gz] under `$PIDGIN_DEV_ROOT/win32-dev` (Containing headers and import lib for mingw gcc).
 
 === Tcl 8.4.5 ===
@@ -71 +72 @@
 
 === Mozilla NSS ===
-  * Download and unzip the following under `~/win32-dev` (make sure you `chmod 755` all the unzipped binaries):
+  * Download and unzip the following under `$PIDGIN_DEV_ROOT/win32-dev` (make sure you `chmod 755` all the unzipped binaries):
     * [ftp://ftp.mozilla.org/pub/mozilla.org/security/nss/releases/NSS_3_11_4_RTM/msvc6.0/WIN954.0_OPT.OBJ/nss-3.11.4.zip Network Security Services (NSS)]
     * [ftp://ftp.mozilla.org/pub/mozilla.org/nspr/releases/v4.6.4/msvc6.0/WIN954.0_OPT.OBJ/nspr-4.6.4.zip Netscape Portable Runtime (NSPR)]
@@ -88 +89 @@
   Run the following:
 {{{
-$ cd ~/pidgin
+$ cd $PIDGIN_DEV_ROOT/pidgin
 $ make -f Makefile.mingw install
 }}}
-  Now just wait and let your compiler do its thing.  When finished, Pidgin will be in `~/pidgin/win32-install-dir`.
+  Now just wait and let your compiler do its thing.  When finished, Pidgin will be in `$PIDGIN_DEV_ROOT/pidgin/win32-install-dir`.
 
 == Build the Pidgin Installer ==
@@ -99 +100 @@
       For information on the NSIS installer, visit the [http://nsis.sourceforge.net NSIS website].
     * Download [http://prdownloads.sourceforge.net/pidgin/gtk-2.10.11-rev-b-installer.tar.gz?download gtk-2.10.11-rev-b-installer.tar.gz]
-      and extract it to `~/` (or whichever directory you have the pidgin dir in). From within the new `gtk_installer directory`, run `. build.sh` (this builds the GTK+ runtime installer, which the Pidgin installer will include).
-    * Download [/static/win32/pidgin-inst-deps.tar.gz pidgin-inst-deps.tar.gz] and extract under `~/win32-dev`.
+      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).
+    * Download [/static/win32/pidgin-inst-deps.tar.gz pidgin-inst-deps.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
+$ cd $PIDGIN_DEV_ROOT/pidgin
 $ make -f Makefile.mingw installers
 }}}