Attachment #5515 for issue #13097

View | Details | Raw Unified | Return to issue 13097
Collapse All | Expand All




<p>
Commands you have to type on the keyboard 
follow this syntax throughout this document:
</p>

<LinuxSolarisWin_tcsh>
<p>
<pre>
<KBD>config_office> ./configure</KBD>
</pre>

<p> 
In this example, the script <CODE>configure</CODE> is executed 
in the directory <CODE>config_office</CODE>.
</p>
</LinuxSolarisWin_tcsh>

<Windows>
<p>
<pre>
<KBD>D:\my\source> winenv.bat</KBD>
</pre>

Links to the different sources are given in the document. 
</p>

<br><br><br>





<li>
<a href="#Overview">Overview</a>
</li>

<ul>


Project</a>
</li>

</ul></li>

<li>
<a href="#BuildRequirements">Build Requirements</a>
</li>

<ul>


the Build Environment and Build Tools</a>
</li>

</ul></li>

<li>
<a href="#BuildInstructions">Build Instructions</a>
</li>

<ul>


a Project with Debug Information</a>
</li>

</ul></li>

<li> 
<a href="#InstallInstructions">Instructions to 


</ul>

<br><br><br>


<h2>

<a href="#BuildingIndividualProjects">Building Individual Projects with a 
Prebuild</a>. 

<br><br><br>


<h2>

Before you start building, you must ensure that your system satisfies the
recommended software and hardware requirements for the type of system you
are working on. For <Linux>Linux, </Linux> <Solaris>Solaris, </Solaris> 
<Win_tcsh>Windows, </Win_tcsh> <Windows>Windows, </Windows> these are as follows:</p>

<p>
<Linux>
<b>Software Requirements</b>


    Should be in place with most Linux distributions. 
  </li>

  <li>
  PAM (should come with most Linux distributions)
  </li>


</Solaris>

<WindowsWin_tcsh>
<p><b>Build Requirements</b></p>

<ul>
  <li>

    <b>Note:</b> Before you use 4NT, you must ensure that the initialization
    file <CODE>4nt.ini</CODE> is present in the 4NT application directory. The
    following code sample shows the content of the <CODE>4nt.ini</CODE> file:
    </p>
<pre>
[4NT]
CommandSep = ^

   <p>
    Not all Cygwin packages are needed to build OpenOffice.org, but make sure
    that the following packages are installed.
    <div style="margin-left: 2em">
     bison<br>
     gawk<br>
     gzip<br>

     tar<br>
     perl<br>
     zip
    </div>
  </li>
</Win_tcsh>


    <a href="http://download.microsoft.com/download/platformsdk/Redist/1.0/W9XMe/EN-US/unicows.exe">
    http://download.microsoft.com/download/platformsdk/Redist/1.0/W9XMe/EN-US/unicows.exe</a>.
    For technical details see 
    <a href="http://porting.openoffice.org/servlets/ReadMsg?msgId=116287&amp;listName=dev">
    http://porting.openoffice.org/servlets/ReadMsg?msgId=116287&amp;listName=dev</a> and  
    <a href="http://porting.openoffice.org/servlets/ProjectDocumentList?dcID=515&amp;action=download">
    http://porting.openoffice.org/servlets/ProjectDocumentList?dcID=515&amp;action=download</a>. 
    (This only affects 643 builds.)
  </li>



</ul>
</WindowsWin_tcsh> 
<br><br>


<h2>

The code contains some further external components which are already provided. 
If you are interested in details about these, look at the External Components 
webpage at 
<a href="http://tools.openoffice.org/ext_comp.html">http://tools.openoffice.org/ext_comp.html</a>.</p>

<br><br><br>




