5 *salomeTools* uses files to store its configuration parameters.
7 There are several configuration files which are loaded by salomeTools in a specific order.
8 When all the files are loaded a *config* object is created.
9 Then, this object is passed to all command scripts.
14 The configuration files use a python-like structure format
15 (see `config module <http://www.red-dove.com/config-doc/>`_ for a complete description).
17 * **{}** define a dictionary,
18 * **[]** define a list,
19 * **@** can be used to include a file,
20 * **$prefix** reference to another parameter (ex: ``$PRODUCT.name``),
23 .. note:: in this documentation a reference to a configuration parameter will be noted ``$XXX.YYY``.
32 | This section is dynamically created by salomeTools at run time.
33 | It contains information about the environment: date, time, OS, architecture etc.
35 .. note:: use this command to get the current setting: *sat config -v VARS*
40 | This section is defined in the product file.
41 | It contains instructions on how to build a version of SALOME (list of prerequisites-products and versions)
43 .. note:: use this command to get the current setting: *sat config SALOME-xx -v PRODUCTS*
47 | This section is optional, it is also defined in the product file.
48 | It gives additional parameters to create an application based on SALOME, as versions of products to use.
50 .. note:: use this command to get the current setting: *sat config SALOME-xx -v APPLICATION*
56 This section is defined by the user configuration file
57 which is located in *~/.salomeTools/salomeTools.pyconf*.
59 The USER section defines parameters (not exhaustive):
61 * **workDir** the working directory. Each product will be usually installed here (in sub-directories).
62 * and other users preferences.
64 .. note:: use this command to get the current setting: *sat config SALOME-xx -v USER*.