Difference between revisions of "Appendix"
(Updated categories + links to new page name + some improvements)
|Line 29:||Line 29:|
Latest revision as of 18:37, 8 December 2011
- a global configuration file /etc/hemera.conf (setup and updated by System administrator) containing usually the most of global and third-party tools configuration elements
- a user configuration file $HOME/.hemera/hemera.conf allowing each Hemera user to adapt configuration to his needs (whatever the reason, if there is no global configuration file, any user can define a complete configuration file)
These pages use the notion of configuration elements which refers to elements which can be defined in either one of these configuration files.
You can see Configuring Hemera.
Binary and Library paths configuration
If you are not familiar with PATH and LD_LIBRARY_PATH environment variables, see *nix environment variables.
For better ease of use, Hemera configuration file provides two configuration elements to define some directory paths to add automatically to PATH or LD_LIBRARY_PATH environment variables
The syntax is a colon-separated list of directories.
You can use the '*' wildcard if path can vary according to situation (like it is the case with SphinxTrain bin-XX sub-directory). Hemera scripts will dynamically complete paths when starting.
In configuration file, there is various configuration elements named hemera.*.path allowing to define third-party tools to use.
For each, you can choose one of these ways to define it:
- specify the full path of the tool
- specify a path relative to HEMERA_TP_PATH
- specify simply the name of the tool if:
- it is available in the PATH environment variable (outside of Hemera)
- you have added its parent directory in hemera.path.bin
IMPORTANT: ensure to add library directory to hemera.path.lib for each third-party tools for which you have compiled source code (but if you have then installed them on your system). It is the case, for instance, if you have compiled sphinx3 source code.
Hemera scripts availability
In this documentation, command lines are usually given assuming Hemera scripts are available, which means parent directories are specified in $PATH, which is the case if you have setup Hemera.
After a global setup, Hemera scripts will be automatically available since next reboot. If you don't want to reboot, you can use:
After a user setup, you only have to open a new shell, or you can use:
The root directory where Hemera main project (and optional tools) is installed.
By default, it corresponds to /usr/share/hemera.
The root directory of third-party project in which tools are installed (or symbolic links are created).
It is defined with configuration element hemera.thirdParty.path.
By default, it corresponds to /usr/share/hemera/ThirdParty.