Difference between revisions of "Minimal installation from SVN"
(headings) |
|||
Line 3: | Line 3: | ||
==Installing apertium and a language pair== |
==Installing apertium and a language pair== |
||
===Download=== |
|||
For most language pairs, these are the packages you need: |
For most language pairs, these are the packages you need: |
||
Line 22: | Line 22: | ||
===Set up environment=== |
|||
By default, Apertium is installed under the directory <code>/usr/local</code>, which requires root (sudo) access when installing. If that's fine with you, do: |
By default, Apertium is installed under the directory <code>/usr/local</code>, which requires root (sudo) access when installing. If that's fine with you, do: |
||
<pre> |
<pre> |
||
Line 42: | Line 42: | ||
You should also put those lines in your ~/.bashrc so you don't have to paste them into every terminal you open. |
You should also put those lines in your ~/.bashrc so you don't have to paste them into every terminal you open. |
||
===Configure, build and install=== |
|||
The next step is to configure, build and install each of the modules you checked out, in this order: |
|||
# <code>lttoolbox</code> |
# <code>lttoolbox</code> |
||
# <code>apertium</code> |
# <code>apertium</code> |
||
Line 50: | Line 50: | ||
<code>cd</code> to each of the directories before you run the the commands shown below. |
<code>cd</code> to each of the directories before you run the the commands shown below. |
||
⚫ | |||
⚫ | |||
⚫ | |||
⚫ | |||
⚫ | |||
⚫ | |||
⚫ | |||
If you specified a <code>$PREFIX</code> (e.g. to avoid installing as root), then do this in each directory: |
If you specified a <code>$PREFIX</code> (e.g. to avoid installing as root), then do this in each directory: |
||
Line 57: | Line 65: | ||
make install |
make install |
||
ldconfig |
ldconfig |
||
⚫ | |||
⚫ | |||
⚫ | |||
⚫ | |||
⚫ | |||
⚫ | |||
⚫ | |||
</pre> |
</pre> |
||
Line 70: | Line 70: | ||
(If you're on a Mac, you don't need to do ldconfig, don't worry that it fails.) |
(If you're on a Mac, you don't need to do ldconfig, don't worry that it fails.) |
||
===Test=== |
|||
Now test that it works. The command <code>apertium -l</code> should show a list of translation directions, of the form "from-to". Pick one, and do |
Now test that it works. The command <code>apertium -l</code> should show a list of translation directions, of the form "from-to". Pick one, and do |
||
<pre> |
<pre> |
Revision as of 08:46, 21 November 2013
This guide shows you how to download, configure, compile and install core apertium packages and language data. It assumes you've already installed the prerequisites for your system – if you have not, see the system-specific guides under Installation.
Installing apertium and a language pair
Download
For most language pairs, these are the packages you need:
- lttoolbox
- apertium
- apertium-lex-tools
- the language pair(s) your are interested in
Here are the commands if you would like the Esperanto-English pair:
svn checkout https://svn.code.sf.net/p/apertium/svn/trunk/lttoolbox svn checkout https://svn.code.sf.net/p/apertium/svn/trunk/apertium svn checkout https://svn.code.sf.net/p/apertium/svn/trunk/apertium-lex-tools svn checkout https://svn.code.sf.net/p/apertium/svn/trunk/apertium-eo-en
If you want another pair than eo-en, only the last line needs changing. To see the available 'released' language pairs, go to https://svn.code.sf.net/p/apertium/svn/trunk/ (pairs which are in development are in the incubator/nursery/staging subdirectories of https://svn.code.sf.net/p/apertium/svn/).
Set up environment
By default, Apertium is installed under the directory /usr/local
, which requires root (sudo) access when installing. If that's fine with you, do:
LD_LIBRARY_PATH=/usr/local/lib:${LD_LIBRARY_PATH} export LD_LIBRARY_PATH PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:${PKG_CONFIG_PATH} export PKG_CONFIG_PATH
You should also put those lines in your ~/.bashrc so you don't have to paste them into every terminal you open.
However, if you want it installed somewhere else or don't want to install it as root, instead do:
PREFIX=$HOME/local # or wherever you want apertium stuff installed LD_LIBRARY_PATH=$PREFIX/lib:${LD_LIBRARY_PATH} export LD_LIBRARY_PATH PKG_CONFIG_PATH=$PREFIX/lib/pkgconfig:${PKG_CONFIG_PATH} export PKG_CONFIG_PATH
You should also put those lines in your ~/.bashrc so you don't have to paste them into every terminal you open.
Configure, build and install
The next step is to configure, build and install each of the modules you checked out, in this order:
lttoolbox
apertium
apertium-lex-tools
- the language pair (e.g.
apertium-eo-en
)
cd
to each of the directories before you run the the commands shown below.
If you didn't specify $PREFIX
above, or don't know what this means, then do this in each directory:
./autogen.sh make sudo make install sudo ldconfig
If you specified a $PREFIX
(e.g. to avoid installing as root), then do this in each directory:
./autogen.sh --prefix=$PREFIX make make install ldconfig
(If you're on a Mac, you don't need to do ldconfig, don't worry that it fails.)
Test
Now test that it works. The command apertium -l
should show a list of translation directions, of the form "from-to". Pick one, and do
echo 'This is a test sentence.' | apertium from-to
replacing from-to with the direction you want.
For language pairs that use CG (vislcg3 / cg-proc)
Many language pairs now use CG (e.g. Macedonian→English, Breton→French, Nynorsk-Bokmål, …). For these, you need vislcg3
beforehand. See Vislcg3#Installing_VISL_CG3 for installation (use ./cmake.sh -DCMAKE_INSTALL_PREFIX=<prefix>
if you're installing to a prefix).
Note that you have to have ICU installed beforehand (available through most GNU/Linux package managers, in Arch Linux as icu
, in Debian/Ubuntu as libicu-dev
).
For language pairs that use HFST
Many language pairs now use HFST (e.g. the Turkic and Saami ones). For these, you need hfst
and typically OpenFST
and foma
beforehand. Follow the installation guides first for Foma and OpenFST, then HFST.
See also
- Installation – specific info for many different operating systems
- Installation Troubleshooting