| Both sides previous revision Previous revision Next revision | Previous revision |
| install:compile_cygwin [2008/08/25 14:13] – 92.252.45.110 | install:compile_cygwin [2010/12/03 09:30] (current) – old revision restored eros |
|---|
| |
| Compilation and installation of CWB version 3.0 | Compilation and installation of CWB version 3.0 |
| | |
| |
| |
| The problems we have encountered may be due to limitations in the virtual memory management of Windows and the Cygwin emulation layer manage. Apparently, a user process is limited to a 2 GB address space in Windows, and Cygwin seems to impose [[http://cygwin.com/cygwin-ug-net/setup-maxmem.html|further restrictions]]. Help from someone with more experience in Windows and Cygwin programming would be highly welcome, so that we can identify the true cause of the problems and try to find a workaround. | The problems we have encountered may be due to limitations in the virtual memory management of Windows and the Cygwin emulation layer manage. Apparently, a user process is limited to a 2 GB address space in Windows, and Cygwin seems to impose [[http://cygwin.com/cygwin-ug-net/setup-maxmem.html|further restrictions]]. Help from someone with more experience in Windows and Cygwin programming would be highly welcome, so that we can identify the true cause of the problems and try to find a workaround. |
| |
| In the long term, we hope to offer a native Windows port of the CWB. Please join the [[http://devel.sslmit.unibo.it/mailman/listinfo/cwb|CWBdev mailing list]] if you would be interested in working on this port. | In the long term, we hope to offer a native Windows port of the CWB. Please join the [[http://devel.sslmit.unibo.it/mailman/listinfo/cwb|CWBdev mailing list]] if you would be interested to work on this port. |
| | |
| |
| ===== Prerequisites ===== | ===== Prerequisites ===== |
| * ''gcc'' | * ''gcc'' |
| * ''libncurses-devel'' | * ''libncurses-devel'' |
| | * ''make'' |
| | * ''perl'' |
| |
| We recommend to install the simple text editor ''nano'' (from the //Editors// section) for editing configuration files, but you can also use your favourite Windows text editor. | We recommend to install the simple text editor ''nano'' (from the //Editors// section) for editing configuration files, but you can also use your favourite Windows text editor. |
| | |
| |
| ===== Getting the source code ===== | ===== Getting the source code ===== |
| |
| Get the source code from [[http://cwb.sourceforge.net/|here]], and unpack it: | Get the source code from [[http://sourceforge.net/projects/cwb/|here]], and unpack it: |
| |
| <code bash> | <code bash> |
| tar xf cwb-XXXXXX.tgz | tar xf cwb-XXXXXX.tgz (current version 2.2.b99-RC1) |
| </code> | </code> |
| |
| |
| <code bash> | <code bash> |
| cd cwb-3.0 | cd cwb-XXXXXX (current version 2.2.b99-RC1) |
| </code> | </code> |
| |
| **Important note:** In principle, you can unpack the CWB source code anywhere you like, but //don't put it on a network drive// (we've encountered some weird errors there) and make sure that the directory path //does not contain blanks// (which will happen e.g. if you put the source code on your Desktop). The best solution is probably to keep the source code somewhere in the Cygwin directory tree, e.g. your Cygwin home directory. | **Important note:** In principle, you can unpack the CWB source code anywhere you like, but //don't put it on a network drive// (we've encountered some weird errors there) and make sure that the directory path //does not contain blanks// (which will happen e.g. if you put the source code on your Desktop). The best solution is probably to keep the source code somewhere in the Cygwin directory tree, e.g. your Cygwin home directory. |
| | |
| |
| ===== Edit the makefile ===== | ===== Edit the makefile ===== |
| </code> | </code> |
| |
| Otherwise, navigate to the ''cwb-3.0'' directory in Windows Explorer and open the file ''config.mk'' with a text editor. | Otherwise, navigate to the ''cwb-XXXXXX'' directory in Windows Explorer and open the file ''config.mk'' with a text editor. |
| |
| In the **platform** directive, insert //cygwin// | In the **platform** directive, insert //cygwin// |