Difference between revisions of "Minimal installation from SVN"

From Apertium
Jump to navigation Jump to search
 
(34 intermediate revisions by 9 users not shown)
Line 1: Line 1:
[[Installation minimale depuis SVN|En français]]
{{TOCD}}
{{Github-migration-check}}
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]].
<div style="background-color:pink; text-align:center; line-height:2.5; border: 1px solid crimson;">This page is deprecated. </div>


The information which was here is split across other pages.
==Installing apertium and a language pair==
===Download===
For most language pairs, these are the packages you need:


The page contained,
* lttoolbox
* apertium
* apertium-lex-tools
* the language pair(s) your are interested in


* How to compile Apertium core. For this, please see [[Install Apertium core by compiling]]
Here are the commands if you would like the Esperanto-English pair:
<pre>
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
</pre>


* How to create new, or compile exisitng, language builds. For a new or mixed pair, see [[How to bootstrap a new pair]]. For existing pairs, see [[Install language data by compiling]],
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/).


* Details about the HFST and CG modules. Please see [[Installation of grammar libraries]]
===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:
<pre>
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
</pre>
You should also put those lines in your ~/.bashrc so you don't have to paste them into every terminal you open.


Or start from the information root at [[Installation]]?
However, if you want it installed somewhere else or don't want to install it as root, instead do:
<pre>
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
</pre>
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>apertium</code>
# <code>apertium-lex-tools</code>
# the language pair (e.g. <code>apertium-eo-en</code>)

<code>cd</code> to each of the directories before you run the the commands shown below.

If you didn't specify <code>$PREFIX</code> above, or don't know what this means, then do this in each directory:
<pre>
./autogen.sh
make
sudo make install
sudo ldconfig
</pre>

If you specified a <code>$PREFIX</code> (e.g. to avoid installing as root), then do this in each directory:
<pre>
./autogen.sh --prefix=$PREFIX
make
make install
ldconfig
</pre>


(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
<pre>
echo 'This is a test sentence.' | apertium from-to
</pre>
replacing from-to with the direction you want.

==For language pairs that use CG (vislcg3 / cg-proc / cg-comp) ==
Many language pairs now use [[Constraint Grammar]] (e.g. Macedonian→English, Breton→French, Nynorsk-Bokmål, …). For these, you need <code>vislcg3</code> beforehand. See [[Vislcg3#Installing_VISL_CG3]] for installation (use <code>./cmake.sh -DCMAKE_INSTALL_PREFIX=<prefix></code> if you're installing to a prefix).

Note that you have to have [http://site.icu-project.org/ ICU] installed beforehand (available through most GNU/Linux package managers, in Arch Linux as <code>icu</code>, in Debian/Ubuntu as <code>libicu-dev</code>, in Macports as <code>icu</code>).

==For language pairs that use HFST (hfst-proc / hfst-lexc / hfst-twolc)==
Many language pairs now use HFST (e.g. the Turkic and Saami ones). For these, you need <code>hfst</code> and <code>foma</code> beforehand. Follow the installation guides first for [[Foma]], then [[HFST]].

==See also==
* [[Installation]] – specific info for many different operating systems
* [[Installation Troubleshooting]]


[[Category:Documentation]]
[[Category:Installation]]
[[Category:Documentation in English]]

Latest revision as of 22:05, 7 March 2018

En français

WARNING

This page is out of date as a result of the migration to GitHub. Please update this page with new documentation and remove this warning. If you are unsure how to proceed, please contact the GitHub migration team.

This page is deprecated.

The information which was here is split across other pages.

The page contained,

Or start from the information root at Installation?