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.
37 # to get the current setting
38 sat config --value VARS
42 | This section is defined in the product file.
43 | It contains instructions on how to build a version of SALOME (list of prerequisites-products and versions)
47 # to get the current setting
48 sat config SALOME-xx --value PRODUCTS
52 | This section is optional, it is also defined in the product file.
53 | It gives additional parameters to create an application based on SALOME, as versions of products to use.
57 # to get the current setting
58 sat config SALOME-xx --value APPLICATION
65 This section is defined by the user configuration file,
66 ``~/.salomeTools/salomeTools.pyconf``.
68 The ``USER`` section defines some parameters (not exhaustive):
72 | The working directory.
73 | Each product will be usually installed here (in sub-directories).
75 * **browser** : The web browser to use (*firefox*).
77 * **editor** : The editor to use (*vi, pluma*).
79 * and other user preferences.
83 # to get the current setting
84 sat config SALOME-xx --value USER