1 <!doctype HTML public "-//W3C//DTD HTML 4.0 Frameset//EN">
\r
5 <!--(==============================================================)-->
\r
6 <!--(Document created with RoboEditor. )============================-->
\r
7 <!--(==============================================================)-->
\r
11 <title>Installing SALOME</title>
\r
13 <!--(Meta)==========================================================-->
\r
15 <meta http-equiv=content-type content="text/html; charset=windows-1252">
\r
16 <meta name=generator content="RoboHELP by eHelp Corporation - www.ehelp.com">
\r
17 <meta name=generator-major-version content=0.1>
\r
18 <meta name=generator-minor-version content=1>
\r
19 <meta name=filetype content=kadov>
\r
20 <meta name=filetype-version content=1>
\r
21 <meta name=page-count content=1>
\r
22 <meta name=layout-height content=8574>
\r
23 <meta name=layout-width content=825>
\r
26 <!--(Links)=========================================================-->
\r
28 <link rel='stylesheet' href='../default_ns.css'>
\r
29 <script type="text/javascript" language="JavaScript" title="WebHelpSplitCss">
\r
31 if (navigator.appName !="Netscape")
\r
32 { document.write("<link rel='stylesheet' href='../default.css'>");}
\r
35 <style type="text/css">
\r
37 h1.whs1 {font-size: 24pt;}
\r
38 hr.whs2 {float: aligncenter; text-align: justify;}
\r
39 p.whs3 {text-align: justify;}
\r
40 h3.whs4 {text-align: justify;}
\r
41 p.whs5 {text-align: justify; font-style: italic; color: #ff0000;}
\r
42 p.whs6 {text-align:justify; background-image:url(../texture_horiz_ltbluebubbles.jpg); }
\r
43 img_whs7 {border-style: none; border: none; width: 36px; height: 38px; float: none;}
\r
44 p.whs8 {text-align: justify; text-indent: 48px;}
\r
45 p.whs9 {text-align: justify; margin-left: 40px;}
\r
46 p.whs10 {text-align: center;}
\r
47 img_whs11 {border-style: none; width: 638px; height: 404px;}
\r
48 img_whs12 {border-style: none; width: 481px; height: 117px;}
\r
49 table.whs13 {width: 100%; float: alignleft; x-border-left: 4px table-solid; x-border-top: 4px table-solid; x-border-right: 4px table-solid; x-border-bottom: 4px table-solid; border-collapse: separate; x-border-left: 4px table-solid; x-border-top: 4px table-solid; x-border-right: 4px table-solid; x-border-bottom: 4px table-solid; border-collapse: separate;}
\r
50 th.whs14 {background-color: #c0c0c0;}
\r
51 td.whs15 {background-color: #e4e4e4;}
\r
52 p.whs16 {font-family: 'Times New Roman', serif; text-align: justify;}
\r
53 p.whs17 {font-family: 'Times New Roman', serif;}
\r
56 <script type="text/javascript" language="JavaScript" title="BSSC Special Effects" src="../ehlpdhtm.js"></script><script type="text/javascript" language="JavaScript" title="WebHelpInlineScript">
\r
59 if (innerWidth != origWidth || innerHeight != origHeight)
\r
62 if ((parseInt(navigator.appVersion) == 4) && (navigator.appName == "Netscape")) {
\r
63 origWidth = innerWidth;
\r
64 origHeight = innerHeight;
\r
70 <style type="text/css">
\r
72 div.WebHelpPopupMenu {position:absolute; left:0px; top:0px; z-index:4; visibility:hidden;}
\r
75 <script type="text/javascript" language="javascript1.2" src="../whmsg.js"></script>
\r
76 <script type="text/javascript" language="javascript" src="../whver.js"></script>
\r
77 <script type="text/javascript" language="javascript1.2" src="../whproxy.js"></script>
\r
78 <script type="text/javascript" language="javascript1.2" src="../whutils.js"></script>
\r
79 <script type="text/javascript" language="javascript1.2" src="../whtopic.js"></script>
\r
82 <!--(Body)==========================================================-->
\r
87 <script type="text/javascript" language="javascript1.2">
\r
89 if (window.gbWhTopic)
\r
91 if (window.addTocInfo)
\r
93 addButton("show",BTN_TEXT,"Show","","","","",0,0,"","","");
\r
96 if (window.writeBtnStyle)
\r
99 if (window.writeIntopicBar)
\r
100 writeIntopicBar(1);
\r
102 if (window.setRelStartPage)
\r
104 setRelStartPage("../kernel.html");
\r
112 document.location.reload();
\r
115 <h1 class="whs1"><span style="font-size: 24pt;"><font size=6 style="font-size:24pt;">Installing
\r
116 SALOME platform </font></span></h1>
\r
119 <!--(HR)============================================================-->
\r
120 <hr align="center" class="whs2">
\r
125 <li class=kadov-p><p class="whs3"><a href="#install_from_script">Installing
\r
126 products using install script directly</a></p></li>
\r
128 <li class=kadov-p><p class="whs3"><a href="#install_from_wizard">Installing
\r
129 products using Installation Wizard</a></p></li>
\r
131 <li class=kadov-p><p class="whs3"><a href="#check_version_proc">Notes
\r
132 on checking products version procedure</a></p></li>
\r
134 <li class=kadov-p><p class="whs3"><a href="#pick_up_env">Picking
\r
135 up the environment</a></p></li>
\r
139 <!--(HR)============================================================-->
\r
140 <hr align="center" class="whs2">
\r
143 <h3 class="whs4"><a NAME=install_from_script></a>Installing
\r
144 products using <tt><font style="color: #ff0000;"
\r
145 color=#FF0000>install</font></tt> script directly</h3>
\r
147 <p class="whs5">To run installation using the install script,
\r
148 type in the command line of a terminal window:</p>
\r
150 <p class="whs3"> </p>
\r
152 <p class="whs3"><tt style="font-family: monospace;">./install
\r
153 [options] <target-directory> [ [ALL] | <product> ... <product>
\r
156 <p class="whs3"> </p>
\r
158 <p class="whs3">Available options are the following: </p>
\r
160 <p class="whs3"><tt style="font-family: monospace;">--binaries</tt>
\r
161 is not an obligatory parameter. If you pass this parameter all products
\r
162 will be extracted from the precompiled archives. Otherwise all products
\r
163 will be installed and built from the sources using gnu make procedure.
\r
167 <p class="whs6"><img src="../note1.gif" x-maintain-ratio="TRUE" width="36px" height="38px" border="0" class="img_whs7"> Take into account that target platform for precompiled binaries
\r
168 is Linux Red Hat 8.0. If you want to install SALOME onto another Linux
\r
169 version, you should use <b><i>sources</i></b> installation mode. </p>
\r
171 <p class="whs3"> </p>
\r
173 <p class="whs3"><tt style="font-family: monospace;">--reinstall</tt>
\r
174 is an optional parameter. Use this parameter if you want to reinstall
\r
175 products you have already installed.</p>
\r
177 <p class="whs3"> </p>
\r
179 <p class="whs3"><tt style="font-family: monospace;">--update</tt>
\r
180 is an optional parameter. Pass this parameter to the script if you want
\r
181 your profile to be updated by the installation script. This option is
\r
182 used only when <b>SALOME sources</b> and/or <b>SALOME binaries </b>are
\r
185 <p class="whs3"> </p>
\r
187 <p class="whs3"><tt style="font-family: monospace;">--native</tt>
\r
188 is optional parameter. This option states the way the installation procedure
\r
189 picks up the environment for the products which are not currently installed.
\r
190 When this option is used, the installation script first tries to find
\r
191 and use native products. If necessary products are not found in /usr/bin
\r
192 and /usr/lib directories, script looks for them in the target directory.
\r
193 If the option is not used (default behaviour), the script first inspects
\r
194 the target directory and the system folders. <br>
\r
195 For more detail information see <a href="#pick_up_env">here.</a> </p>
\r
197 <p class="whs3"> </p>
\r
199 <p class="whs3"><tt style="font-family: monospace;">--with-mesa</tt>
\r
200 is also optional parameter. This parameter forces linking <b>VTK </b>and
\r
201 <b>Qt</b> with <b>Mesa</b> library and is not taken into account if <b>Mesa
\r
202 </b>library is not installed in the target directory. </p>
\r
204 <p class="whs3"> </p>
\r
206 <p class="whs3"><tt style="font-family: monospace;">--temp
\r
207 </tt>is optional parameter, the directory path must follow it. This directory
\r
208 is used for temporary files. By default script uses <b>/tmp </b>folder.
\r
209 You can change this directory if you doesn't have sufficient amount of
\r
210 disk space in the <b>/tmp</b> folder. <b><br>
\r
213 <p class="whs6"><img src="../note1.gif" x-maintain-ratio="TRUE" width="36px" height="38px" border="0" class="img_whs7"> The directory you point should exist and must be an absolute
\r
214 path, otherwise installation script will fail. </p>
\r
216 <p class="whs3"> </p>
\r
218 <p class="whs3"><tt style="font-family: monospace;"><target-directory></tt>
\r
219 is the only obligatory parameter and should be an absolute path. This
\r
220 will be the root directory for installing products. </p>
\r
222 <p class="whs3"> </p>
\r
224 <p class="whs6"><img src="../note1.gif" x-maintain-ratio="TRUE" width="36px" height="38px" border="0" class="img_whs7"> This directory should exist. <tt><target-directory></tt>
\r
225 and temp directory must not coincide to avoid collisions. </p>
\r
227 <p class="whs3"> </p>
\r
229 <p class="whs3"><tt style="font-family: monospace;"><product>
\r
230 ... <product></tt> are the symbolic names of the installing products.
\r
232 Prerequisite products are <b>gcc tcl cas python numeric swig mesa qt qwt
\r
233 sip pyqt hdf med omni vtk salomebin salomesources salomedoc</b> <br>
\r
234 Additional bonus products are <b>doxygen graphviz happydoc</b> </p>
\r
236 <p class="whs3">You can also use <tt>ALL</tt> parameter
\r
237 to install all supplied products at once. </p>
\r
239 <p class="whs3"> </p>
\r
241 <p class="whs6"><img src="../note1.gif" x-maintain-ratio="TRUE" width="36px" height="38px" border="0" class="img_whs7"> If you want to use native products do not add them into the
\r
242 script parameters. You should also use <tt>--native</tt> option in this
\r
245 <p class="whs3"> </p>
\r
247 <p class="whs3"><tt style="font-family: monospace;">--help</tt>
\r
248 or <tt>-h</tt> key will print this information. </p>
\r
251 <!--(HR)============================================================-->
\r
252 <hr align="center" class="whs2">
\r
255 <h3 class="whs4"><a NAME=install_from_wizard></a>Installing
\r
256 products using <font style="color: #ff0000;"
\r
257 color=#FF0000>Installation Wizard</font></h3>
\r
259 <p class="whs8">Actually you can install
\r
260 all necessary products with help of the install script. But it's not convenient
\r
261 because you have to enter in the command line all parameters used by this
\r
262 script in a strictly definite order. You are strongly recommended to use
\r
263 Installation Wizard program. It represents a GUI superstructure over the
\r
264 shell script. It helps you to install all products needed for SALOME platform,
\r
265 avoiding the problem with parameters' order. </p>
\r
267 <p class="whs8"> </p>
\r
269 <p class="whs5">To run Installation Wizard, type in the command
\r
270 line of the terminal</p>
\r
272 <p class="whs3"> </p>
\r
274 <p class="whs9"> <b>./runInstall.csh</b>.
\r
277 <p class="whs3"> </p>
\r
279 <p class="whs8">This software was built
\r
280 with help of <b><i>Qt</i></b>. The wizard contains several pages. To navigate
\r
281 between pages use <i>"Next"</i> and <i>"Back"</i>
\r
282 buttons in the lower part of the wizard window. <i>"Cancel"</i>
\r
283 button closes dialog window and quits the installation procedure. To invoke
\r
284 this help information click <i>"Help"</i> button. </p>
\r
286 <p class="whs3">Skip the first <i>"<span style="font-weight: bold;"><B>Introduction</B></span>"</i>
\r
287 page by pressing <i>"<span style="font-weight: bold;"><B>Next</B></span>"</i>
\r
288 button. In the second page you have the possibility to select products
\r
289 for installation (see <a href="#ProductPage">Fig.1</a> ). Each product
\r
290 has several options of installation - it can be installed as precompiled
\r
291 binaries, as sources or not installed at all. You can mark the products,
\r
292 you want to install, by clicking the corresponding radiobuttons and checkboxes
\r
293 in the list view in the left part of the page. Note that some products
\r
294 can be installed only together with other products (or these products
\r
295 should be already installed on your machine). So the installation procedure
\r
296 has a special feature to automatically mark these products in the list
\r
297 view. For example, in order to install <b><i>pyqt</i></b> it's necessary
\r
298 to have <b><i>gcc, python</i></b>,<b><i> qt</i></b> and <b><i>sip</i></b>
\r
299 installed. Therefore all these products will be marked when you check
\r
300 on <b><i>pyqt</i></b>. This feature can be switched off by clicking <i>"<span
\r
301 style="font-weight: bold;"><B>Auto set prerequisites products</B></span>"</i>
\r
303 There are three special buttons in the right part of the page. If you want
\r
304 to install all products as sources just click <i>"<span style="font-weight: bold;"><B>Select
\r
305 Sources</B></span>"</i> button. This will also mark <b><i>SALOME docs</i></b>,
\r
306 <b><i>SALOME sources</i></b> and <b><i>SALOME binaries</i></b> items.
\r
307 You can mark all products (except <b><i>gcc</i></b> and <b><i>swig</i></b>,
\r
308 see below) as binaries by clicking <i>"<span style="font-weight: bold;"><B>Select
\r
309 Binaries (recommended)</B></span>"</i> button. This will mark <b><i>SALOME
\r
310 docs</i></b>, <b><i>SALOME sources</i></b> and <b><i>SALOME binaries</i></b>
\r
311 items too. <i>"<span style="font-weight: bold;"><B>Unselect All</B></span>"</i>
\r
312 resets all products to <i>"not install"</i> state. </p>
\r
314 <p class="whs3"> </p>
\r
316 <p align="center" class="whs10"><img src="../productpage.png" width="638px" height="404px" border="0" class="img_whs11"> <br>
\r
317 <a NAME=ProductPage></a><b>Figure 1:</b> "Products to install"
\r
320 <p align="center" class="whs10"> </p>
\r
322 <p class="whs3">The <i>"<span style="font-weight: bold;"><B>Total
\r
323 disk space required:</B></span>"</i> field displays how much disk space
\r
324 on the hard drive is required for installation of selected products. <br>
\r
325 Installation procedure uses a special directory for storing temporary files.
\r
326 The <i>"<span style="font-weight: bold;"><B>Space for temporary files:</B></span>"</i>
\r
327 field shows the information about required disk space on the hard drive
\r
328 for extracting and compiling of the selected products. </p>
\r
332 <p class="whs6"><b
\r
333 style="font-weight: bold;"><img src="../note1.gif" x-maintain-ratio="TRUE" width="36px" height="38px" border="0" class="img_whs7"> </b>Please, take into account
\r
334 that displayed amount of required disk space is approximate and may differ
\r
335 when you install products on your hard drive. </p>
\r
337 <p class="whs3"> </p>
\r
339 <p class="whs3"> </p>
\r
341 <p class="whs6"><b
\r
342 style="font-weight: bold;"><img src="../note1.gif" x-maintain-ratio="TRUE" width="36px" height="38px" border="0" class="img_whs7"> </b>Not all products can be installed
\r
343 as precompiled binaries. <b><i>gcc</i></b> and <b><i>swig</i></b> must
\r
344 be installed as sources and then compiled. Therefore when you try to install
\r
345 all products as binaries by clicking <i>"Select Binaries (recommended)"</i>
\r
346 button these two items will be marked as sources and you will get the
\r
347 following <a href="#CantInstall">warning message box</a> </p>
\r
349 <p align="center" class="whs10"> </p>
\r
351 <p align="center" class="whs10"><img src="../cantinstall.png" width="481px" height="117px" border="0" class="img_whs12"> <br>
\r
352 <a NAME=CantInstall></a><b>Figure 2:</b> <b><i>gcc</i></b> and <b><i>swig</i></b>
\r
353 warning message box </p>
\r
355 <p align="center" class="whs10"> </p>
\r
357 <p class="whs6"><b
\r
358 style="font-weight: bold;"><img src="../note1.gif" x-maintain-ratio="TRUE" width="36px" height="38px" border="0" class="img_whs7"></b> Installation procedure has
\r
359 the limitation concerning<b> </b>gcc 3.2 installation procedure. The known
\r
360 bug of the gcc3.2 is impossibility to build it on the computer where gcc3.2
\r
361 is already installed. In this case build procedure fails. </p>
\r
363 <p class="whs3"> </p>
\r
365 <p class="whs3">To proceed installation click <i>"<span
\r
366 style="font-weight: bold;"><B>Next</B></span>"</i> button. </p>
\r
368 <p class="whs3">In the second page you are proposed to
\r
369 enter the target directory where all selected products will be installed
\r
370 to (see <a href="#DirPage">Fig.3</a> ). You can also press <i>"<span
\r
371 style="font-weight: bold;"><B>Browse</B></span>..."</i> button and choose
\r
372 the folder for installation using standard <b><i>Qt</i></b> browse directory
\r
375 <p class="whs3">As it was mentioned before, the shell script
\r
376 uses a special directory for storing all temporary files. The <b>/tmp</b>
\r
377 folder is used by default. You can change this default behaviour - just
\r
378 type any folder or use the corresponding <i>"<span style="font-weight: bold;"><B>Browse...</B></span>"</i>
\r
382 <p class="whs3">The temporary folder field is disabled
\r
383 when you are installing only binaries. </p>
\r
385 <p class="whs3"> </p>
\r
387 <p align="center" class="whs10"><img src="../dirpage.png" width="638px" height="404px" border="0" class="img_whs11"> <br>
\r
388 <a NAME=DirPage></a><b>Figure 3:</b> "Installation settings"
\r
391 <p class="whs3"> </p>
\r
393 <p class="whs8">If the directory you
\r
394 want to install products does not exist you will be prompted by message
\r
395 box to confirm this directory creation. If you type wrong directory path,
\r
396 or if you have no permission for the directory you use the corresponding
\r
397 message box will raise. <br>
\r
398 The installation procedure also checks available disk space on the selected
\r
399 directories according to the products selected. If there is no enough
\r
400 disk space on your hard drive you will also see the corresponding error
\r
403 <p class="whs8">Unfortunately, the configure
\r
404 procedure has a very annoying bug under Linux platform. The directory
\r
405 should be obligatory entered without spaces. For example, the configure
\r
406 procedure for <b><i>gcc</i></b> won't work if you pass the following parameter:
\r
407 <i>--prefix="/New Folder 1"</i>. <b>Therefore you are strongly
\r
408 recommended not to use directory names containing spaces.</b> </p>
\r
410 <p class="whs3">In case if you have some products already
\r
411 installed on your machine it will be very convenient not to install these
\r
412 products again, because repeated compiling can take a lot of time. We
\r
413 have added checking of installed products in the installation shell script
\r
414 in order to decrease time for installing of products. But it can lead
\r
415 to some troubles. For example, the shell script can successfully check
\r
416 <b><i>Qt</i></b> (check <b>QTDIR</b> and find libqt-mt.so.3.0.5) but some
\r
417 files can be corrupted or non-existent (e.g. some header files have been
\r
418 accidentally removed ). For such cases in the shell script there is a
\r
419 possibility to reinstall these corrupted products. For that purpose you
\r
420 have to check <i>"<span style="font-weight: bold;"><B>Reinstall products
\r
421 you have already installed (recommended)?</B></span>"</i> option on this
\r
422 page. You are recommended to use <i>"<span style="font-weight: bold;"><B>No</B></span>"</i>
\r
423 switch only if this Installation Wizard program has been used before.
\r
426 <p class="whs3">For more detailed information about checking
\r
427 products version procedure see <a href="#check_version_proc">here</a>.
\r
430 <p class="whs8"><a name=profile></a>The
\r
431 shell script creates special files: <b>.salomecsh</b> and <b>.salomesh</b>
\r
432 in the <b><i>SALOME sources</i></b> and <b><i>SALOME binaries</i></b>
\r
433 root directories. You have a possibility to add one of them into your
\r
434 profile. Just check <i>"<span style="font-weight: bold;"><B>Do you want
\r
435 to update your profile?</B></span>" </i>option In this case your
\r
436 environment will always point to the newly installed products. </p>
\r
438 <p class="whs8">Check <i>"<span
\r
439 style="font-weight: bold;"><B>Use Mesa library</B></span>"</i> option if
\r
440 you want to install/build Vtk and Qt (OpenGL support) to be linked to
\r
441 preinstalled Mesa library. You should have Mesa drivers installed on the
\r
442 target directory or somewhere else, but in the last case you have to set
\r
443 MESA_HOME environment variable. Or you should choose Mesa 3.4.2 product
\r
444 to be installed also. Otherwise Vtk/Qt without Mesa support will be installed.
\r
447 <p class="whs8">If you want to use native
\r
448 Linus Red Hat 8.0 products (these are gcc, tcl, Python, Qt, Sip and PyQt)
\r
449 do not mark these products in the <i>"<span style="font-weight: bold;"><B>Products
\r
450 to install</B></span>"</i> page and check <i>"<span style="font-weight: bold;"><B>Prefer
\r
451 native products</B></span>" </i>option. See <a href="#pick_up_env">Pick
\r
452 up the environment</a> section for more detail information. </p>
\r
454 <p class="whs3">To proceed further click <i>"<span
\r
455 style="font-weight: bold;"><B>Next</B></span>"</i> button (see <a href="#ChoicePage">Fig.4</a>).
\r
458 <p class="whs3"> </p>
\r
460 <p align="center" class="whs10"><img src="../choicepage.png" width="638px" height="404px" border="0" class="img_whs11"> <br>
\r
461 <a NAME=ChoicePage></a><b>Figure 4:</b> "Check your choice" page
\r
464 <p align="center" class="whs10"> </p>
\r
466 <p class="whs3">This page summarizes the installation settings
\r
467 you've made on the previous pages. You can check again the settings and
\r
468 change them if necessary. <br>
\r
469 When you are sure that everything is OK, press <i>"<span style="font-weight: bold;"><B>Next</B></span>"</i>
\r
470 button to follow to the <a href="#ProgressPage">next page</a>. </p>
\r
472 <p class="whs3"> </p>
\r
474 <p align="center" class="whs10"><img src="../progresspage.png" width="638px" height="404px" border="0" class="img_whs11"> <br>
\r
475 <a NAME=ProgressPage></a><b>Figure 5:</b> "Installation progress"
\r
478 <p class="whs3"> </p>
\r
480 <p class="whs3">To start installation of the selected products
\r
481 click <i>"<span style="font-weight: bold;"><B>Start</B></span>"</i>
\r
482 button. It launches the shell installation script and you will be able
\r
483 to see the output of the script in the topmost dialog's frame. In case
\r
484 of any installation problems (for example, you have accidentally removed
\r
485 the temporary directory) the script will ask you: <i>"<span style="font-weight: bold;"><B>Would
\r
486 you like to continue : (Y,N) ?</B></span>"</i>. You can answer this question
\r
487 by typing [Y] or [N] in the middle text edit control frame. <b><span style="font-weight: normal;"><br>
\r
488 P</span></b>ress [Enter] when you finish typing data. </p>
\r
490 <p class="whs3">The <i>"<span style="font-weight: bold;"><B>Installation
\r
491 Status</B></span>"</i> frame window shows you the progress of installation.
\r
492 It contains a list of all selected products with brief descriptions. "<font
\r
493 style="color: #ff0000;"
\r
494 color=#FF0000>Waiting</font>" description means that installation
\r
495 of this product have not started yet. Currently installing product is
\r
496 marked as "<font style="color: #FF9900;"
\r
497 color=#FF9900>Processing</font>". All installed
\r
498 products have "<font style="color: #33FF33;"
\r
499 color=#33FF33>Completed</font>" description.
\r
502 <p class="whs3">You can abort installation and close the
\r
503 installation procedure using <i>"Cancel"</i> button. It sends
\r
504 the signal "SIGTERM" to the shell script. The script has a signal
\r
505 handler and will try to clear all temporary files. The process of removing
\r
506 temporary files can take some time, so the installation wizard will wait
\r
507 3 seconds before closing. </p>
\r
509 <p class="whs3">At the end of installation (all selected
\r
510 products have been installed successfully) you can go back to the previous
\r
511 pages to start a new installation or click <i>"Finish"</i> button
\r
512 to close the installation wizard. </p>
\r
515 <!--(HR)============================================================-->
\r
516 <hr align="center" class="whs2">
\r
519 <h3 class="whs4"><a NAME=check_version_proc></a>Notes on<font
\r
520 style="color: #ff0000;"
\r
521 color=#FF0000> checking products version</font> procedure</h3>
\r
523 <p>Unfortunately under Linux platform there is no exact algorithm to identify
\r
524 the product's version. The table below contains the information relating
\r
525 to checking preinstalled products. <br>
\r
528 <!--(Table)=========================================================-->
\r
529 <div align=left><table NOSAVE x-use-null-cells width="100%" border="4" class="whs13">
\r
532 <th NOSAVE bgcolor="#C0C0C0" class="whs14"><font style="font-size: medium;"
\r
533 size=4>Product</font> </th>
\r
534 <th NOSAVE bgcolor="#C0C0C0" class="whs14"><font style="font-size: medium;"
\r
535 size=4>Algorithm of checking</font> </th>
\r
536 <th NOSAVE bgcolor="#C0C0C0" class="whs14"><font style="font-size: medium;"
\r
537 size=4>Preliminary steps before launching</font>
\r
538 <font style="font-size: medium;"
\r
540 of installation procedure</font> </th>
\r
541 <th NOSAVE bgcolor="#C0C0C0" class="whs14"><font style="font-size: medium;"
\r
542 size=4>Notes</font> </th></tr>
\r
545 <td bgcolor="#E4E4E4" class="whs15">
\r
546 <p class="whs3">gcc 3.2</td>
\r
547 <td>ver=`/usr/bin/gcc --version | grep 'gcc (GCC) .*' | cut -b 11-13`</td>
\r
549 <td>ver should be equal 3.2 <br>
\r
550 It is recommended to use native gcc on Linux RedHat 8.0</td></tr>
\r
553 <td bgcolor="#E4E4E4" class="whs15">
\r
554 <p class="whs3">tcl 8.3</td>
\r
555 <td NOSAVE>existence of TCLHOME <br>
\r
556 existence of tclsh8.3 <br>
\r
557 existence of wish8.3 <br>
\r
558 existence of libtcl8.3.so <br>
\r
559 existence of libtk8.3.so <br>
\r
560 existence of libtclx8.3.so <br>
\r
561 existence of libtkx8.3.so</td>
\r
562 <td>set TCLHOME if you have preinstalled version of tcl. <br>
\r
563 set LD_LIBRARY_PATH on a directory where libs can be found.</td>
\r
564 <td>It is recommended to use native tcl on Linux RedHat 8.0</td></tr>
\r
567 <td bgcolor="#E4E4E4" class="whs15">
\r
568 <p class="whs3">Cascade 4.0</td>
\r
569 <td>existence of CASROOT environment variable</td>
\r
570 <td>set CASROOT if you have preinstalled version of CASCADE</td>
\r
571 <td>Unfortunately we can't say anything exactly about CASCADE 4.0 and we
\r
572 only check CASROOT environment variable. If you have problem with preinstalled
\r
573 version of CASCADE reinstall it</td></tr>
\r
576 <td bgcolor="#E4E4E4" class="whs15">
\r
577 <p class="whs3">Python 2.2.1</td>
\r
578 <td>existense of PYTHONHOME <br>
\r
579 isPython=`which python` <br>
\r
580 ver=`python -V`</td>
\r
581 <td>set PYTHONHOME to root Python folder <br>
\r
582 set PATH on a directory where python can be found</td>
\r
583 <td>Python should exist and ver should be equal to 2.2.1 <br>
\r
584 It is recommended to use native Python on Linux RedHat 8.0</td></tr>
\r
587 <td bgcolor="#E4E4E4" class="whs15">
\r
588 <p class="whs3">Mesa 3.4.2</td>
\r
589 <td>existence of libGL.so.1.2.030402</td>
\r
590 <td>set LD_LIBRARY_PATH on a directory where libGL.so.1.2.030402 can be
\r
592 <td>You have a possibility to build products (vtk & qt) with Mesa drivers
\r
593 from the package supplied with this installation procedure or to use OpenGL
\r
594 drivers installed on your computer locally. This check procedure concerns
\r
595 only supplied Mesa driver.</td></tr>
\r
598 <td bgcolor="#E4E4E4" class="whs15">
\r
599 <p class="whs3">Swig 1.3.17</td>
\r
600 <td>isSwig=`which swig` <br>
\r
601 ver=`swig -version` <br>
\r
602 ver=`echo $ver | awk '{print $3}'`</td>
\r
603 <td>set PATH on a directory where swig can be found</td>
\r
604 <td>Swig should exist and ver should be equal to 1.3.17</td></tr>
\r
607 <td bgcolor="#E4E4E4" class="whs15">
\r
608 <p class="whs3">Qt 3.0.5</td>
\r
609 <td>existence of QTDIR <br>
\r
610 existence of libqt-mt.so.3.0.5</td>
\r
611 <td>set QTDIR if you have preinstalled version of qt</td>
\r
612 <td>We try to find libqt-mt.so.3.0.5 in ${QTDIR}/lib folder. <br>
\r
613 You should set MESA_HOME only if you have preinstalled version of Mesa
\r
615 It is recommended to use native Qt on Linux RedHat 8.0</td></tr>
\r
618 <td bgcolor="#E4E4E4" class="whs15">
\r
619 <p class="whs3">Qwt 0.4.1</td>
\r
620 <td>existence of QWTHOME <br>
\r
621 existence of libqwt.so.0.4.1</td>
\r
622 <td>set QWTHOME if you have preinstalled version of qwt</td>
\r
623 <td>We try to find libqwt.so.0.4.1 in the ${QWTHOME}/lib folder. </td></tr>
\r
626 <td bgcolor="#E4E4E4" class="whs15">
\r
627 <p class="whs3">Hdf 5-1.4.4</td>
\r
628 <td>existence of HDF5HOME <br>
\r
629 existence of libhdf5.so.0.0.0 <br>
\r
630 existence of libhdf5.settings</td>
\r
631 <td>set HDF5HOME if you have preinstalled version of hdf</td>
\r
632 <td>We try to find libhdf5.so.0.0.0 and libhdf5.settings in ${HDF5HOME}/lib
\r
634 File libhdf5.settings should contain the following entry: <br>
\r
635 HDF5 Version: 1.4.4</td></tr>
\r
638 <td bgcolor="#E4E4E4" class="whs15">
\r
639 <p class="whs3">Med 2.1.6</td>
\r
640 <td>existence of MED2HOME <br>
\r
641 existence of libmed.so.0.0.0</td>
\r
642 <td>set MED2HOME if you have preinstalled version of med</td>
\r
643 <td>Unfortunately we can't check version number. <br>
\r
644 We try to find libmed.so.0.0.0 in ${MED2HOME}/lib folder. <br>
\r
645 If you have problem with preinstalled version of med reinstall it.</td></tr>
\r
648 <td bgcolor="#E4E4E4" class="whs15">
\r
649 <p class="whs3">Vtk 4.2</td>
\r
650 <td>existence of VTKHOME <br>
\r
651 existence of libvtkCommon.so</td>
\r
652 <td>set VTKHOME if you have preinstalled version of vtk</td>
\r
653 <td>Unfortunately we can't check the version number. <br>
\r
654 We try to find libvtkCommon.so in ${VTKHOME}/lib/vtk folder. <br>
\r
655 If you have problem with preinstalled version of vtk reinstall it.</td></tr>
\r
658 <td bgcolor="#E4E4E4" class="whs15">
\r
659 <p class="whs3">OmniORB 3.0.5, <br>
\r
660 OmniORBpy 1.5, <br>
\r
661 OmniNotify 1.2</td>
\r
662 <td>existence of OMNIORBDIR <br>
\r
663 existence of libomniORB3.so.0.5 <br>
\r
664 existence of _omnipymodule.so.0.5 <br>
\r
665 existence of libCOSNotify3.so.0.5 <br>
\r
666 existence of notifd <br>
\r
667 existence of THIS_IS_omniORB_3_0_5 <br>
\r
668 existence of THIS_IS_omniNotify_1_2 <br>
\r
669 existence of THIS_IS_OMNIORBPY_1_5</td>
\r
670 <td>set OMNIORBDIR if you have preinstalled version of omni</td>
\r
671 <td>We try to find libomniORB3.so.0.5, _omnipymodule.so.0.5 and libCOSNotify3.so.0.5
\r
672 in ${OMNIORBDIR}/lib/i586_linux_2.0_glibc2.1 folder. <br>
\r
673 We try to find notifd in ${OMNIORBDIR}/bin/i586_linux_2.0_glibc2.1 folder.
\r
675 Additional checking - omni add special files THIS_IS_... <br>
\r
676 We try to find THIS_IS_omniORB_3_0_5 in ${OMNIORBDIR} folder. <br>
\r
677 We try to find THIS_IS_omniNotify_1_2 in ${OMNIORBDIR}/src/services/omniNotify.
\r
679 We try to find THIS_IS_OMNIORBPY_1_5 in ${OMNIORBDIR}/src/lib/omniORBpy
\r
683 <td bgcolor="#E4E4E4" class="whs15">
\r
684 <p class="whs3">Numeric 22.0</td>
\r
685 <td>existence of Numeric folder <br>
\r
686 existence of _numpy.so</td>
\r
687 <td>set PYTHONHOME if you have preinstalled version of python</td>
\r
688 <td>Unfortunately we can't check the version number. <br>
\r
689 We try to find Numeric folder in ${PYTHONHOME}/lib/python2.2/site-packages/Numeric
\r
691 If you have problem with preinstalled version of numeric 22.0 reinstall
\r
695 <td bgcolor="#E4E4E4" class="whs15">
\r
696 <p class="whs3">Sip 3.3.2</td>
\r
697 <td>existence of SIPDIR <br>
\r
698 existence of sip <br>
\r
699 existence of libsip.so.9.1.0</td>
\r
700 <td>set SIPDIR to directory where you have sip preinstalled</td>
\r
701 <td>We try to find sip and libsip.so.9.1.0 in $SIPDIR folder if you set
\r
702 SIPDIR , otherwise searching is done using $PATH and $LD_LIBRARY_PATH
\r
704 It is recommended to use native Sip on Linux RedHat 8.0</td></tr>
\r
707 <td bgcolor="#E4E4E4" class="whs15">
\r
708 <p class="whs3">PyQt 3.3.2</td>
\r
709 <td>existence of PYQTDIR <br>
\r
710 existence of libqtxmlcmodule.so.1.0.0</td>
\r
711 <td>set PYQTDIR to directory where you have sip preinstalled</td>
\r
712 <td>Unfortunately we can't check the version number. <br>
\r
713 We try to find libqtxmlcmodule.so.1.0.0 in $PYQTDIR folder if you set PYQTDIR,
\r
714 otherwise searching is done using $LD_LIBRARY_PATH . <br>
\r
715 If you have problem with preinstalled version of PyQt 3.3.2 reinstall it.
\r
717 It is recommended to use native PyQt on Linux RedHat 8.0</td></tr>
\r
720 <td bgcolor="#E4E4E4" class="whs15">
\r
721 <p class="whs3">HappyDoc 2.1</td>
\r
722 <td>existence of happydoc <br>
\r
723 ver=`happydoc | grep "HappyDoc version 2.1"`</td>
\r
724 <td>set PYTHONHOME if you have preinstalled version of python</td>
\r
725 <td>We try to find happydoc in $PYTHONHOME/bin folder. <br>
\r
726 ver should not be empty. <br>
\r
727 This product is not obligatory. It was added only for your comfort.</td></tr>
\r
730 <td bgcolor="#E4E4E4" class="whs15">
\r
731 <p class="whs3">Doxygen 1.3-rc2</td>
\r
732 <td>existence of doxygen <br>
\r
733 existence of doxysearch <br>
\r
734 existence of doxytag <br>
\r
735 existence of doxywizard</td>
\r
736 <td>set QTDIR if you have preinstalled version of qt <br>
\r
737 set PATH on a directory where doxygen, doxysearch, doxytag and doxywizard
\r
739 <td>Unfortunately we can't check the version number. <br>
\r
740 It's necessary to have compiled Qt in order to build doxywizard. <br>
\r
741 If you have problem with preinstalled version of doxygen 1.3-rc2 reinstall
\r
743 This product is not obligatory. It was added only for your comfort.</td></tr>
\r
746 <td bgcolor="#E4E4E4" class="whs15">
\r
747 <p class="whs3">Graphviz 1.9</td>
\r
748 <td>existance of dot</td>
\r
749 <td>add GraphViz's bin directory to the PATH environment variable</td>
\r
750 <td>Unfortunately we can't check the version number. <br>
\r
751 We try to find dot program in the $PATH</td></tr>
\r
754 <td bgcolor="#E4E4E4" class="whs15">
\r
755 <p class="whs3">SALOME binaries</td>
\r
756 <td>existence of SALOME_ROOT_DIR <br>
\r
757 existence of VERSION file <br>
\r
758 ver=`cat $SALOME_ROOT_DIR/bin/VERSION | awk -F: '{print $2}' | tr -d '[:space:]'`</td>
\r
759 <td>set SALOME_ROOT_DIR if you have preinstalled binaries of SALOME version
\r
761 <td>SALOME binaries should exist and ver should be equal to 1.2</td></tr>
\r
764 <td bgcolor="#E4E4E4" class="whs15">
\r
765 <p class="whs3">SALOME sources</td>
\r
766 <td>existence of SALOMEPRO_SRC <br>
\r
767 existence of VERSION file <br>
\r
768 ver=`cat $SALOMEPRO_SRC/bin/VERSION | awk -F: '{print $2}' | tr -d '[:space:]'`</td>
\r
769 <td>set SALOMEPRO_SRC if you have preinstalled sources of SALOME version
\r
771 <td>SALOME sources should exist and ver should be equal to 1.2</td></tr>
\r
773 </div><p class="whs3"> </p>
\r
775 <p class="whs6"><img src="../note1.gif" x-maintain-ratio="TRUE" width="36px" height="38px" border="0" class="img_whs7">: For native products installation procedure sets proper environment
\r
776 variables itself, and you do not need to set such variables like, e.g.
\r
777 <b>TCLHOME</b> or <b>PYTHONHOME</b>. But if you have native products installed
\r
778 to different from default directories (not <b>/usr/bin</b>, <b>/usr/lib</b>),
\r
779 it is recommended to follow above description. </p>
\r
782 <!--(HR)============================================================-->
\r
783 <hr align="center" class="whs2">
\r
786 <h3 class="whs4"><a NAME=pick_up_env></a>Picking up the
\r
787 <font style="color: #ff0000;"
\r
788 color=#FF0000>environment</font></h3>
\r
790 <p class="whs8">Please, read carefully
\r
791 the following information. This section describes how the installation
\r
792 procedure collects environment. </p>
\r
794 <p class="whs8">After installing each
\r
795 product shell script creates in the product root folder special environment
\r
796 file with the name of the product but beginning from the dot, which includes
\r
797 all necessary product settings. For example for VTK-4.2 the file is<b>
\r
798 .VTK-4.2</b>. These files allows to pick up all environment settings which
\r
799 are necessary to build and launch SALOME. When you install SALOME sources
\r
800 and/or binaries, installation procedure looks through the target directory
\r
801 to pick up all the settings files and creates two scripts: <b>.salomesh</b>
\r
802 and <b>.salomecsh </b>for sh and csh correspondingly. Such approach helps
\r
803 to save time when reinstalling products and you may not to care about
\r
804 setting all environment variables manually. What you need is just to use
\r
805 one of these scripts. You even may not to add this script in your profile.
\r
806 Installation Wizard will do it for you if corresponding option is enabled
\r
807 (<i>"Do you want to update your profile?"</i> check box for
\r
808 Install Wizard and <tt>--update</tt> option for the script). </p>
\r
810 <p class="whs3">It also concerns those products, which
\r
811 are not currently installed. For example, you install some SALOME binaries
\r
812 to the directory where you have previously installed other products.
\r
813 Installation procedure still tries to collect environment files from the
\r
814 target directory if it finds the necessary products there. If some product
\r
815 is not found in the target directory the corresponding section of .salomesh/.salomecsh
\r
816 files will be skipped. However for native products (<b><i>gcc, tcl,
\r
817 python, qt, sip, pyqt)</i></b> instal script also tries to find them in
\r
818 the system directories. The corresponding section of <b>.salome*</b> files
\r
819 will contain special description, for example <i>"#------ native
\r
820 gcc is used ------"</i>. </p>
\r
822 <p class="whs3">You should take into account such behaviour
\r
823 of the installation procedure. Install script doesn't know itself which
\r
824 version of the product you want to use - native or preinstalled. You have
\r
825 possibility to change the order of searching the products by using special
\r
826 key: <i>"Prefer native products"</i> option for Wizard and <tt>--native</tt>
\r
827 key for the install script. In this case installation procedure will try
\r
828 to find products FIRST in your system folders and THEN in the target directory.
\r
831 <p class="whs3">Please, again bear in mind that described
\r
832 above concerns only those products WHICH ARE NOT CURRENTLY INSTALLED.
\r
835 <p class="whs3">In any case you may edit <b>.salome*</b>
\r
836 files after installation procedure finishes. </p>
\r
839 <!--(HR)============================================================-->
\r
840 <hr align="center" class="whs2">
\r
843 <p class="whs3"> </p>
\r
845 <p class="whs3"> </p>
\r
850 <a href="javascript:void(0);" onClick="var e; if (parseInt(navigator.appVersion)>=4){e=event;} if (parseInt(navigator.appVersion) >=2 && typeof(PopupMenu_Invoke) == 'function') PopupMenu_Invoke(e,'','About SALOME PRO architecture','about_salome_pro_architecture.htm','Introduction to SALOME PRO','introduction_to_salome_pro.htm','Running SALOME PRO','running_salome_pro.htm');return false;" title="Related Topics"><img src="../ss_btn_related_topics.gif" border=0 height=17 width=82 alt="Related Topics"></a></p>
\r
852 <p class="whs16"> </p>
\r
854 <p class="whs16"> </p>
\r
856 <p class="whs16"> </p>
\r
858 <p class="whs16"> </p>
\r
860 <p class="whs17"> </p>
\r
862 <script type="text/javascript" language="JavaScript" title="WebHelpRelatedTopics"><!--
\r
863 if (parseInt(navigator.appVersion) >= 3 && typeof (WritePopupMenuLayer) == "function")
\r
864 WritePopupMenuLayer();
\r
865 //--></script><script type="text/javascript" language="javascript1.2">
\r
867 if (window.writeIntopicBar)
\r
868 writeIntopicBar(0);
\r
