Changes between Version 64 and Version 65 of BuildingWinPidgin

Timestamp:

Dec 7, 2009, 4:45:32 AM (14 years ago)

Author:

John Bailey

Comment:

Note that cross-compiling doesn't play nice with amd64 distros

BuildingWinPidgin

@@ -147 +147 @@
 
 == Cross Compiling ==
-  It is quite easy to cross compile Pidgin for Windows on a Linux machine.
+  It is quite easy to cross compile Pidgin for Windows on a Linux machine.  Note that cross-compiling does '''''not''''' work properly on amd64 (also called x86_64 or x64) systems--the most common failure is that the linker will die with a segmentation fault at various points.
 
   To begin, you'll need to install MinGW. On Debian/Ubuntu, this involves installing packages `mingw32`, `mingw32-binutils`, and `mingw32-runtime`. On other distributions, the packages may be named differently.
@@ -170 +170 @@
   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.
 
-  If you want to build the installers, you'll need to build the GTK+ installer as mentioned above.  However, the `build.sh` script referenced above needs to be changed.  The line starting with `makensis.exe` needs to be changed to read:
+  If you want to build the installers, you'll need to install NSIS.  On Debian and Ubuntu, the package name is `nsis`; this will likely be different elsewhere.  In order to build the GTK+ installer as mentioned above, the `build.sh` script referenced above needs to be changed.  The line starting with `makensis.exe` needs to be changed to read:
 {{{
 makensis -V3 -DGTK_VERSION=$gtk_version -DGTK_REVISION=$gtk_revision gtk-installer.nsi