gnucash/packaging/win32
Christian Stimming a67b94b32f Fix libofx and OFX import on win32.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@15523 57a11ea4-9604-0410-9ed3-97b8803252fd
2007-02-08 13:58:29 +00:00
..
create_cross_mingw.sh Add script for building a cross-compile mingw toolchain on Linux. 2006-09-14 15:33:42 +00:00
custom.sh Update win32 build to use aqbanking-2.2.7. 2007-02-07 10:10:02 +00:00
dist.sh Add libofx/opensp to resulting win32 setup.exe 2007-02-07 10:09:03 +00:00
functions Add checking for whether an unpacked directory isnt confused with an older one. 2007-02-07 14:38:47 +00:00
gnucash.iss.in Add more registry keys for aqbanking/gwenhywfar. Also, delete those keys on uninstall again. 2007-01-31 14:00:59 +00:00
goffice-0.3.0-patch.diff Repost goffice-0.3.0-patch.diff, with gtk-doc.m4 included. 2006-10-11 17:09:32 +00:00
goffice-0.3.2-patch.diff Some win32 package updates: 2006-11-01 22:43:00 +00:00
install.sh Fix libofx and OFX import on win32. 2007-02-08 13:58:29 +00:00
libofx-0.8.3-patch.diff Fix libofx and OFX import on win32. 2007-02-08 13:58:29 +00:00
opensp-1.5.2-patch.diff Add compiling and installation of opensp, libofx and enable ofx support of gnucash 2007-02-06 16:19:23 +00:00
pi.sh Add pi.sh, a postinstall script of mingw. 2006-09-01 21:33:01 +00:00
README Update win32 installation instruction according to last months' changes 2007-01-16 20:48:24 +00:00
reset.sh Fix typo in reset.sh. 2006-10-21 18:31:05 +00:00

These scripts try to download and install a Windows/mingw32 build
environment for GnuCash on Windows. 

For cross-compiling the windows executable on Linux, see the lower
section of this file.

Before you start with the automated build, you have to complete these
steps manually. The directory variables are set in custom.sh.

* Download MSYS (but *only* msys; no mingw and no msysdtk)
from http://www.mingw.org/download.shtml -> Current -> MSYS -> (bin, *.exe)
to $DOWNLOAD_DIR

* Install MSYS (no postinstall)
to $MSYS_DIR

* Download wget
from http://www.mingw.org/download.shtml -> Current -> mingwPORT -> (bin, wget-*)
to $DOWNLOAD_DIR

* Adjust custom.sh (install.sh doesn't need to be changed). In
  custom.sh you should adapt the directory variables. If you want to,
  you could also comment out those build steps that have been
  completed already and/or should not be performed now, although the
  script is quite intelligent not to duplicate already completed
  work. If you want verbose output of any script step, change the
  first line in install.sh and add the "-x" switch.

Start/Enter any MSYS shell window. Let the automated build begin by:

  $INSTALLER_DIR/install.sh

Good luck!

To generate a self-installing setup.exe file that contains
*everything*, run the following command after install.sh has
completed:

  $INSTALLER_DIR/dist.sh

More information is collected on http://wiki.gnucash.org/wiki/Windows


--------------------------

Cross-compiling a Windows/mingw32 executable of GnuCash on a Linux
host system. (Note: This used to work unchangedly in Sept'2006 but
probably not any longer.)

These steps need to be performed:

1. Edit the file create_cross_mingw.sh and set the PREFIX= variable to
   the preferred prefix of the mingw32 gcc/binutils on your
   Linux. (It is strongly recommended to choose a different prefix
   than your normal compiler toolchain in order to distinguish
   your native vs. cross compiler more easily.) Then run the
   script create_cross_mingw.sh - it will
   download, compile, and install a mingw32 toolchain.

2. Edit the file custom.sh: Make a globale search-and-replace of
   '\\' into '/' so that all directories are specified in unix
   conventions. Set the variable cross_compile to "yes". Then
   adjust the directories in custom.sh according to your
   preferred installation, especially $GLOBAL_DIR.

3. Download a binary windows packages for "guile" e.g. from
   http://www.tu-harburg.de/~et2cs/gnc/ and unpack it into the
   directory $GUILE_DIR as given in custom.sh. (This is done because
   the build system for guile doesn't support cross-compiling.)

4. Call install.sh, which will read the directory settings from
   custom.sh. It should download, compile, and install everything
   automatically. Eventually the windows gnucash is installed into
   $GNUCASH_DIR. 

5. The content of $GNUCASH_DIR (as well as all the other binary
   packages) should then be copied to a windows machine. The paths
   in $GNUCASH_DIR/bin/gnucash and/or $GNUCASH_DIR/bin/gnucash.bat
   need to be adjusted for the installation location on the
   windows machine.

Good luck!