diff options
Diffstat (limited to 'TAO/CIAO/CIAO-INSTALL.html')
-rw-r--r-- | TAO/CIAO/CIAO-INSTALL.html | 122 |
1 files changed, 61 insertions, 61 deletions
diff --git a/TAO/CIAO/CIAO-INSTALL.html b/TAO/CIAO/CIAO-INSTALL.html index ce66f61fb5f..9b98f798491 100644 --- a/TAO/CIAO/CIAO-INSTALL.html +++ b/TAO/CIAO/CIAO-INSTALL.html @@ -6,15 +6,15 @@ <hr> <h3>Building and Installing CIAO </h3> - <p>The first thing you should do to install CIAO is to set the environment - variable <code>CIAO_ROOT</code> to be <code>$TAO_ROOT/CIAO</code>. Please refer + <p>The first thing you should do to install CIAO is to set the environment + variable <code>CIAO_ROOT</code> to be <code>$TAO_ROOT/CIAO</code>. Please refer to the <A href="../../ACE-INSTALL.html">ACE installation notes</A> and <A href="../TAO-INSTALL.html"> - TAO installation notes</A> for instructions on setting <code>$ACE_ROOT</code> - and <code>$TAO_ROOT</code>, respectively. They are needed since CIAO sits on - top of ACE+TAO. Compiling ACE+TAO successfully is the <strong>first</strong> requirement + TAO installation notes</A> for instructions on setting <code>$ACE_ROOT</code> + and <code>$TAO_ROOT</code>, respectively. They are needed since CIAO sits on + top of ACE+TAO. Compiling ACE+TAO successfully is the <strong>first</strong> requirement for compiling CIAO. </p> - <p>CIAO is divided into several parts, so different installation/building rules + <p>CIAO is divided into several parts, so different installation/building rules apply to different parts of CIAO.<br> <br> </p> @@ -25,11 +25,11 @@ <li> CIDL Compiler: This part of CIAO include <code>$CIAO_ROOT/CCF</code> and <code>$CIAO_ROOT/CIDLC</code>. <li> - CIAO Deployment and Configuration Framework: This part of CIAO includes all the - directories in <code>$CIAO_ROOT/DAnCE</code>. DAnCE is an implementation of the - new <a href="http://www.omg.org/cgi-bin/doc?ptc/2003-07-02">Deployment and - Configuration</a> specification. We refer, henceforth, to all pieces as CIAO - in general. The above two pieces will be referred specifically by their names + CIAO Deployment and Configuration Framework: This part of CIAO includes all the + directories in <code>$CIAO_ROOT/DAnCE</code>. DAnCE is an implementation of the + new <a href="http://www.omg.org/cgi-bin/doc?ptc/2003-07-02">Deployment and + Configuration</a> specification. We refer, henceforth, to all pieces as CIAO + in general. The above two pieces will be referred specifically by their names as CIDLC and DAnCE though they are part of CIAO. </li> </ol> @@ -53,31 +53,31 @@ </td> </tr> <tr> - <td><b>Binaries <a href="http://www.dre.vanderbilt.edu/cidlc/binary">available</a> intermittently, + <td><b>Binaries <a href="http://www.dre.vanderbilt.edu/cidlc/binary">available</a> intermittently, no automatic builds or tests</b> </td> <td>MacOS, Solaris </td> </tr> </table> - <p>If you have <A href="../../docs/ACE-porting.html">porting questions</A> or - have a problem compiling CIAO with TAO and ACE on the platforms shown above - please send email to either <A href="news:comp.soft-sys.ace">ACE Newsgroup</A> or - the <A href="mailto:ciao-users@cs.wustl.edu">CIAO mailing list</A> and we'll - try to help you fix the problems. You can also submit bug reports and - enhancement requests in our <A href="../../docs/usage-bugzilla.html">bug tracking + <p>If you have <A href="../../docs/ACE-porting.html">porting questions</A> or + have a problem compiling CIAO with TAO and ACE on the platforms shown above + please send email to either <A href="news:comp.soft-sys.ace">ACE Newsgroup</A> or + the <A href="mailto:ciao-users@cs.wustl.edu">CIAO mailing list</A> and we'll + try to help you fix the problems. You can also submit bug reports and + enhancement requests in our <A href="../../docs/usage-bugzilla.html">bug tracking system</A>. </p> <p>CIAO can be obtained <a href="http://www.dre.vanderbilt.edu/Download.html">electronically</a> - via the WWW and ftp. <a href="http://www.dre.vanderbilt.edu/CIAO">CIAO</a> is - bundled with the ACE and TAO release. You'll always need the most recent + via the WWW and ftp. <a href="http://www.dre.vanderbilt.edu/CIAO">CIAO</a> is + bundled with the ACE and TAO release. You'll always need the most recent version of ACE and TAO because CIAO tracks changes to ACE and TAO very closely. </p> <hr> <h3>Install CIDL Compiler </h3> <p>We suggest you download the prebuilt binary <code>cidlc(exe)</code> from <strong> - <a href="http://www.dre.vanderbilt.edu/cidlc/">here</a></strong> or, if you + <a href="http://www.dre.vanderbilt.edu/cidlc/">here</a></strong> or, if you are using Windows or Linux, you can build it by yourself. </p> <p><A href="../../MPC/README">MPC</A> is used to build the CIDL compiler on <strong> @@ -93,14 +93,14 @@ <li> Make sure you set cidl=1, boost=1, and exceptions=1 in <code>$ACE_ROOT/include/makeinclude/platfrom_macros.GNU</code>. <li> - Install <code>boost_filesystem</code>, <code>boost_regex</code> and <code>Utility + Install <code>boost_filesystem</code>, <code>boost_regex</code> and <code>Utility Library</code>. For how to do that please see <A href="./CCF/Documentation/Build.html"> Build.html</A>. <li> In <code>$CIAO_ROOT/CIDLC</code> run <code>$ACE_ROOT/bin/mwc.pl CIDLC.mwc</code> <li> In <code>$CIAO_ROOT/CIDLC</code> run <code>make</code>.<br> - Note: The linking time is a bit long (more than 5 Minutes with an Intel XEON + Note: The linking time is a bit long (more than 5 Minutes with an Intel XEON 1.90GHZ CPU, please be patient). </li> </ul> @@ -109,30 +109,30 @@ <ol> <li> Use the provided Visual Studio solution/project file. For detail please see <A href="./CCF/Documentation/Build.html"> - Build.html</A>. Since MPC is now supported to build the CIDL compiler on + Build.html</A>. Since MPC is now supported to build the CIDL compiler on Windows, these solution/project files may be removed in the future. <li> Use <A href="../../MPC/README">MPC</A>. The procedure is outlined below. <ul> <li> If you have not created it already, create the file <code>%ACE_ROOT%/bin/MakeProjectCreator/config/default.features</code> - and add <code>cidl=1</code> and <code>boost=1</code> to it, each on its own - line. An easy way to do this is to copy the file <code>global.features</code> (in the + and add <code>cidl=1</code> and <code>boost=1</code> to it, each on its own + line. An easy way to do this is to copy the file <code>global.features</code> (in the same directory) as <code>default.features</code> - and modify the appropriate lines in the new file, leaving everything else the + and modify the appropriate lines in the new file, leaving everything else the same. <li> Install the <a href="http://www.boost.org">Boost</a> - libraries on your machine. For Windows, you can download either the - Windows-specific .exe file or the platform-independent .zip file. Use version - 1.32.0 or later. The accompanying documentation on how to build and install + libraries on your machine. For Windows, you can download either the + Windows-specific .exe file or the platform-independent .zip file. Use version + 1.32.0 or later. The accompanying documentation on how to build and install Boost is pretty straightforward. <li> Set the following environment variables: <ul> <li> <code>ACE_ROOT</code> - - [path ending with ACE_wrappers directory] (this should already be + - [path ending with ACE_wrappers directory] (this should already be set if you're using CIAO) <li> <code>BOOST_CFG</code> - <code>_vc7_mdsd</code> @@ -140,18 +140,18 @@ <code>BOOST_ROOT</code> - [path ending with Boost directory] <li> - <code>BOOST_VERSION</code> - [name of the directory under <code>%BOOST_ROOT%\include</code>, + <code>BOOST_VERSION</code> - [name of the directory under <code>%BOOST_ROOT%\include</code>, for ex. <code>boost-1_32</code>, for Boost vesrion 1.32.0] <LI> <code>UTILITY_ROOT</code> - <code>%ACE_ROOT%\contrib\utility</code> </LI> </ul> <li> - In <code>%CIAO_ROOT%\CIDLC</code> run <code>%ACE_ROOT%\bin\mwc.pl -type vc71 + In <code>%CIAO_ROOT%\CIDLC</code> run <code>%ACE_ROOT%\bin\mwc.pl -type vc71 CIDLC.mwc</code> <li> - Open <code>CIDLC.sln</code> and build as usual. Within the solution, the CIDLC - project is the top-level one, which depends on all the other projects, and + Open <code>CIDLC.sln</code> and build as usual. Within the solution, the CIDLC + project is the top-level one, which depends on all the other projects, and produces <code>cidlc.exe</code> in <code>%CIAO_ROOT%\bin</code>. </li> </ul> @@ -160,43 +160,43 @@ <hr> <h3>Obtaining and Installing Xerces-C </h3> - <p>The Xerces-C XML parsing library is a necessary component to build parts of - DAnCE that need to process XML based descriptor files, which include the <b>Plan - Launcher</b> and the <b>Repository Manager</b>. Currently, the only Xerces-C + <p>The Xerces-C XML parsing library is a necessary component to build parts of + DAnCE that need to process XML based descriptor files, which include the <b>Plan + Launcher</b> and the <b>Repository Manager</b>. Currently, the only Xerces-C version supported by the DOC group is version 2.6 or later. Earlier versions of the Xerces-C library may work. </p> <h4>Building Xerces-C </h4> - <p>You may check <a href="http://www.dre.vanderbilt.edu/~wotte/xerces/">here</a> to - see if there is a prebuilt binary available for your platform. Otherwise, you + <p>You may check <a href="http://www.dre.vanderbilt.edu/~wotte/xerces/">here</a> to + see if there is a prebuilt binary available for your platform. Otherwise, you will have to obtain the source from the <a href="http://xml.apache.org/xerces-c/download.cgi"> - Xerces-C webpage</a> and build it. Building Xerces-C is fairly + Xerces-C webpage</a> and build it. Building Xerces-C is fairly straightfoward. Please see the documentation available <a href="http://xml.apache.org/xerces-c/build.html"> here</a> for instructions particular to your platform. </p> <ul> <li> - <strong>NOTE</strong>: Some of the provided projects with Xerces-C attach - inconsistant library decorators onto the end of the Xerces-C libraries. The MPC - build tool will expect these libraries to be named xerces-c for non debug + <strong>NOTE</strong>: Some of the provided projects with Xerces-C attach + inconsistant library decorators onto the end of the Xerces-C libraries. The MPC + build tool will expect these libraries to be named xerces-c for non debug versions, and xerces-cd for debug versions. </ul> <h4>Xerces-C Environment Settings </h4> - <p>If the Xerces includes and libraries are in your system include and library - paths, respectively, then you need not set up any environment and may proceed - to the next step. If not, you will need to set an environment variable named - XERCESCROOT to a path such that $XERCESCROOT/include points to the includes and - $XERCESCROOT/lib points to the libraries. Also make sure that $XERCESCROOT/lib - is in the appropriate environment variable that your platform uses to search + <p>If the Xerces includes and libraries are in your system include and library + paths, respectively, then you need not set up any environment and may proceed + to the next step. If not, you will need to set an environment variable named + XERCESCROOT to a path such that $XERCESCROOT/include points to the includes and + $XERCESCROOT/lib points to the libraries. Also make sure that $XERCESCROOT/lib + is in the appropriate environment variable that your platform uses to search for dynamically linked libraries. </p> <hr> <h3>Install CIAO core/tools/examples </h3> - <p>Most of the GNUmakefiles/project files/solution files required to build CIAO - are available in the release. If you don't like the configurations used, please + <p>Most of the GNUmakefiles/project files/solution files required to build CIAO + are available in the release. If you don't like the configurations used, please feel free to regenerate them using MPC. Please see <A href="../../MPC/README">this</A> for more details. </p> @@ -208,7 +208,7 @@ <li> Make sure you have the Xerces-C libraries installed/built <li> - Make sure all ACE/TAO/etc. generated libs are in <code>$ACE_ROOT/lib</code>. To + Make sure all ACE/TAO/etc. generated libs are in <code>$ACE_ROOT/lib</code>. To build CIAO you will need: <ul> <li> @@ -237,7 +237,7 @@ <p>For the supported build tools please see <a href="http://downloads.ociweb.com/MPC/MakeProjectCreator.pdf"> MPC manual</a>. </p> - <p>You have to execute the MPC command in the following directories if you only + <p>You have to execute the MPC command in the following directories if you only want to build the examples and have a peek at CIAO: </p> <ul> @@ -245,7 +245,7 @@ <code>$CIAO_ROOT/DAnCE/</code> </li> </ul> - <p>On <strong>Linux</strong>: do <code>$ACE_ROOT/bin/mwc.pl</code> at the + <p>On <strong>Linux</strong>: do <code>$ACE_ROOT/bin/mwc.pl</code> at the locations specified above then <code>make</code>. </p> <p>On <strong>Windows/VC6</strong>: do <code>%ACE_ROOT%/bin/mwc.pl -type vc6</code> @@ -255,14 +255,14 @@ at the locations specified above then Open the solution file and build. </p> <p><strong>Note:</strong> You can run <code>mwc.pl</code> at <code>$CIAO_ROOT</code> - as long as you don't intend to build CIDL compiler with MPC. If this is the - case(default), you can run the mwc.pl command with proper augment once then you - can do <code>make</code> at <code>$CIAO_ROOT</code> (Linux) or open the + as long as you don't intend to build CIDL compiler with MPC. If this is the + case(default), you can run the mwc.pl command with proper augment once then you + can do <code>make</code> at <code>$CIAO_ROOT</code> (Linux) or open the workspace/solution file at <code>$CIAO_ROOT</code> (Windows) to build. </p> </li> </ol> - <strong>Building CIAO quickly</strong> : You can build CIAO quickly by doing + <strong>Building CIAO quickly</strong> : You can build CIAO quickly by doing the following: <ul class="noindent"> <li> @@ -276,12 +276,12 @@ <li> Type 'make' <li style="LIST-STYLE-TYPE: none"> - This will build all the required ACE+TAO libraries including CIAO libraries and + This will build all the required ACE+TAO libraries including CIAO libraries and tools. </li> </ul> <hr> - <p>Back to the <a href="http://www.cs.wustl.edu/~schmidt/CIAO.html">CIAO</a> home + <p>Back to the <a href="http://www.cs.wustl.edu/~schmidt/CIAO.html">CIAO</a> home page. <!--#include virtual="/~schmidt/cgi-sig.html" --></p> </body> </html> |