Difference between revisions of "Prerequisites for nix"

From Apertium
Jump to navigation Jump to search
(Gather all on one page.)
 
(GitHub migration)
 
(5 intermediate revisions by 2 users not shown)
Line 6: Line 6:
You will need,
You will need,


* git
* subversion
* subversion


to download (and contribute back) apertium code.
to download (and contribute back) apertium code. Note that Apertium code using subversion is read-only because Apertium has migrated to GitHub; the latest code and development will occur on GitHub.


You may also want the text-match-and-hack tool,
You may also want the text-match-and-hack tool,
Line 15: Line 16:


which is used in many examples on the wiki (but is not necessary)
which is used in many examples on the wiki (but is not necessary)



==Compiling tools==
==Compiling tools==
Line 25: Line 25:
* g++
* g++
* make (GNU)
* make (GNU)


[[Category:Installation]]
[[Category:Documentation in English]]
* pkg-config
* pkg-config
* autogen
* autogen
Line 32: Line 36:
* build-essential
* build-essential


(which also includes 'dpkg', the base tool for Debian packaging)
(also includes 'dpkg', the base tool for Debian packaging)


Also,
Also,
Line 51: Line 55:


===Necessary libraries===
===Necessary libraries===
If installed by packaging system, and the packaging system splits headers from libraries, you need the headers too. For example, on Debian, install available xxx-dev packages also.
If installed by packaging system, and the packaging system splits headers from libraries, you need the headers too. For example, on Debian, install available xxx-dev packages ('dev' packages will load the main library also).


* flex
* flex
Line 57: Line 61:
* libxlst
* libxlst
* libpcre
* libpcre
* zlib (under Debian 'zlib1g')
* zlib

=== Extra libraries ===
These rarely need to be compiled, as packaging is available.

==== vslcg3 ====

* libboost
* libicu
* libgoogle-perftools/gperftools (same code by different names)
* cmake (a build tool)


==== HFST ====
* flex
* bison
* libreadline-dev


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

Latest revision as of 05:35, 8 March 2018

This a general list. Also applies to Mac OS and building in a *nix environment under Windows.

See also the specific instructions for several operating systems/distributions.

Help tools[edit]

You will need,

  • git
  • subversion

to download (and contribute back) apertium code. Note that Apertium code using subversion is read-only because Apertium has migrated to GitHub; the latest code and development will occur on GitHub.

You may also want the text-match-and-hack tool,

  • gawk

which is used in many examples on the wiki (but is not necessary)

Compiling tools[edit]

Linux/GNU compile tools[edit]

These may be pre-installed on operating systems, even general systems such as Ubuntu,

  • gcc
  • g++
  • make (GNU)
  • pkg-config
  • autogen

In larger packaging systems, one package may cover all of these. For example, in Debian:

  • build-essential

(also includes 'dpkg', the base tool for Debian packaging)

Also,

  • libc
  • gettext

almost always pre-installed on any *nix. 'libc' will probably include a necessary 'iconv' library.

GNU build system tools[edit]

These may not be pre-installed on operating systems unless dedicated to compiling,

  • autoconf
  • automake
  • libtool

'autoconf' will include several other necessary libraries such as 'm4' and 'perl'.

Necessary libraries[edit]

If installed by packaging system, and the packaging system splits headers from libraries, you need the headers too. For example, on Debian, install available xxx-dev packages ('dev' packages will load the main library also).

  • flex
  • libxml2
  • libxlst
  • libpcre
  • zlib (under Debian 'zlib1g')

Extra libraries[edit]

These rarely need to be compiled, as packaging is available.

vslcg3[edit]

  • libboost
  • libicu
  • libgoogle-perftools/gperftools (same code by different names)
  • cmake (a build tool)


HFST[edit]

  • flex
  • bison
  • libreadline-dev