Changes between Version 2 and Version 3 of BuildingWinPidgin/3.0.0

Timestamp:

Apr 22, 2013, 4:06:09 PM (11 years ago)

Author:

MarkDoliner

Comment:

s/hxxp/http/

BuildingWinPidgin/3.0.0

@@ -42 +42 @@
 {{{
 #!comment
-  The source for Pidgin 3.x.y is available [hxxp://prdownloads.sourceforge.net/pidgin/pidgin-3.x.y.tar.bz2 here] (use the latest release if this isn't updated yet).[[BR]][[BR]]
+  The source for Pidgin 3.x.y is available [http://prdownloads.sourceforge.net/pidgin/pidgin-3.x.y.tar.bz2 here] (use the latest release if this isn't updated yet).[[BR]][[BR]]
 }}}
   The 3.0.0 branch isn't released yet, so there are no source packages for this at the moment.[[BR]][[BR]]
@@ -63 +63 @@
 #!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 [hxxp://nsis.sourceforge.net/Download NSIS]. Include NSIS to Cygwin's `PATH`.
-     *  For information on the NSIS installer, visit the [hxxp://nsis.sourceforge.net NSIS website].[[BR]]
-    * Download the [hxxp://nsis.sourceforge.net/Nsisunz_plug-in nsisunz plugin], and extract `nsisunz.dll` into the `Plugins` directory of your NSIS installation.
+    * 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 [hxxp://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.:
+     * 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.:
 {{{
 MONO_SIGNCODE=/cygdrive/c/Program\ Files\ \(x86\)/Mono-2.10.8/bin/signcode
@@ -116 +116 @@
 
 == Debugging ==
-  There is a quite good '''Just In Time''' debugger for MinGW: [hxxp://code.google.com/p/jrfonseca/wiki/DrMingw drmingw].[[BR]]
+  There is a quite good '''Just In Time''' debugger for MinGW: [http://code.google.com/p/jrfonseca/wiki/DrMingw drmingw].[[BR]]
   There is also a version of `gdb` available from MinGW, if you prefer.
 
@@ -143 +143 @@
 }}}
 
-  If your distribution doesn't include a recent enough win32api, you can download it from the [hxxp://www.mingw.org/ MinGW site], extract it into your `win32-dev` directory, and override the `INCLUDE_PATHS` and `LIB_PATHS` variables in your `local.mak` as I have done.
+  If your distribution doesn't include a recent enough win32api, you can download it from the [http://www.mingw.org/ MinGW site], extract it into your `win32-dev` directory, and override the `INCLUDE_PATHS` and `LIB_PATHS` variables in your `local.mak` as I have done.
 
-      NSIS version 2.46 or greater is required to cross-compile.  If compiling NSIS from source, the [hxxp://www.scons.org/ scons] package is a dependency.  This can usually be installed through your linux distribution's package archive.  An example of how to install the NSIS package is given below (Assuming use of the NSIS 2.46 version):
+      NSIS version 2.46 or greater is required to cross-compile.  If compiling NSIS from source, the [http://www.scons.org/ scons] package is a dependency.  This can usually be installed through your linux distribution's package archive.  An example of how to install the NSIS package is given below (Assuming use of the NSIS 2.46 version):
 
       `.tar.bz2` file contains latest source[[BR]]
@@ -152 +152 @@
 #!sh
 mkdir nsis; cd nsis
-wget hxxp://prdownloads.sourceforge.net/nsis/nsis-2.46-src.tar.bz2?download 
-wget hxxp://prdownloads.sourceforge.net/nsis/nsis-2.46.zip?download
+wget http://prdownloads.sourceforge.net/nsis/nsis-2.46-src.tar.bz2?download 
+wget http://prdownloads.sourceforge.net/nsis/nsis-2.46.zip?download
 tar -jxvf nsis-2.46-src.tar.bz2
 cd nsis-2.46