Trac is being migrated to new services! Issues can be found in our new YouTrack instance and WIKI pages can be found on our website.

Changes between Version 20 and Version 21 of BuildingWinPidgin


Ignore:
Timestamp:
Aug 4, 2007, 2:31:19 AM (17 years ago)
Author:
rageboy
Comment:

pidgin->pidgin-<version> to avoid confusion between root and root\pidgin

Legend:

Unmodified
Added
Removed
Modified
  • BuildingWinPidgin

    v20 v21  
    3131     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.
    3232
    33   3. The following instructions were written under the assumption that [#GetthePidginsourcecode the Pidgin source] will be extracted or checked out into `$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).
     33  3. The following instructions were written under the assumption that [#GetthePidginsourcecode the Pidgin source] will be extracted or checked out into `$PIDGIN_DEV_ROOT/pidgin-<version>` 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).
    3434     Some users may find the [#CustomizingtheBuildEnvironment instructions for customizing their build environment] useful.
    3535
     
    4242C:\development\pidgin_dev
    4343(The following is the source tree root, containing config.h.mingw and libpurple.)
    44 C:\development\pidgin_dev\pidgin
     44C:\development\pidgin_dev\pidgin-<version>
    4545C:\development\pidgin_dev\win32-dev
    4646(If the following file is present, your structure is probably correct.)
     
    9696  Run the following:
    9797{{{
    98 $ cd $PIDGIN_DEV_ROOT/pidgin
     98$ cd $PIDGIN_DEV_ROOT/pidgin-<version>
    9999$ make -f Makefile.mingw install
    100100}}}
    101   Now just wait and let your compiler do its thing.  When finished, Pidgin will be in `$PIDGIN_DEV_ROOT/pidgin/win32-install-dir`.
     101  Now just wait and let your compiler do its thing.  When finished, Pidgin will be in `$PIDGIN_DEV_ROOT/pidgin-<version>/win32-install-dir`.
    102102
    103103== Build the Pidgin Installer ==
     
    113113    The Makefile targets for these are `installer`, `installer_nogtk`, and `installer_debug` respectively.  To build all 3, use the `installers` target.
    114114{{{
    115 $ cd $PIDGIN_DEV_ROOT/pidgin
     115$ cd $PIDGIN_DEV_ROOT/pidgin-<version>
    116116$ make -f Makefile.mingw installers
    117117}}}
     
    122122  This is often useful to test against a development version of a library dependency or to override compiler flags.
    123123
    124   This done is by overridding the various Makefile variables in a `local.mak` file in the `$PIDGIN_DEV_ROOT/pidgin` directory.
     124  This done is by overridding the various Makefile variables in a `local.mak` file in the `$PIDGIN_DEV_ROOT/pidgin-<version>` directory.
    125125  This file does not exist by default.
    126126
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!