(<a href="http://www.openoffice.org/dev_docs/source/download.html">http://www.openoffice.org/dev_docs/source/download.html</a>),
e.g. <CODE>oo_643B_src.tar.gz</CODE> in case of the 643B release.
<p>
Unpack the tarballs as follows (for the example 643B):</p>
<pre>
<KBD>> gunzip oo_643B_src.tar.gz</KBD>
<KBD>> tar -xvf oo_643B_src.tar</KBD>
<KBD>> cd oo_643B_src</KBD> 
</pre>
<p>This will be $SRC_ROOT from now on.</p>
</p>
</li>

<li>


</ul>

<br><br><br>




CC and CXX point to your c and c++ compiler:
</p>

</LinuxSolaris>
<Linux>
<pre>
<KBD>CC=/your/path/to/gcc</KBD>

<KBD>CXX=/your/path/to/CC</KBD>
</pre>
</Solaris><LinuxSolaris>
</p>

To run the <CODE>configure</CODE> script, type the following command:

<p>To run the <CODE>configure</CODE> script, type the following command:</p>

<pre>
<KBD>$SRC_ROOT> cd config_office</KBD>
<KBD>config_office> ./configure</KBD>

<p>
The following should demonstrate in detail what steps have to be done to 
set up the environment. For this examples we assume that
  <p>
  <ul>
    <li>
      the source code is in <CODE>C:\oo643B</CODE>

    </li>
  </ul>

<ul>
<H3>tcsh - Example</H3>
<b>As the use of the tcsh shell is still experimental, you have to enable it
with <CODE>--with-use-shell=tcsh</CODE></b>

<p>
To run the <CODE>configure</CODE> script, type the following command:

<p>
<pre>
<KBD>$SRC_ROOT> cd config_office</KBD>
<KBD>config_office> ./configure --with-cl-home=/cygdrive/c/PROGRA~1/MICROS~3/VC98 --with-asm-home=/cygdrive/c/ml --with-jdk-home=/cygdrive/c/jdk1.3.1 --with-use-shell=tcsh</KBD>
</pre>
</ul>
</Win_tcsh>

<LinuxSolarisWin_tcsh><p>
There are a number of options that you can use with the
<CODE>configure</CODE>
script. To display these options, type the following command:
</p>

<p>
<pre>
<KBD>config_office> ./configure --help</KBD>
</pre>

<Windows>
<p>
The following should demonstrate in detail what steps have to be done to 
set up the environment:</p> 

<ul>
  <li>
  <p>
  Run the configure script according to the following example. We 
  assume here that</p> 

  <p>
  <ul>

    <li>

<CODE>configure</CODE> script. To display these options, type 
the following command:

<p>
<pre>
<KBD>config_office> bash configure --help</KBD>
</pre>

<p> 
After running <CODE>configure</CODE>, you have to source the configuration 
file which sets all environment variables: 
</p>
<pre>
<KBD>$SRC_ROOT> tcsh</KBD>
</LinuxSolarisWin_tcsh>
<Linux><KBD>$SRC_ROOT> source LinuxIntelEnv.Set</KBD></Linux>
<Solaris><KBD>$SRC_ROOT> source SolarisSparcEnv.Set</KBD></Solaris>
<Win_tcsh><KBD>$SRC_ROOT> source winenv.set</KBD></Win_tcsh><LinuxSolarisWin_tcsh>

<p>
To create the build tools, type the following command:

<p>
<pre>
<KBD>$SRC_ROOT> ./bootstrap</KBD>
</pre>

This involves already building some modules and will take a few minutes.
</LinuxSolarisWin_tcsh>

<br><br><br>


<H2>

<p>
The following table shows the time required to build on a system with a 
particular specification. You can use these details to estimate the time
required to build on your system.</p>

<p>
<Linux>
<table BORDER="1" CELLSPACING=0 CELLPADDING=5>
  <tr VALIGN=TOP>

  </tr>
</table>
</Solaris>
<WindowsWin_tcsh>
<table BORDER="1" CELLSPACING=0 CELLPADDING=5>
  <tr VALIGN=TOP>
    <td>Architecture</td>

    <td>~10 h</td>
  </tr>
</table>
</WindowsWin_tcsh> 


<H2>

usually <VAR>module-name</VAR><CODE>/util</CODE> which is responsible for 
linking one or more shared libraries.

<br><br><br>


<H2>

<KBD>$SRC_ROOT/(module)> build debug=true</KBD>
</pre>

<br><br><br>

<h2>
<a NAME="InstallInstructions"></a>Instructions to Build 

in the installation project webpage.
</p>

<br><br><br>


<H2>

<Linux><CODE>$SRC_ROOT/solver/641/unxlngi4.pro/pck</CODE>.</Linux><Solaris><CODE>$SRC_ROOT/solver/641/unxsols3.pro/pck</CODE>.</Solaris><WindowsWin_tcsh><CODE>$SRC_ROOT/solver/641/wntmsci7.pro/pck</CODE>.</WindowsWin_tcsh>
</pre>

<p>
The filenames of these files contain a number code for the language, corresponding to 
the international phone code of a country in which that language is mainly spoken. 
For instance, the file <CODE>

<p>
Having unzipped the helpcontent files in there, building of installation sets can be 
resumed or repeated (in case you already have build some), as described in the previous 
chapter. English installation sets will be located in</p> 

<pre>
<CODE>$SRC_ROOT/instsetoo/<Linux>unxlngi3.pro</Linux><Solaris>unxsols3.pro</Solaris><WindowsWin_tcsh>wntmsci7.pro</WindowsWin_tcsh>/01/normal</CODE>, 

<CODE>$SRC_ROOT/instsetoo/<Linux>unxlngi3.pro</Linux><Solaris>unxsols3.pro</Solaris><WindowsWin_tcsh>wntmsci7.pro</WindowsWin_tcsh>/33/normal</CODE>.
</pre>

<p>Similarily, you will find 49 for German, 34 for Spanish, etc.</p>

<p>
Localised help content is not yet available for all languages. In such cases, the english 

appear in english. 
</p>

<br><br><br>


</body>

Return to issue 13097

Lines 24-32 Link Here

(-)build_template.html (-57 / +44 lines)
24	<p>	24	<p>
25	Commands you have to type on the keyboard	25	Commands you have to type on the keyboard
26	follow this syntax throughout this document:	26	follow this syntax throughout this document:
		27	</p>
27		28
28	<LinuxSolarisWin_tcsh>	29	<LinuxSolarisWin_tcsh>
29	<p>
30	<pre>	30	<pre>
31	<KBD>config_office> ./configure</KBD>	31	<KBD>config_office> ./configure</KBD>
32	</pre>	32	</pre>
Lines 34-43 Link Here
34	<p>	34	<p>
35	In this example, the script <CODE>configure</CODE> is executed	35	In this example, the script <CODE>configure</CODE> is executed
36	in the directory <CODE>config_office</CODE>.	36	in the directory <CODE>config_office</CODE>.
		37	</p>
37	</LinuxSolarisWin_tcsh>	38	</LinuxSolarisWin_tcsh>
38		39
39	<Windows>	40	<Windows>
40	<p>
41	<pre>	41	<pre>
42	<KBD>D:\my\source> winenv.bat</KBD>	42	<KBD>D:\my\source> winenv.bat</KBD>
43	</pre>	43	</pre>
Lines 60-66 Link Here
60	Links to the different sources are given in the document.	60	Links to the different sources are given in the document.
61	</p>	61	</p>
62		62
63	<br><p><br><p><br><p>	63	<br><br><br>
64		64
65		65
66		66
Lines 70-76 Link Here
70		70
71	<li>	71	<li>
72	<a href="#Overview">Overview</a>	72	<a href="#Overview">Overview</a>
73	</li>
74		73
75	<ul>	74	<ul>
76		75
Lines 83-93 Link Here
83	Project</a>	82	Project</a>
84	</li>	83	</li>
85		84
86	</ul>	85	</ul></li>
87		86
88	<li>	87	<li>
89	<a href="#BuildRequirements">Build Requirements</a>	88	<a href="#BuildRequirements">Build Requirements</a>
90	</li>
91		89
92	<ul>	90	<ul>
93		91
Lines 104-114 Link Here
104	the Build Environment and Build Tools</a>	102	the Build Environment and Build Tools</a>
105	</li>	103	</li>
106		104
107	</ul>	105	</ul></li>
108		106
109	<li>	107	<li>
110	<a href="#BuildInstructions">Build Instructions</a>	108	<a href="#BuildInstructions">Build Instructions</a>
111	</li>
112		109
113	<ul>	110	<ul>
114		111
Lines 126-132 Link Here
126	a Project with Debug Information</a>	123	a Project with Debug Information</a>
127	</li>	124	</li>
128		125
129	</ul>	126	</ul></li>
130		127
131	<li>	128	<li>
132	<a href="#InstallInstructions">Instructions to	129	<a href="#InstallInstructions">Instructions to
Lines 139-145 Link Here
139		136
140	</ul>	137	</ul>
141		138
142	<br><p><br><p><br><p>	139	<br><br><br>
143		140
144		141
145	<h2>	142	<h2>
Lines 275-281 Link Here
275	<a href="#BuildingIndividualProjects">Building Individual Projects with a	272	<a href="#BuildingIndividualProjects">Building Individual Projects with a
276	Prebuild</a>.	273	Prebuild</a>.
277		274
278	<br><p><br><p><br><p>	275	<br><br><br>
279		276
280		277
281	<h2>	278	<h2>
Lines 286-294 Link Here
286	Before you start building, you must ensure that your system satisfies the	283	Before you start building, you must ensure that your system satisfies the
287	recommended software and hardware requirements for the type of system you	284	recommended software and hardware requirements for the type of system you
288	are working on. For <Linux>Linux, </Linux> <Solaris>Solaris, </Solaris>	285	are working on. For <Linux>Linux, </Linux> <Solaris>Solaris, </Solaris>
289	<Win_tcsh>Windows, </Win_tcsh> <Windows>Windows, </Windows> these are as follows:	286	<Win_tcsh>Windows, </Win_tcsh> <Windows>Windows, </Windows> these are as follows:</p>
290		287
291	<p>
292	<Linux>	288	<Linux>
293	<b>Software Requirements</b>	289	<b>Software Requirements</b>
294		290
Lines 308-314 Link Here
308	Should be in place with most Linux distributions.	304	Should be in place with most Linux distributions.
309	</li>	305	</li>
310		306
311	</li>	307	<li>
312	PAM (should come with most Linux distributions)	308	PAM (should come with most Linux distributions)
313	</li>	309	</li>
314		310
Lines 378-384 Link Here
378	</Solaris>	374	</Solaris>
379		375
380	<WindowsWin_tcsh>	376	<WindowsWin_tcsh>
381	<p><b>Build Requirements</b><p>	377	<p><b>Build Requirements</b></p>
382		378
383	<ul>	379	<ul>
384	<li>	380	<li>
Lines 398-404 Link Here
398	<b>Note:</b> Before you use 4NT, you must ensure that the initialization	394	<b>Note:</b> Before you use 4NT, you must ensure that the initialization
399	file <CODE>4nt.ini</CODE> is present in the 4NT application directory. The	395	file <CODE>4nt.ini</CODE> is present in the 4NT application directory. The
400	following code sample shows the content of the <CODE>4nt.ini</CODE> file:	396	following code sample shows the content of the <CODE>4nt.ini</CODE> file:
401	<p>	397	</p>
402	<pre>	398	<pre>
403	[4NT]	399	[4NT]
404	CommandSep = ^	400	CommandSep = ^
Lines 481-487 Link Here
481	<p>	477	<p>
482	Not all Cygwin packages are needed to build OpenOffice.org, but make sure	478	Not all Cygwin packages are needed to build OpenOffice.org, but make sure
483	that the following packages are installed.	479	that the following packages are installed.
484	<ul>	480	<div style="margin-left: 2em">
485	bison<br>	481	bison<br>
486	gawk<br>	482	gawk<br>
487	gzip<br>	483	gzip<br>
Lines 489-495 Link Here
489	tar<br>	485	tar<br>
490	perl<br>	486	perl<br>
491	zip	487	zip
492	</ul>	488	</div>
493	</li>	489	</li>
494	</Win_tcsh>	490	</Win_tcsh>
495		491
Lines 539-548 Link Here
539	<a href="http://download.microsoft.com/download/platformsdk/Redist/1.0/W9XMe/EN-US/unicows.exe">	535	<a href="http://download.microsoft.com/download/platformsdk/Redist/1.0/W9XMe/EN-US/unicows.exe">
540	http://download.microsoft.com/download/platformsdk/Redist/1.0/W9XMe/EN-US/unicows.exe</a>.	536	http://download.microsoft.com/download/platformsdk/Redist/1.0/W9XMe/EN-US/unicows.exe</a>.
541	For technical details see	537	For technical details see
542	<a href="http://porting.openoffice.org/servlets/ReadMsg?msgId=116287&listName=dev">	538	<a href="http://porting.openoffice.org/servlets/ReadMsg?msgId=116287&listName=dev">
543	http://porting.openoffice.org/servlets/ReadMsg?msgId=116287&listName=dev</a> and	539	http://porting.openoffice.org/servlets/ReadMsg?msgId=116287&listName=dev</a> and
544	<a href="http://porting.openoffice.org/servlets/ProjectDocumentList?dcID=515&action=download">	540	<a href="http://porting.openoffice.org/servlets/ProjectDocumentList?dcID=515&action=download">
545	http://porting.openoffice.org/servlets/ProjectDocumentList?dcID=515&action=download</a>.	541	http://porting.openoffice.org/servlets/ProjectDocumentList?dcID=515&action=download</a>.
546	(This only affects 643 builds.)	542	(This only affects 643 builds.)
547	</li>	543	</li>
548		544
Lines 619-625 Link Here
619		615
620	</ul>	616	</ul>
621	</WindowsWin_tcsh>	617	</WindowsWin_tcsh>
622	<p><br><p><br><p>	618	<br><br>
623		619
624		620
625	<h2>	621	<h2>
Lines 630-638 Link Here
630	The code contains some further external components which are already provided.	626	The code contains some further external components which are already provided.
631	If you are interested in details about these, look at the External Components	627	If you are interested in details about these, look at the External Components
632	webpage at	628	webpage at
633	<a href="http://tools.openoffice.org/ext_comp.html">http://tools.openoffice.org/ext_comp.html</a>.	629	<a href="http://tools.openoffice.org/ext_comp.html">http://tools.openoffice.org/ext_comp.html</a>.</p>
634		630
635	<br><p><br><p><br><p>	631	<br><br><br>
636		632
637		633
638		634
Lines 650-663 Link Here
650	(<a href="http://www.openoffice.org/dev_docs/source/download.html">http://www.openoffice.org/dev_docs/source/download.html</a>),	646	(<a href="http://www.openoffice.org/dev_docs/source/download.html">http://www.openoffice.org/dev_docs/source/download.html</a>),
651	e.g. <CODE>oo_643B_src.tar.gz</CODE> in case of the 643B release.	647	e.g. <CODE>oo_643B_src.tar.gz</CODE> in case of the 643B release.
652	<p>	648	<p>
653	Unpack the tarballs as follows (for the example 643B):	649	Unpack the tarballs as follows (for the example 643B):</p>
654	<pre>	650	<pre>
655	<KBD>> gunzip oo_643B_src.tar.gz</KBD>	651	<KBD>> gunzip oo_643B_src.tar.gz</KBD>
656	<KBD>> tar -xvf oo_643B_src.tar</KBD>	652	<KBD>> tar -xvf oo_643B_src.tar</KBD>
657	<KBD>> cd oo_643B_src</KBD>	653	<KBD>> cd oo_643B_src</KBD>
658	</pre>	654	</pre>
659	This will be $SRC_ROOT from now on.	655	<p>This will be $SRC_ROOT from now on.</p>
660	</p>
661	</li>	656	</li>
662		657
663	<li>	658	<li>
Lines 718-724 Link Here
718		713
719	</ul>	714	</ul>
720		715
721	<br><p><br><p><br><p>	716	<br><br><br>
722		717
723		718
724		719
Lines 772-778 Link Here
772	CC and CXX point to your c and c++ compiler:	767	CC and CXX point to your c and c++ compiler:
773	</p>	768	</p>
774		769
775	<p></LinuxSolaris>	770	</LinuxSolaris>
776	<Linux>	771	<Linux>
777	<pre>	772	<pre>
778	<KBD>CC=/your/path/to/gcc</KBD>	773	<KBD>CC=/your/path/to/gcc</KBD>
Lines 785-795 Link Here
785	<KBD>CXX=/your/path/to/CC</KBD>	780	<KBD>CXX=/your/path/to/CC</KBD>
786	</pre>	781	</pre>
787	</Solaris><LinuxSolaris>	782	</Solaris><LinuxSolaris>
788	</p>
789		783
790	To run the <CODE>configure</CODE> script, type the following command:
791		784
792	<p>	785	<p>To run the <CODE>configure</CODE> script, type the following command:</p>
		786
793	<pre>	787	<pre>
794	<KBD>$SRC_ROOT> cd config_office</KBD>	788	<KBD>$SRC_ROOT> cd config_office</KBD>
795	<KBD>config_office> ./configure</KBD>	789	<KBD>config_office> ./configure</KBD>
Lines 802-808 Link Here
802	<p>	796	<p>
803	The following should demonstrate in detail what steps have to be done to	797	The following should demonstrate in detail what steps have to be done to
804	set up the environment. For this examples we assume that	798	set up the environment. For this examples we assume that
805	<p>
806	<ul>	799	<ul>
807	<li>	800	<li>
808	the source code is in <CODE>C:\oo643B</CODE>	801	the source code is in <CODE>C:\oo643B</CODE>
Lines 824-830 Link Here
824	</li>	817	</li>
825	</ul>	818	</ul>
826		819
827	<ul>
828	<H3>tcsh - Example</H3>	820	<H3>tcsh - Example</H3>
829	<b>As the use of the tcsh shell is still experimental, you have to enable it	821	<b>As the use of the tcsh shell is still experimental, you have to enable it
830	with <CODE>--with-use-shell=tcsh</CODE></b>	822	with <CODE>--with-use-shell=tcsh</CODE></b>
Lines 832-851 Link Here
832	<p>	824	<p>
833	To run the <CODE>configure</CODE> script, type the following command:	825	To run the <CODE>configure</CODE> script, type the following command:
834		826
835	<p>
836	<pre>	827	<pre>
837	<KBD>$SRC_ROOT> cd config_office</KBD>	828	<KBD>$SRC_ROOT> cd config_office</KBD>
838	<KBD>config_office> ./configure --with-cl-home=/cygdrive/c/PROGRA~1/MICROS~3/VC98 --with-asm-home=/cygdrive/c/ml --with-jdk-home=/cygdrive/c/jdk1.3.1 --with-use-shell=tcsh</KBD>	829	<KBD>config_office> ./configure --with-cl-home=/cygdrive/c/PROGRA~1/MICROS~3/VC98 --with-asm-home=/cygdrive/c/ml --with-jdk-home=/cygdrive/c/jdk1.3.1 --with-use-shell=tcsh</KBD>
839	</pre>	830	</pre>
840	</ul>
841	</Win_tcsh>	831	</Win_tcsh>
842		832
843	</LinuxSolarisWin_tcsh><p>	833	<LinuxSolarisWin_tcsh><p>
844	There are a number of options that you can use with the	834	There are a number of options that you can use with the
845	<CODE>configure</CODE>	835	<CODE>configure</CODE>
846	script. To display these options, type the following command:	836	script. To display these options, type the following command:
		837	</p>
847		838
848	<p>
849	<pre>	839	<pre>
850	<KBD>config_office> ./configure --help</KBD>	840	<KBD>config_office> ./configure --help</KBD>
851	</pre>	841	</pre>
Lines 854-868 Link Here
854	<Windows>	844	<Windows>
855	<p>	845	<p>
856	The following should demonstrate in detail what steps have to be done to	846	The following should demonstrate in detail what steps have to be done to
857	set up the environment:	847	set up the environment:</p>
858		848
859	<ul>	849	<ul>
860	<li>	850	<li>
861	<p>	851	<p>
862	Run the configure script according to the following example. We	852	Run the configure script according to the following example. We
863	assume here that	853	assume here that</p>
864		854
865	<p>
866	<ul>	855	<ul>
867		856
868	<li>	857	<li>
Lines 944-950 Link Here
944	<CODE>configure</CODE> script. To display these options, type	933	<CODE>configure</CODE> script. To display these options, type
945	the following command:	934	the following command:
946		935
947	<p>
948	<pre>	936	<pre>
949	<KBD>config_office> bash configure --help</KBD>	937	<KBD>config_office> bash configure --help</KBD>
950	</pre>	938	</pre>
Lines 955-964 Link Here
955	<p>	943	<p>
956	After running <CODE>configure</CODE>, you have to source the configuration	944	After running <CODE>configure</CODE>, you have to source the configuration
957	file which sets all environment variables:	945	file which sets all environment variables:
958	<p>	946	</p>
959	<pre>	947	<pre>
960	<KBD>$SRC_ROOT> tcsh</KBD>	948	<KBD>$SRC_ROOT> tcsh</KBD>
961	</LinuxSolaris>	949	</LinuxSolarisWin_tcsh>
962	<Linux><KBD>$SRC_ROOT> source LinuxIntelEnv.Set</KBD></Linux>	950	<Linux><KBD>$SRC_ROOT> source LinuxIntelEnv.Set</KBD></Linux>
963	<Solaris><KBD>$SRC_ROOT> source SolarisSparcEnv.Set</KBD></Solaris>	951	<Solaris><KBD>$SRC_ROOT> source SolarisSparcEnv.Set</KBD></Solaris>
964	<Win_tcsh><KBD>$SRC_ROOT> source winenv.set</KBD></Win_tcsh><LinuxSolarisWin_tcsh>	952	<Win_tcsh><KBD>$SRC_ROOT> source winenv.set</KBD></Win_tcsh><LinuxSolarisWin_tcsh>
Lines 1005-1011 Link Here
1005	<p>	993	<p>
1006	To create the build tools, type the following command:	994	To create the build tools, type the following command:
1007		995
1008	<p>
1009	<pre>	996	<pre>
1010	<KBD>$SRC_ROOT> ./bootstrap</KBD>	997	<KBD>$SRC_ROOT> ./bootstrap</KBD>
1011	</pre>	998	</pre>
Lines 1015-1021 Link Here
1015	This involves already building some modules and will take a few minutes.	1002	This involves already building some modules and will take a few minutes.
1016	</LinuxSolarisWin_tcsh>	1003	</LinuxSolarisWin_tcsh>
1017		1004
1018	<br><p><br><p><br><p>	1005	<br><br><br>
1019		1006
1020		1007
1021	<H2>	1008	<H2>
Lines 1050-1058 Link Here
1050	<p>	1037	<p>
1051	The following table shows the time required to build on a system with a	1038	The following table shows the time required to build on a system with a
1052	particular specification. You can use these details to estimate the time	1039	particular specification. You can use these details to estimate the time
1053	required to build on your system.	1040	required to build on your system.</p>
1054		1041
1055	<p>
1056	<Linux>	1042	<Linux>
1057	<table BORDER="1" CELLSPACING=0 CELLPADDING=5>	1043	<table BORDER="1" CELLSPACING=0 CELLPADDING=5>
1058	<tr VALIGN=TOP>	1044	<tr VALIGN=TOP>
Lines 1109-1115 Link Here
1109	</tr>	1095	</tr>
1110	</table>	1096	</table>
1111	</Solaris>	1097	</Solaris>
1112	<Windows>	1098	<WindowsWin_tcsh>
1113	<table BORDER="1" CELLSPACING=0 CELLPADDING=5>	1099	<table BORDER="1" CELLSPACING=0 CELLPADDING=5>
1114	<tr VALIGN=TOP>	1100	<tr VALIGN=TOP>
1115	<td>Architecture</td>	1101	<td>Architecture</td>
Lines 1136-1142 Link Here
1136	<td>~10 h</td>	1122	<td>~10 h</td>
1137	</tr>	1123	</tr>
1138	</table>	1124	</table>
1139	</Windows>	1125	</WindowsWin_tcsh>
1140		1126
1141		1127
1142	<H2>	1128	<H2>
Lines 1220-1226 Link Here
1220	usually <VAR>module-name</VAR><CODE>/util</CODE> which is responsible for	1206	usually <VAR>module-name</VAR><CODE>/util</CODE> which is responsible for
1221	linking one or more shared libraries.	1207	linking one or more shared libraries.
1222		1208
1223	<br><p><br><p><br><p>	1209	<br><br><br>
1224		1210
1225		1211
1226	<H2>	1212	<H2>
Lines 1241-1247 Link Here
1241	<KBD>$SRC_ROOT/(module)> build debug=true</KBD>	1227	<KBD>$SRC_ROOT/(module)> build debug=true</KBD>
1242	</pre>	1228	</pre>
1243		1229
1244	<br><p><br><p><br><p>	1230	<br><br><br>
1245		1231
1246	<h2>	1232	<h2>
1247	<a NAME="InstallInstructions"></a>Instructions to Build	1233	<a NAME="InstallInstructions"></a>Instructions to Build
Lines 1287-1293 Link Here
1287	in the installation project webpage.	1273	in the installation project webpage.
1288	</p>	1274	</p>
1289		1275
1290	<br><p><br><p><br><p>	1276	<br><br><br>
1291		1277
1292		1278
1293	<H2>	1279	<H2>
Lines 1316-1321 Link Here
1316	<Linux><CODE>$SRC_ROOT/solver/641/unxlngi4.pro/pck</CODE>.</Linux><Solaris><CODE>$SRC_ROOT/solver/641/unxsols3.pro/pck</CODE>.</Solaris><WindowsWin_tcsh><CODE>$SRC_ROOT/solver/641/wntmsci7.pro/pck</CODE>.</WindowsWin_tcsh>	1302	<Linux><CODE>$SRC_ROOT/solver/641/unxlngi4.pro/pck</CODE>.</Linux><Solaris><CODE>$SRC_ROOT/solver/641/unxsols3.pro/pck</CODE>.</Solaris><WindowsWin_tcsh><CODE>$SRC_ROOT/solver/641/wntmsci7.pro/pck</CODE>.</WindowsWin_tcsh>
1317	</pre>	1303	</pre>
1318		1304
		1305	<p>
1319	The filenames of these files contain a number code for the language, corresponding to	1306	The filenames of these files contain a number code for the language, corresponding to
1320	the international phone code of a country in which that language is mainly spoken.	1307	the international phone code of a country in which that language is mainly spoken.
1321	For instance, the file <CODE>	1308	For instance, the file <CODE>
Lines 1328-1334 Link Here
1328	<p>	1315	<p>
1329	Having unzipped the helpcontent files in there, building of installation sets can be	1316	Having unzipped the helpcontent files in there, building of installation sets can be
1330	resumed or repeated (in case you already have build some), as described in the previous	1317	resumed or repeated (in case you already have build some), as described in the previous
1331	chapter. English installation sets will be located in	1318	chapter. English installation sets will be located in</p>
1332		1319
1333	<pre>	1320	<pre>
1334	<CODE>$SRC_ROOT/instsetoo/<Linux>unxlngi3.pro</Linux><Solaris>unxsols3.pro</Solaris><WindowsWin_tcsh>wntmsci7.pro</WindowsWin_tcsh>/01/normal</CODE>,	1321	<CODE>$SRC_ROOT/instsetoo/<Linux>unxlngi3.pro</Linux><Solaris>unxsols3.pro</Solaris><WindowsWin_tcsh>wntmsci7.pro</WindowsWin_tcsh>/01/normal</CODE>,
Lines 1342-1348 Link Here
1342	<CODE>$SRC_ROOT/instsetoo/<Linux>unxlngi3.pro</Linux><Solaris>unxsols3.pro</Solaris><WindowsWin_tcsh>wntmsci7.pro</WindowsWin_tcsh>/33/normal</CODE>.	1329	<CODE>$SRC_ROOT/instsetoo/<Linux>unxlngi3.pro</Linux><Solaris>unxsols3.pro</Solaris><WindowsWin_tcsh>wntmsci7.pro</WindowsWin_tcsh>/33/normal</CODE>.
1343	</pre>	1330	</pre>
1344		1331
1345	Similarily, you will find 49 for German, 34 for Spanish, etc. </p>	1332	<p>Similarily, you will find 49 for German, 34 for Spanish, etc.</p>
1346		1333
1347	<p>	1334	<p>
1348	Localised help content is not yet available for all languages. In such cases, the english	1335	Localised help content is not yet available for all languages. In such cases, the english
Lines 1351-1357 Link Here
1351	appear in english.	1338	appear in english.
1352	</p>	1339	</p>
1353		1340
1354	<br><p><br><p><br><p>	1341	<br><br><br>
1355		1342
1356		1343
1357	</body>	1344	</body>