Changes between Version 3 and Version 4 of BuildingWinPidgin/3.0.0

Timestamp:

Apr 22, 2013, 9:09:40 PM (11 years ago)

Author:

tomkiewicz

Comment:

Building the Pidgin installer

BuildingWinPidgin/3.0.0

@@ -10 +10 @@
 
 
-  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.
+  2. Download and install [http://nsis.sourceforge.net/Download NSIS] and its plugins:
+     * 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;
+     * download the [http://nsis.sourceforge.net/Nsisunz_plug-in nsisunz plugin], and extract `nsisunz.dll` into the `Plugins` directory, like above.
 
 
-  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].
+  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.
 
 
-  4. Extract or check out [#GetthePidginsourcecode the Pidgin source] into `$PIDGIN_DEV_ROOT/pidgin-<version>`.
+  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].
+
+
+  5. Extract or check out [#GetthePidginsourcecode the Pidgin source] into `$PIDGIN_DEV_ROOT/pidgin-<version>`.
      Some users may find the [#CustomizingtheBuildEnvironment instructions for customizing their build environment] useful.
 
@@ -32 +37 @@
 }}}
 
-  5. Go through the rest of setting build environment using automatic setup script by running the following from Cygwin terminal:
+  6. Go through the rest of setting build environment using automatic setup script by running the following from Cygwin terminal:
 {{{
 #!sh
@@ -59 +64 @@
 == Build the Pidgin Installer ==
 
-TODO
+    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.:
 {{{
-#!comment
-  * 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):
-    * Download and install [http://nsis.sourceforge.net/Download NSIS]. Include NSIS to Cygwin's `PATH`.
-     *  For information on the NSIS installer, visit the [http://nsis.sourceforge.net NSIS website].[[BR]]
-    * Download the [http://nsis.sourceforge.net/Nsisunz_plug-in nsisunz plugin], and extract `nsisunz.dll` into the `Plugins` directory of your NSIS installation.
-    * Copy `$PIDGIN_DEV_ROOT/win32-dev/pidgin-inst-deps-20130214/SHA1Plugin.dll` into the `Plugins` directory of your NSIS installation.
-    * Now you'll need to decide if you want to sign the executables (not necessary for personal use)
-     * 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.:
-{{{
+SIGN_EXECUTABLES=1
 MONO_SIGNCODE=/cygdrive/c/Program\ Files\ \(x86\)/Mono-2.10.8/bin/signcode
 SIGNCODE_SPC=c:\\Path\\to\\authenticode.spc
@@ -76 +73 @@
 GPG_SIGN=gpg --no-default-keyring --secret-keyring /path/to/secring.gpg
 }}}
-     * Otherwise, in your `local.mak` file (see [wiki:"BuildingWinPidgin#CustomizingtheBuildEnvironment" below]),add the following:
-{{{
-#Disable Signing
-MONO_SIGNCODE=echo ***Bypassing signcode***
-GPG_SIGN=echo ***Bypassing gpg***
-}}}
-  * Now you can actually build the installer.[[BR]]
+
+    If you don't need executable signing, you can start here.
+
     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.
     The `Makefile.mingw` targets for these are `installer_offline`, and `installer` respectively.  To build both, use the `installers` target.
@@ -91 +84 @@
 }}}
     When it finishes, your installer(s) should be in `$PIDGIN_DEV_ROOT/pidgin-<version>/`.
-}}}
 
 == Customizing the Build Environment ==