install:compile_cygwin

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
install:compile_cygwin [2008/08/25 13:31] – 92.252.45.110install:compile_cygwin [2010/12/03 09:30] (current) – old revision restored eros
Line 1: Line 1:
 ====== Compiling CWB from source under Windows ====== ====== Compiling CWB from source under Windows ======
  
-Compilation and installation of CWB version 2.2.b98+Compilation and installation of CWB version 3.0 
 + 
 + 
 + 
 + 
 +===== Status of the Cywgin port ===== 
 + 
 +The Cygwin port of the CWB is **experimental**.  While the source code compiles without error messages and basic CQP queries work well, it is currently not possible to process large corpora (e.g. in the 100M word range). 
 + 
 +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 to work on this port. 
  
  
Line 12: Line 24:
   * ''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.
Line 18: Line 32:
 ===== 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>
  
Line 27: Line 41:
  
 <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 on network drives) and make sure that the directory path //does not contain blanks// (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 =====
Line 40: Line 55:
 </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//
Line 84: Line 99:
 include $(TOP)/config/site/cygwin include $(TOP)/config/site/cygwin
 </file> </file>
 +
  
  
Line 96: Line 112:
 at the command line, and go to fetch a cup of coffee (due to the overhead of the Cygwin emulation layer, compilation is much slower than on Unix systems). at the command line, and go to fetch a cup of coffee (due to the overhead of the Cygwin emulation layer, compilation is much slower than on Unix systems).
  
-Then we compile the different components, one at a time. First we clean and check dependencies:+Since the Cygwin port is still experimental, it is probably a good idea to compile each component of the CWB separately. This will make it easier to recognise compilation errors and warnings. First, clean up any old files and check dependencies:
  
 <code bash> <code bash>
Line 103: Line 119:
 </code> </code>
  
-Then we compile the corpus library:+Then, compile the ''editline'' library used by CQP, which is included in the CWB source code distribution:
  
 <code bash> <code bash>
-make cl+make editline
 </code> </code>
  
-Then editline:+Now compile the corpus library:
  
 <code bash> <code bash>
-make editline+make cl
 </code> </code>
 +
  
 Then the utilities: Then the utilities:
Line 121: Line 138:
 </code> </code>
  
-Finally we compile cqp:+And finally CQP:
  
 <code bash> <code bash>
 make cqp make cqp
 </code> </code>
 +
 +You may also want to check that the manpages are up to date:
 +
 +<code bash>
 +make man
 +</code>
 +
 +
  
 ===== Installation ===== ===== Installation =====
Line 132: Line 157:
  
 <code bash> <code bash>
-sudo make install+make install
 </code> </code>
 +
 +If you have set up Cygwin with a separate administrator account, you may need to type ''sudo make install'' and enter the administrator password here.
  • install/compile_cygwin.1219663914.txt.gz
  • Last modified: 2008/08/25 13:31
  • by 92.252.45.110