[Pidgin] #1017: further explanation

[Pidgin]

#1017: further explanation
-----------------------+----------------------------------------------------
  Reporter:  tap52384  |       Owner:                        
      Type:  defect    |      Status:  new                   
  Priority:  minor     |   Milestone:                        
 Component:  webpage   |     Version:  2.0                   
Resolution:            |    Keywords:  build, pidgin, windows
   Pending:  0         |  
-----------------------+----------------------------------------------------
Comment (by phroggie):

 After posting this, I'll take a look at the BuildingWinPidgin page and see
 if there's any way to clarify the authors intentions. However, keep in
 mind that it is in fact a wiki, and everyone is more than welcome to
 contribute to it. After you've read my replies below, if you can think of
 a way to better clarify the instructions on that page, please do so.

 Replying to [ticket:1017 tap52384]:
 > ***do we need to create an environmental variable in Windows XP called
 PIDGIN_DEV_ROOT that points to c:\development?***
 [[BR]]
 Not explicitly, but setting it may help you to setup your initial
 environment. $PIDGIN_DEV_ROOT simply implies that you're welcome to
 extract Pidgin's sources (and dependent binaries and source archives)
 anywhere you please. I prefer something easier to get to in Cygwin than
 /cygdrive/c/development/pidgin_dev, but the choice is yours. A symlink
 (see next paragraph) will save you some keystrokes when you go to rebuild.

 I personally have (forgive the historical reference, but I've got too many
 things pointing at this to change it easily) E:\Gaim as my
 $PIDGIN_DEV_ROOT, with a symlink in my ~/source/ folder pointing
 ~/source/pidgin to /cygdrive/e/Gaim ({{{ln -s /cygdrive/e/Gaim
 ~/source/pidgin}}} from within a Cygwin terminal). When I build, the
 sources are essentially located at ~/source/pidgin/pidgin-mtn.
 [[BR]][[BR]]
 > ***Below, it says to:
 > (The following is the source tree root, containing the config.h.mingw
 file.)
 > C:\development\pidgin_dev\pidgin
 > Does this mean to copy the pidgin 2.0 source here?  That's what I did,
 since it contains the config.h.mingw file***
 [[BR]]
 Using C:\development\pidgin_dev as your Pidgin development root,
 C:\development\pidgin_dev\pidgin refers to the source of whatever copy of
 Pidgin you're compiling at the time. You could also use
 C:\development\pidgin_dev\pidgin-2.0.0 or C:\development\pidgin_dev
 \pidgin-monotone or the like. The name of this folder is really something
 that does not matter, but it's probably a good idea to name this folder
 appropriately. Looking at my $PIDGIN_DEV_ROOT, I have folders named
 pidgin-2.0.0, pidgin-mtn, pidgin-msnp14, pidgin-gobject, (plus a few more)
 which correspond to different releases of Pidgin and different branches of
 their source. In this same folder, there is a win32-dev folder which
 contains the various dependencies of Pidgin.
 [[BR]][[BR]]
 > ***Is this referring to after all of the dependencies have been
 installed?
 > (If the following file is present, your structure is probably correct.)
 > C:\development\pidgin_dev\win32-dev\gtk_2_0\include\libintl.h***
 [[BR]]
 If C:\development\pidgin_dev\pidgin contains the sources for Pidgin, then
 it sounds like you've extracted (at least a couple packages) to the
 ''right'' directory. I italicize ''right'', because the local.mak stuff
 below allows one to extract just about anything to just about anywhere.
 [[BR]][[BR]]
 > ***Additionally, you have this:
 > This can be overridden by creating a local.mak file in the
 $PIDGIN_DEV_ROOT/pidgin directory and overriding the various Makefile
 variables.
 > Is this something I should concern myself with, and even before that,
 $PIDGIN_DEV_ROOT/pidgin is not in the directory structure explained
 below***
 [[BR]]
 You needn't concern yourself with local.mak. It is of great use if you are
 doing something like compiling against a locally-compiled GTK+ that exists
 somewhere other than $PIDGIN_DEV_ROOT/win32-dev/gtk_2_0, or if you want to
 install Pidgin from a {{{make -f Makefile.mingw install}}} somewhere other
 than $PIDGIN_DEV_ROOT/$PIDGIN_FOLDER/win32-install-dir. An example to do
 the latter, simply put the following lines in local.mak in
 $PIDGIN_DEV_ROOT/$PIDGIN_FOLDER to install to the default C:\Program
 Files\Pidgin (untested, but works in theory):
 {{{
 PIDGIN_INSTALL_DIR = /cygdrive/c/Program\ Files/Pidgin
 PURPLE_INSTALL_DIR = /cygdrive/c/Program\ Files/Pidgin
 }}}
 Or, if you extracted aspell to C:\development\aspell-dev-0-50-3-3, with
 the remainder of Pidgin's deps under C:\development\pidgin_dev\win32-dev,
 the following will help (again, untested):
 {{{
 ASPELL_TOP = /cygdrive/c/development/aspell-dev-0-50-3-3
 }}}
 See libpurple/win32/global.mak to get an idea of what you're able to
 customize. If Pidgin is looking somewhere for something that can't be
 overridden from within local.mak, I'm sure a patch would be accepted that
 fixed this behavior.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/1017#comment:1>
Pidgin <http://pidgin.im>
Pidgin