html version of this document is produced with docutils:
rst2html < doc.txt > doc.html
This document corresponds to SALOME2 3.2.0
| WORK in PROGRESS, INCOMPLETE DOCUMENT |
General information, for users, integrators and developers
Users, integrators and developers, which documentation ?
Following your kind of usage of SALOME, you will find some specific introductory documentation, listed below.
The end user may have to configure his own SALOME application by selection of a subset of availables SALOME modules. He also may want to install his application on several computers.
See SALOME_Application to define your own configuration of SALOME and run it on one or several computers. This is the recommended way of configuration.
The SALOME KERNEL offers offers a list of services available in Python.
See KERNEL_Services.
Applications integrators are in charge of configuration and installation of specific SALOME applications over a local network. Application Integrators built SALOME modules binaries from sources tarballs.
See INSTALL for general information on required configuration and prerequisites, compilation procedure, setting environment principles.
See SALOME_Application to define your own configuration of SALOME and run it on one or several computers. This is the recommended way of configuration.
Module maintainers are in charge of the development and debug of the SALOME modules. Each SALOME module is stored in a CVS base. CVS bases are organised in separate branches for developments and debug. All official or development releases are identified by a CVS tag.
See UnitTests for general information on code directories structure, unit tests associated to the different kind of classes, and how to run the unit tests.
See kernel_resources for information on basic utilities for C++ and Python development, like trace and debug, exceptions, singleton.
| General KERNEL documentation | End User KERNEL Doxygen documentation |