Changes between Version 11 and Version 12 of BuildingWinPidgin

Timestamp:

May 15, 2007, 8:03:32 PM (17 years ago)

Author:

phroggie

Comment:

monotone handles line endings better than CVS did, local.mak clarifications, better describe layout, and a pidgin in a tutu sounds utterly silly ;-)

BuildingWinPidgin

@@ -17 +17 @@
 === The manual way ===
 
-  1. Install the [http://cygwin.com Cygwin] Bash shell. Make sure to select Unix file mode during setup.
-     Also make sure you install bash, bzip2, coreutils, gawk, grep, gzip, make, patch, sed, monotone, tar, unzip, and wget (several of these are selected by default).[[BR]]
+  1. Install the [http://cygwin.com Cygwin] Bash shell.
+     Make sure you install bash, bzip2, coreutils, gawk, grep, gzip, make, patch, sed, monotone, tar, unzip, and wget (several of these are selected by default).[[BR]]
      You may prefer to use the native Windows monotone binary available [http://www.monotone.ca here].
 
@@ -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_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):
+  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). It is not required to actually define `$PIDGIN_DEV_ROOT`, it is simply mentioned here to show which parts of the process are up to your personal choice.[[BR]][[BR]]
+     ** Note: You should avoid using a `$PIDGIN_DEV_ROOT` path that contains spaces as that can cause unnecessary complications.[[BR]][[BR]]
+     The location of win32-dev and it's contents can be changed by creating a `local.mak` file in the `$PIDGIN_DEV_ROOT/pidgin` directory and overriding the various Makefile variables. While this is not necessary, it allows you the freedom to install dependencies wherever you please. The variables that can be overridden with this method are listed in the source archive in [http://developer.pidgin.im/viewmtn/revision/file/8c0ef1cb63204eeb0e5cda5501300c62d11bf89e/libpurple/win32/global.mak libpurple/win32/global.mak]. 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:
+{{{
+ PIDGIN_INSTALL_DIR = /cygdrive/c/Program\ Files/Pidgin
+ PURPLE_INSTALL_DIR = /cygdrive/c/Program\ Files/Pidgin
+}}}
+     People are sometimes confused about the directory structure, so here is an example that will build without any local.mak overrides (`$PIDGIN_DEV_ROOT` is `c:/development/pidgin_dev` in this example):
 {{{
 C:\development\pidgin_dev
-(The following is the source tree root, containing the config.h.mingw file.)
+(The following is the source tree root, containing config.h.mingw and libpurple.)
 C:\development\pidgin_dev\pidgin
 C:\development\pidgin_dev\win32-dev
@@ -42 +47 @@
 C:\development\pidgin_dev\win32-dev\gtk_2_0\include\libintl.h
 }}}
-     ** 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
+     Or, for those more graphically inclined (again using `c:/development/pidgin_dev` for `$PIDGIN_DEV_ROOT`):[[BR]]
+     [[Image(ticket:1017:build-layout.png)]]
 
 == Install Pidgin's build dependencies ==
@@ -83 +88 @@
 === Meanwhile ===
   Download and extract [http://prdownloads.sourceforge.net/meanwhile/meanwhile-1.0.2-win32.zip?download meanwhile-1.0.2-win32.zip] to `win32-dev`.
-
-=== Pidgin's build dependency folder structure example ===
-[[Image(ticket:1017:alldependencies.png)]]
 
 == Get the Pidgin source code ==
@@ -145 +147 @@
   Once this is set up, you should be able to follow the [#BuildPidgin building instructions above].
 
-  ** Note: I haven't been able to get the NSIS installer to to build correctly on my 64-bit Linux system.
+  ** Note: I haven't been able to get the NSIS installer to build correctly on my 64-bit Linux system.