Difference between revisions of "Apertium on Windows"

From Apertium
Jump to navigation Jump to search
(re-organitzed)
Line 1: Line 1:
  +
==Using Cygwin==
  +
 
It is possible to compile Apertium for use on windows using [http://cygwin.com/ Cygwin], which provides a UNIX-like environment in windows.
 
It is possible to compile Apertium for use on windows using [http://cygwin.com/ Cygwin], which provides a UNIX-like environment in windows.
   
Line 13: Line 15:
 
* subversion (Devel)
 
* subversion (Devel)
   
==Steps==
+
===Steps===
   
 
# Check out the repository as normal using svn.
 
# Check out the repository as normal using svn.
Line 29: Line 31:
 
## make
 
## make
   
==Alternatives==
+
==Using Mingw==
  +
  +
=== From Linux (cross-compiling) ===
  +
  +
  +
=== From Windows ===
   
 
One could look into using [http://www.mingw.org MinGW instead]. This would allow compiling the packages on Linux.
 
One could look into using [http://www.mingw.org MinGW instead]. This would allow compiling the packages on Linux.

Revision as of 09:51, 14 July 2007

Using Cygwin

It is possible to compile Apertium for use on windows using Cygwin, which provides a UNIX-like environment in windows.

Before you begin you should install the cygwin with the following additional packages, if you find this list incomplete please update it.

  • autoconf (Devel)
  • automake (Devel)
  • flex (Devel)
  • libgcrypt (Libs)
  • libtool (Devel)
  • libxml2 (Devel)
  • libxml2-devel (Devel)
  • libxslt (Libs)
  • pkg-config (Devel)
  • subversion (Devel)

Steps

  1. Check out the repository as normal using svn.
  2. Patch the apertium source this patch (save it as no_unlocked.diff)
    $ patch -p1 < no_unlocked.diff
  3. and this one too (save as no_ansi.diff)
    $ patch -p1 < no_ansi.diff
  4. Make and install lttoolbox
    1. ./autogen.sh
    2. make
    3. make install
  5. Make and install apertium (required the patches from above)
    1. export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig/
    2. ./autogen.sh
    3. make

Using Mingw

From Linux (cross-compiling)

From Windows

One could look into using MinGW instead. This would allow compiling the packages on Linux.