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 3 and Version 4 of BuildingWinPidgin/3.0.0


Ignore:
Timestamp:
Apr 22, 2013, 9:09:40 PM (11 years ago)
Author:
tomkiewicz
Comment:

Building the Pidgin installer

Legend:

Unmodified
Added
Removed
Modified
  • BuildingWinPidgin/3.0.0

    v3 v4  
    1010
    1111
    12   2. Download the `Bonjour SDK for Windows` from [https://developer.apple.com/bonjour/ the Apple developer website] (Apple ID may be necessary) and install it to default location.
     12  2. Download and install [http://nsis.sourceforge.net/Download NSIS] and its plugins:
     13     * extract `SHA1Plugin.dll` from [/static/win32/pidgin-inst-deps-20130214.tar.gz pidgin-inst-deps-20130214.tar.gz] into the `Plugins` directory of your NSIS installation;
     14     * download the [http://nsis.sourceforge.net/Nsisunz_plug-in nsisunz plugin], and extract `nsisunz.dll` into the `Plugins` directory, like above.
    1315
    1416
    15   3. Download `Perl 5.10` or newer and install it, preferably to `C:\Perl`. You may use [http://www.activestate.com/activeperl/downloads ActivePerl Community Edition].
     17  3. Download the `Bonjour SDK for Windows` from [https://developer.apple.com/bonjour/ the Apple developer website] (Apple ID may be necessary) and install it to default location.
    1618
    1719
    18   4. Extract or check out [#GetthePidginsourcecode the Pidgin source] into `$PIDGIN_DEV_ROOT/pidgin-<version>`.
     20  4. Download `Perl 5.10` or newer and install it, preferably to `C:\Perl`. You may use [http://www.activestate.com/activeperl/downloads ActivePerl Community Edition].
     21
     22
     23  5. Extract or check out [#GetthePidginsourcecode the Pidgin source] into `$PIDGIN_DEV_ROOT/pidgin-<version>`.
    1924     Some users may find the [#CustomizingtheBuildEnvironment instructions for customizing their build environment] useful.
    2025
     
    3237}}}
    3338
    34   5. Go through the rest of setting build environment using automatic setup script by running the following from Cygwin terminal:
     39  6. Go through the rest of setting build environment using automatic setup script by running the following from Cygwin terminal:
    3540{{{
    3641#!sh
     
    5964== Build the Pidgin Installer ==
    6065
    61 TODO
     66    If you want to sign the executables (not necessary for personal use), you'll need to get an appropriate code signing certificate, generate a GPG key if you don't already have one, then download and install [http://www.mono-project.com/Download Mono]. In your `local.mak` file (see [#CustomizingtheBuildEnvironment below]), define the `SIGN_EXECUTABLES` variable to 1, `MONO_SIGNCODE` to the fully qualified path to the `signcode` batch file in the Mono `bin` directory, and the `SIGNCODE_SPC` and `SIGNCODE_PVK` variables to the appropriate files from your certificate. E.g.:
    6267{{{
    63 #!comment
    64   * 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):
    65     * Download and install [http://nsis.sourceforge.net/Download NSIS]. Include NSIS to Cygwin's `PATH`.
    66      *  For information on the NSIS installer, visit the [http://nsis.sourceforge.net NSIS website].[[BR]]
    67     * Download the [http://nsis.sourceforge.net/Nsisunz_plug-in nsisunz plugin], and extract `nsisunz.dll` into the `Plugins` directory of your NSIS installation.
    68     * Copy `$PIDGIN_DEV_ROOT/win32-dev/pidgin-inst-deps-20130214/SHA1Plugin.dll` into the `Plugins` directory of your NSIS installation.
    69     * Now you'll need to decide if you want to sign the executables (not necessary for personal use)
    70      * If you do, you'll need to get an appropriate code signing certificate, generate a GPG key if you don't already have one, then download and install [http://www.mono-project.com/Download Mono]. In your `local.mak` file (see [wiki:"BuildingWinPidgin#CustomizingtheBuildEnvironment" below]), define the `MONO_SIGNCODE` variable to the fully qualified path to the `signcode` batch file in the Mono `bin` directory, and the `SIGNCODE_SPC` and `SIGNCODE_PVK` variables to the appropriate files from your certificate. E.g.:
    71 {{{
     68SIGN_EXECUTABLES=1
    7269MONO_SIGNCODE=/cygdrive/c/Program\ Files\ \(x86\)/Mono-2.10.8/bin/signcode
    7370SIGNCODE_SPC=c:\\Path\\to\\authenticode.spc
     
    7673GPG_SIGN=gpg --no-default-keyring --secret-keyring /path/to/secring.gpg
    7774}}}
    78      * Otherwise, in your `local.mak` file (see [wiki:"BuildingWinPidgin#CustomizingtheBuildEnvironment" below]),add the following:
    79 {{{
    80 #Disable Signing
    81 MONO_SIGNCODE=echo ***Bypassing signcode***
    82 GPG_SIGN=echo ***Bypassing gpg***
    83 }}}
    84   * Now you can actually build the installer.[[BR]]
     75
     76    If you don't need executable signing, you can start here.
     77
    8578    There are 2 different installers, an "Offline" installer that includes all dependencies (except spellchecking dictionaries) and the debug symbols and an "Online" installer that includes only Pidgin itself and will download the various dependencies if necessary.
    8679    The `Makefile.mingw` targets for these are `installer_offline`, and `installer` respectively.  To build both, use the `installers` target.
     
    9184}}}
    9285    When it finishes, your installer(s) should be in `$PIDGIN_DEV_ROOT/pidgin-<version>/`.
    93 }}}
    9486
    9587== Customizing the Build Environment ==
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!