3 \page running_salome_page Running Salome
5 There are two ways to run %SALOME:
7 1) Using <b>Salome Application Concept</b> approach.
9 For more details see \ref SALOME_Application.
11 2) Using <b>\c %runSalome</b> script supplied with %SALOME KERNEL module distribution.
13 To launch %SALOME using \c %runSalome script, you have first to
14 set-up proper environment for %SALOME. If you installed %SALOME using
15 %SALOME Installation Wizard (Linux), you can use \c salome.sh or
16 \c salome.csh script (that is located in the \c KERNEL_<version>
17 directory of your %SALOME installation), for example:
20 cd /home/user/salome_6.5.0/KERNEL_6.5.0
24 Launch %SALOME session using the \c %runSalome script located
25 in the \c SALOME/KERNEL/bin/salome directory:
28 runSalome [options] [STUDY_FILE] [PYTHON_FILE [PYTHON_FILE ...]]
31 Optionally, you can specify in the command line:
32 - Study (document) file to be opened in %SALOME session passing;
33 - One or more Python scripts to be executed after %SALOME
34 start-up. Python scripts will be executed in the new or opened study
35 in the order they appear in the command line.
37 The \c %runSalome script supports large set of options that allow
38 specifying the way to launch %SALOME session. Complete description of
39 all options can be obtained using \c --help or -h option:
45 Here below is a description of most important options:
49 Print detail help information on the \c %runSalome script.
53 Print version of %SALOME platform.
57 Launch %SALOME sesssion in GUI mode (with GUI desktop).
59 - \c --terminal or \c -t
61 Launch %SALOME session in terminal mode (without GUI).
63 - \c --resources=<file> or \c -r \c <file>
65 Parse application settings from the <file> instead of default resource
66 file. Default resource file is situated in user's home directory; for
67 example, for %SALOME version 6.5.0, the file is ${HOME}/.config/salome/.SalomeApprc.6.5.0
69 - \c --modules=module1,module2,... or \c -m=module1,module2,...
71 Specify the list of modules which will be used in the %SALOME session
72 being launched. Note, that list of modules is separated be comma
73 symbols, with no any spaces.
77 The servers open in separate terminal window and log messages are displayed in this window.
79 - <code>--embedded=registry,study,moduleCatalog,cppContainer/</code> or
80 <code>-e=registry,study,moduleCatalog,cppContainer</code>
82 Run listed %SALOME servers in the GUI embedded mode (default value is
83 <code>registry,study,moduleCatalog,cppContainer</code>). Note that logger,
84 pyContainer, and supervContainer servers cannot be embedded to
85 GUI. Note, that this option implies running %SALOME in GUI mode (\c -g
86 option); in terminal mode all servers are running in standalone mode.
88 - <code>--standalone=registry,study,moduleCatalog,cppContainer,pyContainer,supervContainer</code> or
89 <code>-s=registry,study,moduleCatalog,cppContainer,pyContainer,supervContainer</code>
91 Standalone CORBA servers (default: <code>pyContainer,supervContainer</code>).
93 - \c --portkill or \c -p
95 Kill %SALOME session launched with the current port.
97 - \c --killall or \c -k
99 Kill (stop) all running %SALOME sessions before launching new session.
101 - \c --splash=<1/0> or \c -z <1/0>
103 Use 1 to display splash screen [default] at start-up, 0 to disable
104 splash screen. This option is ignored in the terminal mode.
108 Launch with interactive Python console.
110 - <code>--interp=n</code> or <code>-i=n</code>
112 Number of additional Python interpreters to open, with session
113 environment propely set-up.