1 <!doctype HTML public "-//W3C//DTD HTML 4.0 Frameset//EN">
\r
6 <title>Installation Wizard</title>
\r
7 <meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
\r
8 <meta name="generator" content="RoboHelp by eHelp Corporation www.ehelp.com">
\r
9 <link rel="stylesheet" href="../default_ns.css"><script type="text/javascript" language="JavaScript" title="WebHelpSplitCss">
\r
11 if (navigator.appName !="Netscape")
\r
12 { document.write("<link rel='stylesheet' href='../default.css'>");}
\r
19 </style><style type="text/css">
\r
21 h1.whs1 { font-size:24pt; }
\r
22 hr.whs2 { float:aligncenter; }
\r
23 p.whs3 { background-color:#ffffff; }
\r
24 table.whs4 { x-cell-content-align:top; width:100%; border-spacing:0px; border-left-width:0px; border-left-color:#c0c0c0; border-left-style:Solid; border-top-width:0px; border-top-color:#c0c0c0; border-top-style:Solid; border-right-width:0px; border-right-color:#c0c0c0; border-right-style:Solid; border-bottom-width:0px; border-bottom-color:#c0c0c0; border-bottom-style:Solid; }
\r
25 col.whs5 { width:18.383%; }
\r
26 col.whs6 { width:81.617%; }
\r
27 tr.whs7 { x-cell-content-align:top; }
\r
28 td.whs8 { width:18.383%; padding-right:10px; padding-left:10px; border-left-color:#c0c0c0; border-top-color:#c0c0c0; border-top-style:Solid; border-bottom-color:#c0c0c0; border-bottom-width:1px; border-bottom-style:Solid; border-right-color:#c0c0c0; border-right-width:1px; border-right-style:Solid; border-left-width:1px; border-left-style:Solid; border-top-width:1px; }
\r
29 p.whs9 { font-weight:bold; }
\r
30 td.whs10 { width:81.617%; padding-right:10px; padding-left:10px; border-top-color:#c0c0c0; border-top-style:Solid; border-right-color:#c0c0c0; border-right-style:Solid; border-bottom-color:#c0c0c0; border-bottom-width:1px; border-bottom-style:Solid; border-top-width:1px; border-right-width:1px; }
\r
31 td.whs11 { width:18.383%; padding-right:10px; padding-left:10px; border-left-color:#c0c0c0; border-bottom-color:#c0c0c0; border-bottom-width:1px; border-bottom-style:Solid; border-right-color:#c0c0c0; border-right-width:1px; border-right-style:Solid; border-left-width:1px; border-left-style:Solid; }
\r
32 td.whs12 { width:81.617%; padding-right:10px; padding-left:10px; border-right-color:#c0c0c0; border-right-style:Solid; border-bottom-color:#c0c0c0; border-bottom-width:1px; border-bottom-style:Solid; border-right-width:1px; }
\r
33 td.whs13 { width:81.617%; padding-right:10px; padding-left:10px; border-right-style:Solid; border-right-color:#c0c0c0; border-bottom-color:#c0c0c0; border-bottom-width:1px; border-bottom-style:Solid; border-right-width:1px; }
\r
34 td.whs14 { width:18.383%; padding-right:10px; padding-left:10px; border-left-color:#c0c0c0; border-bottom-color:#c0c0c0; border-bottom-style:Solid; border-right-color:#c0c0c0; border-right-width:1px; border-right-style:Solid; border-left-width:1px; border-left-style:Solid; border-bottom-width:1px; }
\r
35 td.whs15 { width:81.617%; padding-right:10px; padding-left:10px; border-right-color:#c0c0c0; border-right-style:Solid; border-bottom-color:#c0c0c0; border-bottom-style:Solid; border-bottom-width:1px; border-right-width:1px; }
\r
36 p.whs16 { text-align:center; }
\r
37 img_whs17 { border:none; width:565px; height:525px; float:none; border-style:none; }
\r
38 p.whs18 { background-image:url('../texture_horiz_ltbluebubbles.jpg'); }
\r
39 img_whs19 { border:none; width:36px; height:38px; float:none; border-style:none; }
\r
40 img_whs20 { border:none; width:565px; height:525px; float:none; border-style:none; }
\r
41 img_whs21 { border:none; width:35px; height:37px; float:none; border-style:none; }
\r
42 table.whs22 { width:100%; border-left-style:Solid; border-left-width:1px; border-right-style:Solid; border-right-width:1px; border-top-style:Solid; border-top-width:1px; border-bottom-style:Solid; border-bottom-width:1px; border-left-color:#c0c0c0; border-right-color:#c0c0c0; border-top-color:#c0c0c0; border-bottom-color:#c0c0c0; }
\r
43 th.whs23 { border-left-color:#c0c0c0; border-left-width:1px; border-left-style:Solid; border-top-color:#c0c0c0; border-top-width:1px; border-top-style:Solid; border-right-color:#c0c0c0; border-right-width:1px; border-right-style:Solid; border-bottom-color:#c0c0c0; border-bottom-width:1px; border-bottom-style:Solid; }
\r
44 p.whs24 { font-size:12pt; }
\r
45 td.whs25 { border-left-color:#c0c0c0; border-left-width:1px; border-left-style:Solid; border-top-color:#c0c0c0; border-top-width:1px; border-top-style:Solid; border-right-color:#c0c0c0; border-right-width:1px; border-right-style:Solid; border-bottom-color:#c0c0c0; border-bottom-width:1px; border-bottom-style:Solid; }
\r
46 td.whs26 { x-cell-content-align:top; border-left-color:#c0c0c0; border-left-width:1px; border-left-style:Solid; border-top-color:#c0c0c0; border-top-width:1px; border-top-style:Solid; border-right-color:#c0c0c0; border-right-width:1px; border-right-style:Solid; border-bottom-color:#c0c0c0; border-bottom-width:1px; border-bottom-style:Solid; }
\r
47 p.whs27 { margin-right:2px; }
\r
48 img_whs28 { border:none; border-style:none; width:36px; height:38px; float:none; }
\r
50 </style><script type="text/javascript" language="JavaScript" title="WebHelpInlineScript">
\r
53 if (innerWidth != origWidth || innerHeight != origHeight)
\r
56 if ((parseInt(navigator.appVersion) == 4) && (navigator.appName == "Netscape")) {
\r
57 origWidth = innerWidth;
\r
58 origHeight = innerHeight;
\r
64 <style type="text/css">
\r
66 div.WebHelpPopupMenu { position:absolute; left:0px; top:0px; z-index:4; visibility:hidden; }
\r
68 </style><script type="text/javascript" language="javascript1.2" src="../whmsg.js"></script>
\r
69 <script type="text/javascript" language="javascript" src="../whver.js"></script>
\r
70 <script type="text/javascript" language="javascript1.2" src="../whproxy.js"></script>
\r
71 <script type="text/javascript" language="javascript1.2" src="../whutils.js"></script>
\r
72 <script type="text/javascript" language="javascript1.2" src="../whtopic.js"></script>
\r
74 <body><script type="text/javascript" language="javascript1.2">
\r
76 if (window.gbWhTopic)
\r
78 if (window.addTocInfo)
\r
80 addTocInfo("About SALOME\nInstalling SALOME");
\r
81 addButton("show",BTN_TEXT,"Show","","","","",0,0,"","","");
\r
84 if (window.writeBtnStyle)
\r
87 if (window.writeIntopicBar)
\r
90 if (window.setRelStartPage)
\r
92 setRelStartPage("../kernel.html");
\r
101 document.location.reload();
\r
104 <h1 class="whs1">Installing SALOME</h1>
\r
113 class=kadov-p><a href="#install_from_wizard">Installing products
\r
114 with the Installation Wizard</a></li>
\r
117 class=kadov-p><a href="#check_version_proc">Notes on check products
\r
118 version procedure</a></li>
\r
121 class=kadov-p><a href="#pick_up_env">Pick up the environment</a></li>
\r
124 class=kadov-p><a href="#xml_files">Modifying XML configuration
\r
127 <li class=kadov-p><p class="whs3"><a href="#new_products">Implementing
\r
128 installation scripts for the new products</a></p></li>
\r
135 <h3><a name=install_from_wizard></a>Installing products with the <font
\r
136 style="color: #ff0000;"
\r
137 color=#FF0000>Installation Wizard</font></h3>
\r
139 <p>You can run the Installation Wizard in two modes. It's root directory
\r
140 contains python script runInstall.py: </p>
\r
142 <p><b style="font-weight: bold;">[ python ] runInstall [ -g | b ] [ -f
\r
143 <xml-file> ] [ -t <target-dir> ] [ -tmp <tmp-dir> ]</b>
\r
148 <table x-use-null-cells cellspacing="0" width="100%" class="whs4">
\r
149 <script language='JavaScript'><!--
\r
150 if ((navigator.appName == "Netscape") && (parseInt(navigator.appVersion) == 4)) document.write("</table><table x-use-null-cells cellspacing='0' width='100%' border='1' bordercolor='silver' bordercolorlight='silver' bordercolordark='silver'>");
\r
155 <tr valign="top" class="whs7">
\r
156 <td width="18.383%" class="whs8">
\r
157 <p class="whs9"><b style="font-weight: bold;">-g</b></td>
\r
158 <td width="81.617%" class="whs10">
\r
159 <p>Runs the Installation Wizard in the GUI mode. In this case only <xml-file>
\r
160 key is taken into account. This option is used by default. </td></tr>
\r
162 <tr valign="top" class="whs7">
\r
163 <td width="18.383%" class="whs11">
\r
164 <p><b style="font-weight: bold;">-b</b></td>
\r
165 <td width="81.617%" class="whs12">
\r
166 <p>Runs the Installation Wizard in the batch mode. </td></tr>
\r
168 <tr valign="top" class="whs7">
\r
169 <td width="18.383%" class="whs11">
\r
170 <p><b style="font-weight: bold;">-f <xml-file></b></td>
\r
171 <td width="81.617%" class="whs12">
\r
172 <p>The configuration file to be used by the Installation Wizard.
\r
173 If this parameter is missed then the script tries to define the <i>Red
\r
174 Hat </i>version and uses corresponding xml file. For example, for the
\r
175 <i>Red Hat 8.0</i> <b>config_RedHat8_0.xml</b> file is supposed
\r
176 to be used by default. If the appropriate file is not found, <b>config.xml</b>
\r
177 is used by default. </td></tr>
\r
179 <tr valign="top" class="whs7">
\r
180 <td width="18.383%" class="whs11">
\r
181 <p> <b>-t <target-dir></b></td>
\r
182 <td width="81.617%" class="whs12">
\r
183 <p>The target directory, SALOME products to be installed to. If used, overloads
\r
184 target directory, given in the configuration xml file. </td></tr>
\r
186 <tr valign="top" class="whs7">
\r
187 <td colspan="1" rowspan="1" width="18.383%" class="whs11">
\r
188 <p><b style="font-weight: bold;">-tmp <tmp-dir></b></td>
\r
189 <td colspan="1" rowspan="1" width="81.617%" class="whs13">
\r
190 <p>The directory, which is used to contain temporary files. If used,
\r
191 overloads temporary directory, given in the configuration xml file.</td></tr>
\r
193 <tr valign="top" class="whs7">
\r
194 <td colspan="1" rowspan="1" width="18.383%" class="whs14">
\r
195 <p><b style="font-weight: bold;">-h</b></td>
\r
196 <td colspan="1" rowspan="1" width="81.617%" class="whs15">
\r
197 <p>Prints this help information. </td></tr>
\r
198 <script language='JavaScript'><!--
\r
199 if ((navigator.appName == "Netscape") && (parseInt(navigator.appVersion) == 4)) document.write("</table></table><table>");
\r
204 <b><br>
\r
207 <p>So, to run the Installation Wizard in the GUI mode, just type <b>runInstall</b>.
\r
212 <p>The installation procedure can support some different Linux platforms
\r
213 (currently it provides only configuration scripts for <i>RedHat-8.0</i>)
\r
214 and various number of products. The using of configuration xml files gives
\r
215 flexible way to modify the list of products to be installed by the Installation
\r
216 Wizard without changing program's source code. Just create your own configuration
\r
217 file and implement installation scripts for products you want to be provided
\r
218 by Wizard. See <a href="#xml_files">modifying XML configuration file</a>
\r
219 and <a href="#new_products">implementing installation scripts for the
\r
220 new products</a> for more information. </p>
\r
222 <p>The <font style="color: #ff0000;"
\r
223 color=#FF0000>Installation Wizard</font> was built with using
\r
224 of the <b><i>Qt </i></b>library. The program contains several pages.
\r
225 To navigate between pages use <i>"Next"</i> and <i>"Back"</i>
\r
226 buttons in the lower part of the wizard window. <i>"Cancel"</i>
\r
227 button closes dialog window and quits the installation procedure. To invoke
\r
228 this help information click <i>"Help"</i> button. </p>
\r
230 <p>Skip the first <i>"Introduction"</i> page by pressing <i>"Next"</i>
\r
233 <p>In the second page you are proposed to enter the target directory where
\r
234 all selected products will be installed to. You can also press <i>"Browse..."</i>
\r
235 button and choose the folder for installation using standard <b><i>Qt</i></b>
\r
236 browse directory dialog box. <br>
\r
237 If the directory you want to install products does not exist you will be
\r
238 prompted to confirm directory creation. If you type wrong directory path,
\r
239 or if you have no permission for the directory you use, the corresponding
\r
240 message box will raise. </p>
\r
242 <p>The Installation Wizard has two modes of the installation: basic and
\r
243 advanced. In the basic mode it is necessary just to enter target directory.
\r
244 If you want to use advanced mode, click <i>"More..."</i> button.
\r
247 <p>In the advanced mode you have the possibility to select products to
\r
248 be installed (see <a href="#ProductPage">Fig.1</a> ). Each product has
\r
249 several options of installation: you have a possibility to use native
\r
250 products, install already precompiled binaries, build product from the
\r
251 sources or not installed at all. Possible options and default choice are
\r
252 provided by the configuration file. You can mark the products, you want
\r
253 to install, by clicking the corresponding radiobuttons in the list view
\r
254 in the left part of the page. Note that some products can be installed
\r
255 only together with other products (or these prerequisite products should
\r
256 be already installed on your computer). The installation procedure has
\r
257 a special feature to automatically mark these products in the list view.
\r
258 For example, in order to install <b><i>pyqt</i></b> it's necessary to
\r
259 have <b><i>gcc, python</i></b>,<b><i> qt</i></b> and <b><i>sip</i></b>
\r
260 installed. Therefore all these products will be marked when you check
\r
261 on <b><i>pyqt</i></b>. This feature can be switched off by clicking <i>"Auto
\r
262 set prerequisites products"</i> checkbox. <br>
\r
263 Special button in the right part of the page - <i>"Unselect All"
\r
264 </i>- allows to reset quickly all products to the <i>"not install"</i>
\r
266 If you want to use native Linux Red Hat 8.0 products (these are gcc, tcl,
\r
267 Python, Qt, Sip and PyQt), select <i>"use native" </i>option.
\r
270 <p>The box at the right side of the page displays the information about
\r
271 currently highlighted product: name, version, short description (if provided),
\r
272 required disk space, temporary files disk space, list of prerequisites
\r
273 and user choice. </p>
\r
275 <a name=ProductPage></a>
\r
277 <p align="center" class="whs16"> </p>
\r
279 <p align="center" class="whs16"><span style="font-style: italic;"><I><img src="../pics/productpage.png" x-maintain-ratio="TRUE" width="565px" height="525px" border="0" class="img_whs17"></I></span>
\r
282 <p align="center" class="whs16"><b style="font-weight: bold;">Figure 1:</b> "Installation
\r
283 settings" page in the advanced mode</p>
\r
285 <p align="center" class="whs16"> </p>
\r
287 <p>The <i>"Total disk space required:"</i> field displays how
\r
288 much disk space on the hard drive is required for installation of selected
\r
295 <p class="whs18"><b
\r
296 style="font-weight: bold;"><img src="../note1.gif" x-maintain-ratio="TRUE" width="36px" height="38px" border="0" class="img_whs19"> </b>Please, take into account
\r
297 that displayed amount of required disk space is approximate and may differ
\r
298 when you install products on your hard drive. </p>
\r
302 <p>The installation procedure uses a special directory to store temporary
\r
303 files. The <i>"Space for temporary files:"</i> field shows the
\r
304 information about required disk space on the hard drive for extracting
\r
305 and compiling of the selected products. You can change the default directory
\r
306 - just type path to the folder you want to use or click on the corresponding
\r
307 <i>"Browse..."</i> button. </p>
\r
311 <p>The installation procedure also checks the available disk space on the
\r
312 selected directories according to the products selected. If there is no
\r
313 enough disk space on your hard drive you will see the corresponding error
\r
318 <p class="whs18"><span><b
\r
319 style="font-weight: bold;"><img src="../note1.gif" x-maintain-ratio="TRUE" width="36px" height="38px" border="0" class="img_whs19"></span> </b>Unfortunately, the
\r
320 configure procedure has a very annoying bug under Linux platform. The
\r
321 directory should be obligatory entered without spaces. For example, the
\r
322 configure procedure for <b><i>gcc</i></b> won't work if you pass the following
\r
323 parameter: <i>--prefix="/New Folder 1"</i>. <b>Therefore you
\r
324 are strongly recommended not to use directory names containing spaces.</b>
\r
329 <p>To proceed further click <i>"Next"</i> button. At this moment
\r
330 program will make some tests to check installation settings: if there
\r
331 is enough disk space on the hard drive, if native products are preinstalled,
\r
332 dependencies (prerequisites) for each product you have selected to be
\r
333 installed. If any test fails you will see corresponding warning message
\r
334 box. Otherwise wizard will follow to the next page: </p>
\r
338 <p align="center" class="whs16"><a name=ChoicePage></a><br>
\r
339 <img src="../pics/choicepage.png" x-maintain-ratio="TRUE" width="565px" height="525px" border="0" class="img_whs17"> </p>
\r
341 <p align="center" class="whs16"><b style="font-weight: bold;">Figure 2:</b> "Check
\r
342 your choice" page</p>
\r
344 <p align="center" class="whs16"> </p>
\r
346 <p>This page summarizes the installation settings you've made on the previous
\r
347 pages. You can check again your choice to change it if necessary. </p>
\r
351 <p>When you are sure that everything is OK, press <i>"Next"</i>
\r
352 button to follow to the <a href="#ProgressPage">next page</a>. </p>
\r
356 <a name=ProgressPage></a>
\r
358 <p align="center" class="whs16"><img src="../pics/progresspage.png" x-maintain-ratio="TRUE" width="565px" height="525px" border="0" class="img_whs20"> </p>
\r
360 <p align="center" class="whs16"><b style="font-weight: bold;">Figure 3:</b> "Installation
\r
361 progress" page</p>
\r
363 <p align="center" class="whs16"> </p>
\r
365 <p>To start installation of the selected products click <i>"Start"</i>
\r
366 button. It launches the shell installation script and you will be able
\r
367 to see the output of the script in the topmost dialog's frame. In case
\r
368 of any installation problems (for example, you have accidentally removed
\r
369 the temporary directory) the script will ask you: <i>"Would you like
\r
370 to continue : (Y,N) ?"</i>. You can answer this question by typing
\r
371 [Y] or [N] in the middle text edit control frame. </p>
\r
377 <p class="whs18"><b
\r
378 style="font-weight: bold;"><img src="../tip1.gif" x-maintain-ratio="TRUE" width="35px" height="37px" border="0" class="img_whs21"></b> press [Enter] when you finish
\r
383 <p>The <i>"Installation Status"</i> frame window shows you the
\r
384 progress of installation. It contains a list of all selected products
\r
385 with brief descriptions. "<font style="color: #ff0000;"
\r
386 color=#FF0000>Waiting</font>"
\r
387 description means that installation of this product have not started yet.
\r
388 Currently installing product is marked as "<font style="color: #ff9900;"
\r
389 color=#FF9900>Processing</font>".
\r
390 All installed products have "<font style="color: #33ff33;"
\r
391 color=#33FF33>Completed</font>"
\r
394 <p>You can abort installation and close the installation procedure using
\r
395 <i>"Cancel"</i> button. It sends the signal "SIGTERM"
\r
396 to the shell script. The script has a signal handler and will try to clear
\r
397 all temporary files. The process of removing temporary files can take
\r
398 some time, so the installation wizard will wait 3 seconds before closing.
\r
403 <p>At the end of installation (all selected products have been installed
\r
404 successfully) you can go back to the previous pages to start a new installation
\r
405 or click <i>"Next"</i> button to go the Readme page: </p>
\r
407 <p align="center" class="whs16"><a name=readmepage></a><br>
\r
408 <img src="../pics/readmepage.png" x-maintain-ratio="TRUE" width="565px" height="525px" border="0" class="img_whs20"></p>
\r
410 <p align="center" class="whs16"><b style="font-weight: bold;">Figure 4:</b> "Finish
\r
411 installation" page</p>
\r
413 <p align="center" class="whs16"> </p>
\r
415 <p>In this page you can read important information about the Instalation
\r
416 Wizard itself and some hints: how to run and test SALOME or how to build
\r
417 SALOME from the sources. This is the contents of the README file which
\r
418 you can find in the root directory of the Installation Wizard. </p>
\r
422 <p>You can also launch SALOME Desktop from this page by clicking <i>"Launch
\r
423 SALOME" </i>button. </p>
\r
425 <p>During the process of installation the script creates some environment
\r
426 files to simplify procedure of launching SALOME. These shell scripts set
\r
427 all necessary environment variables for all products you have installed.
\r
428 To learn how installation scripts collects the environment, see <a
\r
429 href="#pick_up_env"> here</a>. These files are: <b>salome.csh</b> + <b>salome.sh</b>
\r
430 in the <span style="font-style: italic;"><I><span style="font-weight: bold;"><B>KERNEL
\r
431 module</B></span></I></span><b><i> sources</i></b> and <span style="font-style: italic;"><I><span
\r
432 style="font-weight: bold;"><B>KERNEL</B></span></I></span><b><i> module binaries</i></b>
\r
433 root directories and <b>env_products.csh</b> + <b>env_products.sh </b>in
\r
434 the target directory. </p>
\r
440 <h3><a name=check_version_proc></a>Notes on<font style="color: #ff0000;"
\r
441 color=#FF0000> check products
\r
442 version</font> procedure</h3>
\r
444 <p>Unfortunately under Linux platform there is no exact algorithm to identify
\r
445 the product's version. The table below contains the information relating
\r
446 to checking preinstalled products for the Linux.RedHat 8.0 platform <br>
\r
449 <table nosave x-use-null-cells width="100%" class="whs22">
\r
452 <th nosave class="whs23">
\r
453 <p class="whs24">Product </th>
\r
454 <th nosave class="whs23">
\r
455 <p class="whs24">Algorithm of checking </th>
\r
456 <th nosave class="whs23">
\r
457 <p class="whs24">Preliminary steps before launching <br>
\r
458 of installation procedure </th>
\r
459 <th nosave class="whs23">
\r
460 <p class="whs24">Notes </th></tr>
\r
466 <p>ver=`/usr/bin/gcc --version | grep 'gcc (GCC) .*' | cut -b 11-13`</td>
\r
470 <p>ver should be equal 3.2 <br>
\r
471 It is recommended to use native gcc on Linux RedHat 8.0</td></tr>
\r
476 <td nosave class="whs25">
\r
477 <p>existence of TCLHOME <br>
\r
478 existence of tclsh8.3 <br>
\r
479 existence of wish8.3 <br>
\r
480 existence of libtcl8.3.so <br>
\r
481 existence of libtk8.3.so <br>
\r
482 existence of libtclx8.3.so <br>
\r
483 existence of libtkx8.3.so</td>
\r
485 <p>set TCLHOME if you have preinstalled version of tcl. <br>
\r
486 set LD_LIBRARY_PATH on a directory where libs can be found.</td>
\r
488 <p>It is recommended to use native tcl on Linux RedHat 8.0</td></tr>
\r
491 <td valign="top" class="whs26">
\r
492 <p>boost 1.30.2</td>
\r
493 <td valign="top" class="whs26">
\r
494 <p>ver=`egrep 'BOOST_VERSION [0-9]+' ${BOOSTDIR}/boost/version.hpp | sed
\r
495 's/.*BOOST_VERSION \([0-9]\+\)/\1/g'`</td>
\r
496 <td valign="top" class="whs26">
\r
497 <p>set BOOSTDIR if you have preinstalled version of boost</td>
\r
498 <td valign="top" class="whs26">
\r
499 <p>It is impossible to use native BOOST and to install BOOST from binaries.</td></tr>
\r
503 <p>Cascade 5.1.2</td>
\r
505 <p>existence of CASROOT environment variable</td>
\r
507 <p>set CASROOT if you have preinstalled version of CASCADE</td>
\r
509 <p>Unfortunately we can't say anything exactly about CASCADE 5.1.2 and
\r
510 we only check CASROOT environment variable. If you have problem with preinstalled
\r
511 version of CASCADE reinstall it</td></tr>
\r
515 <p>Python 2.2.1</td>
\r
517 <p>existence of PYTHONHOME <br>
\r
518 isPython=`which python` <br>
\r
519 ver=`python -V`</td>
\r
521 <p>set PYTHONHOME to root Python folder <br>
\r
522 set PATH on a directory where python can be found</td>
\r
524 <p>Python should exist and ver should be equal to 2.2.1 <br>
\r
525 It is recommended to use native Python on Linux RedHat 8.0</td></tr>
\r
531 <p>existence of libGL.so.1.2.030402</td>
\r
533 <p>set LD_LIBRARY_PATH on a directory where libGL.so.1.2.030402 can be
\r
536 <p>You have a possibility to build products (vtk & qt) with Mesa drivers
\r
537 from the package supplied with this installation procedure or to use OpenGL
\r
538 drivers installed on your computer locally. This check procedure concerns
\r
539 only supplied Mesa driver.</td></tr>
\r
543 <p>Swig 1.3.17</td>
\r
545 <p>isSwig=`which swig` <br>
\r
546 ver=`swig -version` <br>
\r
547 ver=`echo $ver | awk '{print $3}'`</td>
\r
549 <p>set PATH on a directory where swig can be found</td>
\r
551 <p>Swig should exist and ver should be equal to 1.3.17</td></tr>
\r
557 <p>existence of QTDIR <br>
\r
558 existence of libqt-mt.so.3.0.5</td>
\r
560 <p>set QTDIR if you have preinstalled version of qt</td>
\r
562 <p>We try to find libqt-mt.so.3.0.5 in ${QTDIR}/lib folder. <br>
\r
563 You should set MESA_HOME only if you have preinstalled version of Mesa
\r
565 It is recommended to use native Qt on Linux RedHat 8.0</td></tr>
\r
571 <p>existence of QWTHOME <br>
\r
572 existence of libqwt.so.0.4.1</td>
\r
574 <p>set QWTHOME if you have preinstalled version of qwt</td>
\r
576 <p>We try to find libqwt.so.0.4.1 in the ${QWTHOME}/lib folder. </td></tr>
\r
580 <p>Hdf 5-1.4.4</td>
\r
582 <p>existence of HDF5HOME <br>
\r
583 existence of libhdf5.so.0.0.0 <br>
\r
584 existence of libhdf5.settings</td>
\r
586 <p>set HDF5HOME if you have preinstalled version of hdf</td>
\r
588 <p>We try to find libhdf5.so.0.0.0 and libhdf5.settings in ${HDF5HOME}/lib
\r
590 File libhdf5.settings should contain the following entry: <br>
\r
591 HDF5 Version: 1.4.4</td></tr>
\r
597 <p>existence of MED2HOME <br>
\r
598 existence of libmed.so.0.0.0</td>
\r
600 <p>set MED2HOME if you have preinstalled version of med</td>
\r
602 <p>Unfortunately we can't check version number. <br>
\r
603 We try to find libmed.so.0.0.0 in ${MED2HOME}/lib folder. <br>
\r
604 If you have problem with preinstalled version of med reinstall it.</td></tr>
\r
610 <p>existence of VTKHOME <br>
\r
611 existence of libvtkCommon.so</td>
\r
613 <p>set VTKHOME if you have preinstalled version of vtk</td>
\r
615 <p>Unfortunately we can't check the version number. <br>
\r
616 We try to find libvtkCommon.so in ${VTKHOME}/lib/vtk folder. <br>
\r
617 If you have problem with preinstalled version of vtk reinstall it.</td></tr>
\r
620 <td valign="top" class="whs26">
\r
622 <td valign="top" class="whs26">
\r
623 <p>existence of NETGENROOT</td>
\r
624 <td valign="top" class="whs26">
\r
625 <p>set NETGENROOT if you have preinstalled version of Netgen.</td>
\r
626 <td valign="top" class="whs26">
\r
627 <p>Unfortunarely we can't find anything about netgen version.<br>
\r
628 We just check if NETGENROOT environment varible is set.</td></tr>
\r
632 <p>OmniORB 3.0.5, <br>
\r
633 OmniORBpy 1.5, <br>
\r
634 OmniNotify 1.2</td>
\r
636 <p>existence of OMNIORBDIR <br>
\r
637 existence of libomniORB3.so.0.5 <br>
\r
638 existence of _omnipymodule.so.0.5 <br>
\r
639 existence of libCOSNotify3.so.0.5 <br>
\r
640 existence of notifd <br>
\r
641 existence of THIS_IS_omniORB_3_0_5 <br>
\r
642 existence of THIS_IS_omniNotify_1_2 <br>
\r
643 existence of THIS_IS_OMNIORBPY_1_5</td>
\r
645 <p>set OMNIORBDIR if you have preinstalled version of omni</td>
\r
647 <p>We try to find libomniORB3.so.0.5, _omnipymodule.so.0.5 and libCOSNotify3.so.0.5
\r
648 in ${OMNIORBDIR}/lib/i586_linux_2.0_glibc2.1 folder. <br>
\r
649 We try to find notifd in ${OMNIORBDIR}/bin/i586_linux_2.0_glibc2.1 folder.
\r
651 Additional checking - omni add special files THIS_IS_... <br>
\r
652 We try to find THIS_IS_omniORB_3_0_5 in ${OMNIORBDIR} folder. <br>
\r
653 We try to find THIS_IS_omniNotify_1_2 in ${OMNIORBDIR}/src/services/omniNotify.
\r
655 We try to find THIS_IS_OMNIORBPY_1_5 in ${OMNIORBDIR}/src/lib/omniORBpy
\r
660 <p>Numeric 22.0</td>
\r
662 <p>existence of Numeric folder <br>
\r
663 existence of _numpy.so</td>
\r
665 <p>set PYTHONHOME if you have preinstalled version of python</td>
\r
667 <p>Unfortunately we can't check the version number. <br>
\r
668 We try to find Numeric folder in ${PYTHONHOME}/lib/python2.2/site-packages/Numeric
\r
670 If you have problem with preinstalled version of numeric 22.0 reinstall
\r
677 <p>existence of SIPDIR <br>
\r
678 existence of sip <br>
\r
679 existence of libsip.so.9.1.0</td>
\r
681 <p>set SIPDIR to directory where you have sip preinstalled</td>
\r
683 <p>We try to find sip and libsip.so.9.1.0 in $SIPDIR folder if you set
\r
684 SIPDIR , otherwise searching is done using $PATH and $LD_LIBRARY_PATH
\r
686 It is recommended to use native Sip on Linux RedHat 8.0</td></tr>
\r
692 <p>existence of PYQTDIR <br>
\r
693 existence of libqtxmlcmodule.so.1.0.0</td>
\r
695 <p>set PYQTDIR to directory where you have sip preinstalled</td>
\r
697 <p>Unfortunately we can't check the version number. <br>
\r
698 We try to find libqtxmlcmodule.so.1.0.0 in $PYQTDIR folder if you set PYQTDIR,
\r
699 otherwise searching is done using $LD_LIBRARY_PATH . <br>
\r
700 If you have problem with preinstalled version of PyQt 3.3.2 reinstall it.
\r
702 It is recommended to use native PyQt on Linux RedHat 8.0</td></tr>
\r
706 <p>HappyDoc 2.1</td>
\r
708 <p>existence of happydoc <br>
\r
709 ver=`happydoc | grep "HappyDoc version 2.1"`</td>
\r
711 <p>set PYTHONHOME if you have preinstalled version of python</td>
\r
713 <p>We try to find happydoc in $PYTHONHOME/bin folder. <br>
\r
714 ver should not be empty. <br>
\r
715 This product is not obligatory. It was added only for your comfort.</td></tr>
\r
719 <p class="whs27">Doxygen 1.3-rc2</td>
\r
721 <p>existence of doxygen <br>
\r
722 existence of doxysearch <br>
\r
723 existence of doxytag <br>
\r
724 existence of doxywizard</td>
\r
726 <p>set QTDIR if you have preinstalled version of qt <br>
\r
727 set PATH on a directory where doxygen, doxysearch, doxytag and doxywizard
\r
730 <p>Unfortunately we can't check the version number. <br>
\r
731 It's necessary to have compiled Qt in order to build doxywizard. <br>
\r
732 If you have problem with preinstalled version of doxygen 1.3-rc2 reinstall
\r
734 This product is not obligatory. It was added only for your comfort.</td></tr>
\r
738 <p>Graphviz 1.9</td>
\r
740 <p>existence of dot</td>
\r
742 <p>add GraphViz's bin directory to the PATH environment variable</td>
\r
744 <p>Unfortunately we can't check the version number. <br>
\r
745 We try to find dot program in the $PATH</td></tr>
\r
749 <p>MODULE binaries<br>
\r
750 (MODULE=KERNEL,</p>
\r
753 <p>existence of MODULE_ROOT_DIR <br>
\r
754 existence of VERSION file <br>
\r
755 ver=`cat $MODULE_ROOT_DIR/bin/salome/VERSION | awk -F: '{print $2}' | tr
\r
756 -d '[:space:]'`</td>
\r
758 <p>set MODULE_ROOT_DIR if you have preinstalled binaries of MODULE version
\r
761 <p>MODULE binaries should exist and ver should be equal to 1.4.x</td></tr>
\r
765 <p>MODULE sources<br>
\r
766 (MODULE=KERNEL,</p>
\r
769 <p>existence of MODULE_SRC_DIR <br>
\r
770 existence of VERSION file <br>
\r
771 ver=`cat $MODULE_SRC/bin/VERSION | awk -F: '{print $2}' | tr -d '[:space:]'`</td>
\r
773 <p>set MODULE_SRC_DIR if you have preinstalled sources of MODULE version
\r
776 <p>MODULE sources should exist and ver should be equal to 1.4.x</td></tr>
\r
781 <p class="whs18"><b
\r
782 style="font-weight: bold;"><img src="../note1.gif" x-maintain-ratio="TRUE" width="36px" height="38px" border="0" class="img_whs19"></b> For native products installation
\r
783 procedure sets proper environment variables itself, and you do not need
\r
784 to set such variables like, e.g. <b>TCLHOME</b> or <b>PYTHONHOME</b>.
\r
786 If you have native products installed to different from default directories
\r
787 (not <b>/usr/bin</b>, <b>/usr/lib</b>...), it is recommended to follow
\r
788 above description. Or you should set properly $PATH and $LD_LIBRARY_PATH
\r
789 variables <b><font style="color: #ff0000;"
\r
790 color=#FF0000>before</font></b> starting Installation
\r
791 Wizard. Otherwise installation script will fail to find preinstalled products.
\r
798 <h3><a name=pick_up_env></a>Pick up the <font style="color: #ff0000;"
\r
799 color=#FF0000>environment</font></h3>
\r
801 <p>Please, read carefully the following information. This section describes
\r
802 how the installation procedure collects environment. </p>
\r
804 <p>After installing each product shell script creates in the product root
\r
805 folder special environment file. The name of the file is generated from
\r
806 the name of product by the following scheme: <b>env_<product_name>.sh.</b>
\r
807 This file includes all necessary product settings. For example for Vtk
\r
808 the file is <b>env_Vtk.sh</b>. Environment files allows to pick up all
\r
809 environment settings which are necessary to build and launch SALOME. When
\r
810 installing SALOME sources and/or binaries, installation procedure picks
\r
811 up all the settings files and generate two scripts: <b>salome.sh</b> and
\r
812 <b>salome.csh </b>for sh and csh correspondingly. Such approach helps
\r
813 to save time when reinstalling products and you may not to care about
\r
814 setting all environment variables manually to build/launch SALOME. What
\r
815 you need is just to use one of these scripts. </p>
\r
817 <p>This concerns also those products which are not currently installed.
\r
818 For example, you install some SALOME binaries to the directory where you
\r
819 have previously installed other products. Installation procedure
\r
820 still tries to collect environment files from the target directory if
\r
821 it find necessary products there. If some product is not found in the
\r
822 target directory the corresponding section of <b>salome.sh/salome.csh</b>
\r
823 files will be skipped. <br>
\r
824 For native products (<i><b>gcc, tcl, python, qt, sip, pyqt </b>for RedHat-8.0<b>)</b></i>
\r
825 instal script tries to find them using <b>$PATH</b> / <b>$LD_LIBRARY_PATH</b>
\r
826 variables and then in the system default directories (<b>/usr/bin, /usr/lib</b>
\r
827 etc., depending on the product). </p>
\r
829 <p>In any case you may edit <b>salome.*</b> files after installation procedure
\r
830 finishes, as you want. </p>
\r
836 <h3><a name=xml_files></a>Modifying <font style="color: #ff0000;"
\r
837 color=#FF0000>XML</font> configuration
\r
838 <font style="color: #ff0000;"
\r
839 color=#FF0000>file</font></h3>
\r
841 <p>You can create your own configuration. Installation Wizard then can
\r
842 take it as command line argument to provide list of products you want
\r
843 to install with it. The list of products and some another settings for
\r
844 the Installation Wizard are provided in xml file. The default file which
\r
845 Installation Wizard looks for if no command line arguments ar given, is
\r
846 <b>config.xml</b>. This section describes the format of configuration
\r
848 Xml tags are in bold blue, optional sections/tags are in brackets. </p>
\r
852 <p><b style="font-weight: bold;"><font style="color: #000099;"
\r
853 color=#000099><document></font></b>
\r
854 <font style="color: #000000;"
\r
855 color=#000000><b><br>
\r
856 </b>[</font><b><font style="color: #000099;"
\r
857 color=#000099><config</font></b><font
\r
858 style="color: #000000;"
\r
859 color=#000000> [version=<install_wizard_version>]</font> <font
\r
860 style="color: #000000;"
\r
862
\r
863 [caption=<install_wizard_caption>]</font> <font style="color: #000000;"
\r
865
\r
866 [copyright=<install_wizard_copyright>]</font> <font style="color: #000000;"
\r
868
\r
869 [license=<install_wizard_license_info>]</font> <font style="color: #000000;"
\r
871
\r
872 [os=<target_paltform>]</font><b><font style="color: #000099;"
\r
873 color=#000099>/></font></b><font
\r
874 style="color: #000000;"
\r
875 color=#000000>]</font> <font style="color: #000000;"
\r
876 color=#000000><b><br>
\r
877 </b>[</font><b><font style="color: #000099;"
\r
878 color=#000099><path</font></b><font
\r
879 style="color: #000000;"
\r
880 color=#000000> [targetdir=<target_directory>]</font> <font style="color: #000000;"
\r
882
\r
883 [tempdir=<temp_directory>]</font><b><font style="color: #000099;"
\r
884 color=#000099>/></font></b><font
\r
885 style="color: #000000;"
\r
886 color=#000000>]</font> <font style="color: #000000;"
\r
888 [</font><b><font style="color: #000099;"
\r
889 color=#000099><product</font></b><font
\r
890 style="color: #000000;"
\r
891 color=#000000> name=<product_name></font> <font style="color: #000000;"
\r
893
\r
894 version=<product_version></font> <br>
\r
895
\r
896 [description=<product_description>]<font
\r
897 style="color: #000000;"
\r
899
\r
900 install=<installation_mode></font> <font style="color: #000000;"
\r
902
\r
903 supported=<supported_installation_modes></font> <font style="color: #000000;"
\r
905
\r
906 disable=<disable_flag><br>
\r
907
\r
908 [pickupenv=<pickup_env_flag>]</font><font style="color: #000000;"
\r
910
\r
911 dependancies=<list_of_prerequisites></font> <font style="color: #000000;"
\r
913
\r
914 installdiskspace=<install_disk_space></font> <font style="color: #000000;"
\r
916
\r
917 temporarydiskspace=<tmp_disk_space></font> <font style="color: #000000;"
\r
919
\r
920 script=<installation_script_name></font><font style="color: #000099;"
\r
921 color=#000099>/<b>></b></font><font
\r
922 style="color: #000000;"
\r
923 color=#000000>]</font> <font style="color: #000000;"
\r
925 [</font><b><font style="color: #000099;"
\r
926 color=#000099><product</font></b><font
\r
927 style="color: #000000;"
\r
928 color=#000000> ... </font><font style="color: #000099;"
\r
929 color=#000099>/<b>></b></font><font
\r
930 style="color: #000000;"
\r
931 color=#000000>]</font> <font style="color: #000000;"
\r
933 <b> .</b></font><b><font style="color: #000099;"
\r
934 color=#000099>..</font></b>
\r
935 <b><font style="color: #000099;"
\r
937 </document></font></b> </p>
\r
939 <h4><font style="color: #000000;"
\r
940 color=#000000><config> section</font></h4>
\r
942 <p><font style="color: #000000;"
\r
943 color=#000000>This is optional section - contains general information
\r
944 Installation Wizard itself.</font> </p>
\r
948 <li style="/*begin!kadov{{*/ color: #000000; /*}}end!kadov*/ "
\r
949 class=kadov-p><p><font style="color: #000000;"
\r
950 color=#000000><b style="font-weight: bold;">version</b>:
\r
951 Installation Wizard's version number;</font></p></li>
\r
953 <li style="/*begin!kadov{{*/ color: #000000; /*}}end!kadov*/ "
\r
954 class=kadov-p><p><font style="color: #000000;"
\r
955 color=#000000><b style="font-weight: bold;">caption</b>:
\r
956 Installation Wizard's main window title - if this string contains '%1'
\r
957 text - the title will contain in this place version number (see above);</font></p></li>
\r
959 <li style="/*begin!kadov{{*/ color: #000000; /*}}end!kadov*/ "
\r
960 class=kadov-p><p><font style="color: #000000;"
\r
961 color=#000000><b style="font-weight: bold;">copyright</b>:
\r
962 Installation Wizard's copyright information (appears on the first page
\r
963 of program);</font></p></li>
\r
965 <li style="/*begin!kadov{{*/ color: #000000; /*}}end!kadov*/ "
\r
966 class=kadov-p><p><font style="color: #000000;"
\r
967 color=#000000><b style="font-weight: bold;">license</b>:
\r
968 Installation Wizard's license information (appears on the first page of
\r
969 program);</font></p></li>
\r
971 <li class=kadov-p><p><b style="font-weight: bold;">os</b>: Contains
\r
972 directory name (relative from ./Products/BINARIES) where Installation
\r
973 Wizard should search precompiled binaries packages. If this tag is skipped,
\r
974 binaries are implied to be in the ./Products/BINARIES directory.</p></li>
\r
979 <p><b style="font-weight: bold;"><path> section</b></p>
\r
983 <p>This is optional section - contains default directories. </p>
\r
989 <li style="/*begin!kadov{{*/ color: #000000; /*}}end!kadov*/ "
\r
990 class=kadov-p><p><font style="color: #000000;"
\r
991 color=#000000><b style="font-weight: bold;">targetdir</b>:
\r
992 Starting target directory - path to the directory where products should
\r
993 be installed;</font></p></li>
\r
995 <li class=kadov-p><p><b style="font-weight: bold;">tempdir</b>: Starting
\r
996 temp directory - path to the directory for the temporary files.</p></li>
\r
1001 <p><b style="font-weight: bold;"><product> section</b></p>
\r
1005 <p>This section describes product to be installed with the Installation
\r
1006 Wizard. All tags are obligatory. Products appears in the products tree
\r
1007 and are installed in the order they are described in the configuration
\r
1008 file. It is recommended to insert native products at the top of the list
\r
1009 before all other products. </p>
\r
1016 style="/*begin!kadov{{*/ color: #000000; /*}}end!kadov*/ "
\r
1017 class=kadov-p><font style="color: #000000;"
\r
1018 color=#000000><b style="font-weight: bold;">name</b>:
\r
1019 Name of the product;</font></li>
\r
1022 style="/*begin!kadov{{*/ color: #000000; /*}}end!kadov*/ "
\r
1023 class=kadov-p><font style="color: #000000;"
\r
1024 color=#000000><b style="font-weight: bold;">version</b>:
\r
1025 Version of the product;</font></li>
\r
1028 style="/*begin!kadov{{*/ color: #000000; /*}}end!kadov*/ "
\r
1029 class=kadov-p><font style="color: #000000;"
\r
1030 color=#000000><span style="font-weight: bold;"><B>description</B></span>:
\r
1031 Description of the product (optional);</font></li>
\r
1034 style="/*begin!kadov{{*/ color: #000000; /*}}end!kadov*/ "
\r
1035 class=kadov-p><font style="color: #000000;"
\r
1036 color=#000000><b style="font-weight: bold;">supported</b>:
\r
1037 Supported modes of installation, should contain one or more of the following
\r
1038 options, separated by comma: <i>install sources</i>, <i>install binaries</i>,
\r
1039 <i>use native</i>. Installation script should contain corresponding functions
\r
1040 for each of supported installation modes;</font></li>
\r
1043 style="/*begin!kadov{{*/ color: #000000; /*}}end!kadov*/ "
\r
1044 class=kadov-p><font style="color: #000000;"
\r
1045 color=#000000><b style="font-weight: bold;">install</b>:
\r
1046 Default (starting) installation mode;</font></li>
\r
1049 style="/*begin!kadov{{*/ color: #000000; /*}}end!kadov*/ "
\r
1050 class=kadov-p><font style="color: #000000;"
\r
1051 color=#000000><b style="font-weight: bold;">disable</b>:
\r
1052 If this flag has 'true' value, corresponding product will not appear in
\r
1053 the list of products tree and will not be installed;</font></li>
\r
1056 class=kadov-p><b style="font-weight: bold;">pickupenv</b>: This
\r
1057 flag points that pickup environment procedure should be performed for
\r
1058 this module. If this flag equal to <b>true</b>, salome.sh and salome.csh
\r
1059 files will be created in the product's installation directory. This
\r
1060 is optional key, default value is <b>false.</b></li>
\r
1063 style="/*begin!kadov{{*/ color: #000000; /*}}end!kadov*/ "
\r
1064 class=kadov-p><font style="color: #000000;"
\r
1065 color=#000000><b style="font-weight: bold;">dependancies</b>:
\r
1066 list of prerequisite products, which are necessary to build this product,
\r
1067 separated by comma;</font></li>
\r
1070 style="/*begin!kadov{{*/ color: #000000; /*}}end!kadov*/ "
\r
1071 class=kadov-p><font style="color: #000000;"
\r
1072 color=#000000><b style="font-weight: bold;">installdiskspace</b>:
\r
1073 Total amount space (integer, in Kbytes), which product occupies on the
\r
1074 hard drive after the installation;</font></li>
\r
1077 style="/*begin!kadov{{*/ color: #000000; /*}}end!kadov*/ "
\r
1078 class=kadov-p><font style="color: #000000;"
\r
1079 color=#000000><b style="font-weight: bold;">temporarydiskspace</b>:
\r
1080 Disk space (integer, in Kbytes) for the temporary files, which is necessary
\r
1081 to build the product from the sources;</font></li>
\r
1084 class=kadov-p><b style="font-weight: bold;">script</b>: Installation
\r
1085 script name. This script is in charge of installation of the product.
\r
1086 It is called when necessary from the main program. See <a href="#new_products">next
\r
1087 section</a> for more information.</li>
\r
1092 <p class="whs18"><span
\r
1093 style="font-weight: bold;"><B><img src="../note1.gif" x-maintain-ratio="TRUE" width="36px" height="38px" border="0" class="img_whs19"></B></span> If you add new products
\r
1094 to be installed with Installation Wizard, you should also provide installation
\r
1095 script for this product. See next section for more details. </p>
\r
1101 <h3><a name=new_products></a>Implementing <font style="color: #ff0000;"
\r
1102 color=#FF0000>installation
\r
1103 scripts</font> for the new products</h3>
\r
1105 <p>When you want some product to be installed with the Installation Wizard,
\r
1106 you should add it's description it <a href="#xml_files">in the configuration
\r
1107 file</a> and create bash installation script, following described in this
\r
1108 section rules. <br>
\r
1109 There are some obligatory functions to be provided in this installation
\r
1110 script. These functions are automatically called by master installation
\r
1111 script or/and GUI shell when it is necessary.<br>
\r
1112 File <b>common.sh</b> contains some service functions which can be used
\r
1113 in your installation script, like <b>make_env()</b>,<b> make_dir()</b>,
\r
1114 <b>try_existing()</b>, <b>sort_path()</b>,<b> find_in_path()</b>, etc.
\r
1122 class=kadov-p><b style="font-weight: bold;">check_version()</b>:
\r
1123 This function allows to check the version of the product already installed
\r
1124 on the computer. It should try to find product (native or preinstalled
\r
1125 in the target directory) and check it version. This helps to avoid unnecessary
\r
1126 reinstallation. This is internal function and is not called</li>
\r
1129 class=kadov-p><b style="font-weight: bold;"><font style="color: #000000;"
\r
1130 color=#000000>try_native()</font></b><font
\r
1131 style="color: #000099;"
\r
1132 color=#000099>: </font><font style="color: #000000;"
\r
1133 color=#000000>This function is called when
\r
1134 <i>'use native' </i>installation mode is selected by the user. The function
\r
1135 should try to find native version of the product and define possibility
\r
1136 of it usage. Should create environment for the product in the temporary
\r
1137 directory (see also description of <b>print_env(</b>) function). If you
\r
1138 do not provide native mode installation, you can omit this function.</font></li>
\r
1141 style="/*begin!kadov{{*/ color: #000000; /*}}end!kadov*/ "
\r
1142 class=kadov-p><font style="color: #000000;"
\r
1143 color=#000000><b style="font-weight: bold;">install_source()</b>:
\r
1144 This function is called when <i>'install sources</i>' installation mode
\r
1145 is selected by the user. The function is responsible for the building
\r
1146 of the product from the sources package. Should create environment for
\r
1147 the product in the temporary directory (see also description of <b>print_env(</b>)
\r
1148 function). If you do not provide sources mode installation, you can omit
\r
1149 this function</font></li>
\r
1152 style="/*begin!kadov{{*/ color: #000000; /*}}end!kadov*/ "
\r
1153 class=kadov-p><font style="color: #000000;"
\r
1154 color=#000000><b style="font-weight: bold;">install_binary()</b>:
\r
1155 This function is called when <i>'install binaries'</i> installation mode
\r
1156 is selected by the user. The function is responsible for the extracting
\r
1157 of the product from the binaries package. Should create environment for
\r
1158 the product in the temporary directory (see also description of <b>print_env(</b>)
\r
1159 function). If you do not provide binaries mode installation, you can omit
\r
1160 this function.</font></li>
\r
1163 class=kadov-p><b style="font-weight: bold;">try_preinstalled()</b>:
\r
1164 <font style="color: #000000;"
\r
1165 color=#000000>This function is called when<i> 'not install'</i>
\r
1166 installation mode is selected by the user. In this case script should
\r
1167 inspect target directory to try to find already preinstalled product,
\r
1168 pick up and check environment from there. See <a href="#pick_up_env">here</a>
\r
1169 for more details.</font></li>
\r
1172 class=kadov-p><font style="color: #000000;"
\r
1173 color=#000000><b style="font-weight: bold;">print_env()</b>:
\r
1174 This function is in charge of creation environment script. It should create
\r
1175 file with name </font><b>env_<product_name>.sh</b> in the temporary
\r
1176 directory and then copy it into the product installation directory. The
\r
1177 file should contain all necessary environment variables settings for the
\r
1178 product. It will be collected during the 'pick-up-environment' procedure.</li>
\r
1181 class=kadov-p><b style="font-weight: bold;">pickup-env()</b>: This
\r
1182 procedure corresponds <b>pickupenv</b> tag of the configuration xml file
\r
1183 (see previous section). Should call <b>make_env</b> procedure to perform
\r
1184 pick-up environment procedure for the product.</li>
\r
1189 <p><font style="color: #000000;"
\r
1190 color=#000000>The calling signature of the product installation
\r
1191 script is following:</font> <b><font style="color: #000000;"
\r
1192 color=#000000><br>
\r
1193 <product_script_name> <function_name> <temp_folder> <products_directory>
\r
1194 <target_directory> <dependancies> <product_name></font></b>
\r
1197 <p><font style="color: #000000;"
\r
1198 color=#000000>where</font> <font style="color: #000000;"
\r
1199 color=#000000><b><br>
\r
1200 <product_script_name></b> - installation script name (described in
\r
1201 configuration xml file);</font> <font style="color: #000000;"
\r
1202 color=#000000><b><br>
\r
1203 <function_name></b> - the name of function, corresponding to the
\r
1204 selected installation mode: <i>try_native, install_source, install_binary</i>
\r
1205 or <i>try_preinstalled</i>;</font> <font style="color: #000000;"
\r
1206 color=#000000><b><br>
\r
1207 <temp_folder></b> - temporary files directory;</font> <font style="color: #000000;"
\r
1208 color=#000000><b><br>
\r
1209 <products_directory></b> - directory where the sources/binaries package
\r
1210 can be found. You should provide sources package in the <i><Install_Wizard_root_directory>/Products/SOURCES</i>
\r
1211 directory and binaries package in the <i><InstallWizard_root_directory>/Products/BINARIES/<os_version></i>,
\r
1212 where <os_version> is target platform description, which appears
\r
1213 in the corresponding section of the <a href="#xml_files">configuration
\r
1214 xml file</a>.</font> <font style="color: #000000;"
\r
1215 color=#000000><b><br>
\r
1216 <target_directory></b> - root target directory where product should
\r
1217 be installed to;</font> <font style="color: #000000;"
\r
1218 color=#000000><b><br>
\r
1219 <dependancies></b> - single-quoted list of prerequisite products,
\r
1220 separated by space;</font> <font style="color: #000000;"
\r
1221 color=#000000><b><br>
\r
1222 <product_name> </b>- product name itself.</font> </p>
\r
1226 <p class="whs18"><i><img src="../pics/exemple.gif" x-maintain-ratio="TRUE" width="36px" height="38px" border="0" class="img_whs28">med-2.1.6.sh install_binary /tmp/work ./Products/BINARIES/RedHat8.0
\r
1227 /usr/salome 'gcc Hdf' med</i> </p>
\r
1229 <p class="whs18"><font
\r
1230 style="color: #000000;"
\r
1231 color=#000000>Copy created script into the <i><Install_Wizard_root_directory>/config_files</i>
\r
1232 sub-directory where all installation scripts are stored. Installation
\r
1233 Wizard will automatically search and call your script during the installation
\r
1234 procedure.</font> </p>
\r
1245 <script type="text/javascript" language="javascript1.2">
\r
1247 if (window.writeIntopicBar)
\r
1248 writeIntopicBar(0);
\r
