Main components: autotools, giella-core and templates.
All languages are independent “projects/products”
Building is done (e.g. for sme) in the $GTHOME/langs/sme folder, with:
./autogen.sh -l ./configure make sudo make install
(Note that the ./configure command may take different parameters, see directly below.)
The same commands are used for all languages in the different
langs/ dir, if one wants to build and
install more languages (note that there is a script makeall.sh to compile all languages).
(See also the overview of the subdirectories in each language directory.)
As mentioned, the command
./configure is used to set up different options for compilation.
In order to see all the available options, write:
In order to see what installation you have set just now, write:
The answer will read Invocation command line was, and thereafter
./configure command, with the current settings displayed. A situation
make will build fsts for dictionaries, but otherwise just give the
default values, will show as follows:
Default options may be turned off with disable, e.g. by writing:
or, to turn off the –with options, write –without, and then what you do not want:
Several options may be stacked after each other, in any order.
<lang>/am-shared/ # shared build instructions - the real build stuff m4/ # configuration macros
NEVER TOUCH THESE DIRECTORIES AND FILES!!!
These files (and directories) are always updated by merging in changes from the templates (see below). Such changes should only be done by the infrastructure maintainers.
$GTHOME/giella-core/ - contains core:
Two templates defined so far (6.11.2012):
The infrastructure of all languages are updated by merging in changes in the
templates. Only languages with a corresonding
.timestamp file will be
Template updates MUST be coordinated - the merging is relatively fragile, and at the same time modifies many files.
There’s a separate
test/ dir that contains a mirror hierarchy to the other
dirs, and which contains a couple of test shell script. The basic requirements
for the test scripts are:
TESTSvariable in one of the
As long as these requirements are met, the test scripts can be written in any language - even C!