- This will start SALOME according to the configuration parameters which
- are described into salome.launch file, located in your home directory
- ( $HOME/.salome/salome.launch ).
- If this file does not exists, it is created on the first launch of
- SALOME from <KERNEL_ROOT_DIR>/bin/salome/salome.launch.
-
- You can modify SALOME launching options by editing salome.launch file:
-
- <Configuration-list>
- <launchoptions>
- <gui>yes</gui>
- <logger>no</logger>
- <xterm>no</xterm>
- <portkill>yes</portkill>
- <killall>no</killall>
- </launchoptions>
- <modules-list>
- <module name="...">
- <plugin name="..."/>
- </module>
- </modules-list>
- <containers-list>
- <containertype>...</containertype>
- </containers-list>
- </Configuration-list>
-
- Each parameter described in salome.launch file can be overrided by
- using corresponding keys for runSalome script:
-
- --gui
- Launch GUI desktop
- --logger
- Use logger server
- --xterm
- Start each server in its own xterm console window
- --portkill
- Kill SALOME, running on the current port
- --killall
- Kill SALOME, running on all ports
- --modules=<module>,<module>,...,<module>
- Use module, possible values are GEOM, SMESH, VISU, MED, SUPERV
- --containers=<container>,<container>,...<container>
- Start container of type, possible values are cpp,python,superv
-
- Note that there is no key which corresponds to the <plugin> tag.
- This tag can be used currently only for SMESH module to point external
- meshers plugins which should be loaded by SMESH dynamically.
- Refer <SMESH_ROOT_DIR>/doc/salome/tui/SMESH/PluginMeshers.html
- for more information om meshers plugins.
+ This will start SALOME according to the launching parameters which
+ are described in the configuration files: SalomeApp.xml in the
+ <GUI_ROOT_DIR>/share/salome/resources/gui folder and
+ .SalomeApprc.<version_number> file, located in your home
+ directory (where <version_number> is SALOME version number).
+ If the user configuration file does not exist, it is automatically
+ created when exiting SALOME GUI.
+
+ You can modify SALOME launching options by editing your
+ ~/.SalomeApprc.<version_number> file (not all the options are
+ listed below):
+
+ <section name="launch">
+ <parameter name="gui" value="yes"/>
+ <parameter name="splash" value="yes"/>
+ <parameter name="file" value="no"/>
+ <parameter name="key" value="no"/>
+ <parameter name="interp" value="no"/>
+ <parameter name="logger" value="no"/>
+ <parameter name="xterm" value="no"/>
+ <parameter name="portkill" value="no"/>
+ <parameter name="killall" value="no"/>
+ <parameter name="modules" value="GEOM,SMESH,VISU,MED,YACS"/>
+ <parameter name="embedded" value="SalomeAppEngine"/>
+ <parameter name="standalone" value="study,pyContainer,cppContainer,registry,moduleCatalog"/>
+ </section>
+
+ Some parameters described in configuration file can be overridden by
+ using of corresponding command-line options for runSalome script:
+
+ -t, --terminal
+ Launch without GUI (in the terminal mode).
+ -g, --gui
+ Launch in GUI mode [default].
+ -d <1/0>, --show-desktop=<1/0>
+ 1 to activate GUI desktop [default], 0 to not activate
+ GUI desktop (Session_Server starts, but GUI is not
+ shown). Ignored in the terminal mode.
+ -o, --hide-desktop
+ Do not activate GUI desktop (Session_Server starts,
+ but GUI is not shown). The same as --show-desktop=0.
+ -b, --batch
+ Launch in Batch Mode. (Without GUI on batch machine)
+ -l, --logger
+ Redirect messages to the CORBA collector.
+ -f <log-file>, --log-file=<log-file>
+ Redirect messages to the <log-file>
+ -u <script1,script2,...>, --execute=<script1,script2,...>
+ Python script(s) to be imported. Python scripts are
+ imported in the order of their appearance. In GUI mode
+ python scripts are imported in the embedded python
+ interpreter of current study, otherwise in an external
+ python interpreter
+ -r <file>, --resources=<file>
+ Parse application settings from the <file> instead of
+ default $(HOME)/.SalomeApprc.$(version)
+ -x, --xterm
+ Launch each SALOME server in own xterm console
+ -m <module1,module2,...>, --modules=<module1,module2,...>
+ SALOME modules list (where <module1>, <module2> are
+ the names of SALOME modules which should be available
+ in the SALOME session)
+ -e <server1,server2,...>, --embedded=<server1,server2,...>
+ CORBA servers to be launched in the Session embedded
+ mode. Valid values for <serverN>: registry, study,
+ moduleCatalog, cppContainer, SalomeAppEngine [by
+ default the value from the configuration files is
+ used]
+ -s <server1,server2,...>, --standalone=<server1,server2,...>
+ CORBA servers to be launched in the standalone mode
+ (as separate processes). Valid values for <serverN>:
+ registry, study, moduleCatalog, cppContainer,
+ pyContainer, supervContainer [by default the value
+ from the configuration files is used]
+ -p, --portkill
+ Kill SALOME with the current port
+ -k, --killall
+ Kill all running SALOME sessions
+ -i <N>, --interp=<N>
+ The number of additional external python interpreters
+ to run. Each additional python interpreter is run in
+ separate xterm session with properly set SALOME
+ environment
+ -z <1/0>, --splash=<1/0>
+ 1 to display splash screen [default], 0 to disable
+ splash screen. This option is ignored in the terminal
+ mode. It is also ignored if --show-desktop=0 option is
+ used.
+ -c <1/0>, --catch-exceptions=<1/0>
+ 1 (yes,true,on,ok) to enable centralized exception
+ handling [default], 0 (no,false,off,cancel) to disable
+ centralized exception handling.
+ --print-port
+ Print free port and exit
+ --nosave-config
+ Do not save current configuration
+ ${HOME}/.omniORB_last.cfg
+ --pinter
+ Launch with interactive python console.
+ --ns-port-log=<ns_port_log_file>
+ Print Naming Service Port into a user file.
+ --gdb-session
+ Launch session with gdb
+ --version
+ Show program's version number and exit
+
+ Additional launch settings are given in other sections, which refer to certain
+ modules. For example, SMESH plugins which should be used in the SALOME launch
+ session can be mentioned in the <SMESH> section, e.g.:
+
+ <section name="SMESH">
+ <parameter name="name" value="Mesh"/>
+ <parameter name="icon" value="ModuleMesh.png"/>
+ <parameter name="plugins" value="StdMeshers,NETGENPlugin"/>
+ </section>