diff options
Diffstat (limited to 'ACE-INSTALL.html')
| -rw-r--r-- | ACE-INSTALL.html | 2515 |
1 files changed, 1290 insertions, 1225 deletions
diff --git a/ACE-INSTALL.html b/ACE-INSTALL.html index 0302faafb08..668afa0e02c 100644 --- a/ACE-INSTALL.html +++ b/ACE-INSTALL.html @@ -1,92 +1,109 @@ <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> -<html><head><!-- $Id$ --> - <meta content="text/html; charset=ISO-8859-1" http-equiv="content-type"><title>Building and Installing ACE and Its Auxiliary Libraries and Services</title> +<!-- $Id$ --> - <link rev="made" href="mailto:d.schmidt@vanderbilt.edu"></head> +<HTML> +<HEAD> + <meta content="text/html; charset=ISO-8859-1" http-equiv="content-type"> + <TITLE>Building and Installing ACE and Its Auxiliary Libraries and Services</TITLE> + <link rev=made href="mailto:d.schmidt@vanderbilt.edu"> +</HEAD> +<BODY text = "#000000" + link = "#000fff" + vlink = "#ff0f0f" + bgcolor = "#ffffff"> +<HR> +<H3>Building and Installing ACE and Its Auxiliary Libraries and Services</H3> -<body bgcolor="#ffffff" link="#000fff" text="#000000" vlink="#ff0f0f"> - -<hr> -<h3>Building and Installing ACE and Its Auxiliary Libraries and Services</h3> - -<h4>Synopsis</h4> +<H4>Synopsis</H4> The file explains how to build and install ACE and its Network Services on the various OS platforms and compilers that it has been -ported to. Please consult the <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/ChangeLog">ChangeLog</a> file +ported to. Please consult the <A HREF="ChangeLog">ChangeLog</A> file to see whether any recent changes to the release will affect your -code. In addition, you should check out our <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/docs/ACE-development-process.html">development -process</a>. As you start working with ACE, we suggest you get copies -of the <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE/book1/">C++NPv1</a>, <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE/book2/">C++NPv2</a>, and <a href="http://www.amazon.com/exec/obidos/tg/detail/-/0201699710/qid=1066059513/sr=8-1/ref=sr_8_1/103-7740325-3955843?v=glance&s=books&n=507846">APG</a> books +code. In addition, you should check out our <A +HREF="docs/ACE-development-process.html">development +process</A>. As you start working with ACE, we suggest you get copies +of the <A +HREF="http://www.cs.wustl.edu/~schmidt/ACE/book1/">C++NPv1</A>, <A +HREF="http://www.cs.wustl.edu/~schmidt/ACE/book2/">C++NPv2</A>, and <A +HREF="http://www.amazon.com/exec/obidos/tg/detail/-/0201699710/qid=1066059513/sr=8-1/ref=sr_8_1/103-7740325-3955843?v=glance&s=books&n=507846">APG</A> books to help guide you after you've built and installed ACE. You should -also consult the <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/docs/ACE-FMM.html">ACE Frequently Made +also consult the <a href="docs/ACE-FMM.html">ACE Frequently Made Mistakes page</a>. If you encounter any problems or would like to -request an enhancement, then use our <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/docs/usage-bugzilla.html">bug tracking system</a> to submit a -report in accordance with our <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/docs/ACE-bug-process.html">bug -report process</a>.<p> - -</p><h4>Document Index</h4> - -<ul> - <li><a href="#platforms">Supported Platforms and C++ Compilers</a> - </li><li><a href="#installpre">Installation prerequisites</a> - </li><li><a href="#installnotes">Installation Notes</a> - </li><li><a href="#g++">Compiling ACE with GNU g++</a> - </li><li><a href="#egcs">Compiling ACE with egcs</a> - </li><li><a href="#aceinstall">Building and Installing ACE</a> - </li><li><a href="#svcsinstall">Building and Installing ACE Network Services</a> - </li><li><a href="#sslinstall">Building and Installing The ACE_SSL Library</a> - </li><li><a href="#minimum_build">What Do I Need to Build for TAO?</a> - </li><li><a href="#resource_requirements">System Resource Requirements</a> - </li><li><a href="#MPC">General MPC Information</a> - </li><li><a href="#eclipse">Working with ACE in Eclipse</a> - </li><li><a href="#advanced">Advanced Topics</a> - </li><li><a href="#power">Building from Anonymous CVS</a> -</li></ul> - - -<p></p><hr><p> -</p><h3><a name="platforms">Platforms, C++ Compilers, and Support</a></h3> - -<p>ACE has been ported to a large number of platfroms using many different -compilers over the years. The <a href="http://www.dre.vanderbilt.edu/">DOC group</a>, <a href="http://www.riverace.com/">Riverace</a>, <a href="http://www.theaceorb.com/">OCI</a>, <a href="http://www.theaceorb.nl/">Remedy IT</a>, and members of the ACE +request an enhancement, then use our <a +href="docs/usage-bugzilla.html">bug tracking system</a> to submit a +report in accordance with our <A +HREF="docs/ACE-bug-process.html">bug +report process</a>.<P> + +<H4>Document Index</H4> + +<UL> + <LI><A HREF="#platforms">Supported Platforms and C++ Compilers</A> + <LI><A HREF="#installpre">Installation prerequisites</A> + <LI><A HREF="#installnotes">Installation Notes</A> + <LI><A HREF="#g++">Compiling ACE with GNU g++</A> + <LI><A HREF="#egcs">Compiling ACE with egcs</A> + <LI><A HREF="#aceinstall">Building and Installing ACE</A> + <LI><A HREF="#svcsinstall">Building and Installing ACE Network Services</A> + <LI><A HREF="#sslinstall">Building and Installing The ACE_SSL Library</A> + <LI><A HREF="#minimum_build">What Do I Need to Build for TAO?</A> + <LI><A HREF="#resource_requirements">System Resource Requirements</A> + <LI><A HREF="#MPC">General MPC Information</A> + <LI><A HREF="#advanced">Advanced Topics</A> + <LI><A HREF="#power">Building from Anonymous CVS</A> +</UL> + + +<P><HR><P> +<H3><A NAME="platforms">Platforms, C++ Compilers, and Support</A></H3> + +<p>ACE has been ported to a large number of platfroms using many different +compilers over the years. The <A +HREF="http://www.dre.vanderbilt.edu/">DOC group</A>, <A +HREF="http://www.riverace.com/">Riverace</A>, <A +HREF="http://www.theaceorb.com">OCI</A>, <A +HREF="http://www.theaceorb.nl">Remedy IT</A>, and members of the ACE user community have all contributed ports to make ACE the successful and far-reaching toolkit it is today. Any UNIX/POSIX/Windows -variation is a potential target platform for ACE. If you have <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/docs/ACE-porting.html">porting questions</a> or have a problem +variation is a potential target platform for ACE. If you have <A +HREF="docs/ACE-porting.html">porting questions</A> or have a problem compiling the ACE source distribution, please contact one of the commercial support companies, or send a copy of the -PROBLEM-REPORT-FORM to either the <a href="news:comp.soft-sys.ace">ACE -Newsgroup</a> or the <a href="mailto:ace-users@cs.wustl.edu">ACE -mailing list</a> and someone will try to help you fix the problems. +PROBLEM-REPORT-FORM to either the <A HREF="news:comp.soft-sys.ace">ACE +Newsgroup</A> or the <A HREF="mailto:ace-users@cs.wustl.edu">ACE +mailing list</A> and someone will try to help you fix the problems. -</p><p>The responsibility for maintaining ACE across this wide range of +<p>The responsibility for maintaining ACE across this wide range of platforms is divided among a few different groups: the DOC group, Riverace, OCI, Remedy IT, and the ACE user community itself. The table below summarizes each group's role and where you can get more detailed information. For information on TAO's platform coverage and -support, please also see <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/TAO/TAO-INSTALL.html">TAO's install -document</a>.</p><p> +support, please also see <A HREF="TAO/TAO-INSTALL.html">TAO's install +document</A>.<P> -<table border="1" width="75%"> -<caption><b>Groups Involved in ACE Development and Support<br></b></caption> +<table width="75%" border=1> +<caption><b>Groups Involved in ACE Development and Support<BR></B></caption> <thead> - <tr valign="top"> + <tr valign=top> <th>Group - </th><th>Platforms - </th><th>For more information - </th></tr> -</thead><tbody> + <th>Platforms + <th>For more information + </tr> +<tbody> <tr> <th>DOC Group</th> - <td><a href="http://www.dre.vanderbilt.edu/scoreboard/">Tested</a> + <td><A HREF="http://www.dre.vanderbilt.edu/scoreboard/">Tested</A> and used daily by the DOC group: Solaris 7, 8 and 9 (many compilers excluding SunC++ 4.x) Windows 2000, XP (MSVC++ 6.x, and 7.x) Linux/Intel (many compilers), Linux/IA64 (GCC). </td> - <td>DOC sites at <a href="http://www.dre.vanderbilt.edu/">ISIS, </a><a href="http://doc.ece.uci.edu/">UCI</a> and <a href="http://tao.doc.wustl.edu/">Washington University</a> + <td>DOC sites at <A HREF="http://www.dre.vanderbilt.edu/">ISIS, <A + HREF="http://doc.ece.uci.edu/">UCI</A> and <A + HREF="http://tao.doc.wustl.edu/">Washington University</A> </td> </tr> <tr> @@ -94,26 +111,26 @@ document</a>.</p><p> <td>Offers support services for many platforms including those above, HP-UX, AIX, and Windows CE. </td> - <td>Riverace's <a href="http://www.riverace.com/">web site</a></td> + <td>Riverace's <A HREF="http://www.riverace.com/">web site</A></td> </tr> <tr> <th>OCI</th> <td>Maintains ACE on certain platforms required for their TAO software and service offerings. </td> - <td>OCI's <a href="http://www.theaceorb.com/">web site</a> and - the TAO <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/TAO/TAO-INSTALL.html">install document</a></td> + <td>OCI's <A HREF="http://www.theaceorb.com/">web site</A> and + the TAO <A HREF="TAO/TAO-INSTALL.html">install document</A></td> </tr> <tr> <th>Remedy IT</th> <td>Maintains ACE on many platforms required for their ACE and TAO service offerings. Besides the standard DOC group platforms - we also support Borland C++ Builder 6, CBuilderX 1.0, MinGW, - Cygwin, VxWorks 5.5, OpenVMS 7.3-2, Linux 64bit Alpha, Tru64, - HPUX 11i 32/64 bit on PA-RISC, and HPUX 11i v2 on Itanium. + we also support Borland C++ Builder 6, CBuilderX 1.0, MinGW, + Cygwin, VxWorks 5.5, OpenVMS 7.3-2, Linux 64bit Alpha, Tru64, + and HPUX 11i 32/64 bit. </td> - <td>Remedy IT <a href="http://www.theaceorb.nl/">web site</a> and - the TAO <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/TAO/TAO-INSTALL.html">install document</a> + <td>Remedy IT <A HREF="http://www.theaceorb.nl">web site</A> and + the TAO <A HREF="TAO/TAO-INSTALL.html">install document</A> </td> </tr> <tr> @@ -128,7 +145,7 @@ document</a>.</p><p> Chorus; OS/9; PharLap TNT Embedded ToolSuite 9.1; QNX RTP and Neutrino 2.0; VxWorks; LynxOS; RTEMS </td> - </tr><tr> + <tr> <th>Not supported</th> <td>The following platforms have been supported in the past but are not supported anymore by the DOC Group. If you want to have @@ -137,29 +154,33 @@ document</a>.</p><p> Borland C++ Builder 4 and 5. </td> </tr> - <tr><td></td> + <td></td> </tr> -</tbody></table></p><p> +</table><P> -</p><p>Although the DOC group has provided outstanding, world-class +<p>Although the DOC group has provided outstanding, world-class support for ACE over the years, ACE's success has greatly increased the amount of effort required to keep up with its maintenance, answer users' questions, and give design guidance. Riverace offers world-class commercial services to support ACE users and OCI and Remedy IT offer similar services for TAO, allowing the DOC group's -primary focus to shift back to their main goal: <em>research</em>. The -DOC group is fundamentally focused on (and <a href="http://www.cs.wustl.edu/%7Eschmidt/resume-grants.html">funded -by</a>) advanced R&D projects. The group continues to be +primary focus to shift back to their main goal: <EM>research</EM>. The +DOC group is fundamentally focused on (and <A +HREF="http://www.cs.wustl.edu/~schmidt/resume-grants.html">funded +by</A>) advanced R&D projects. The group continues to be intimately involved in ACE+TAO development and maintenance, but with -revised priorities for maintenance. The <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/docs/ACE-bug-process.html">bug fixing policies</a> followed by -the DOC group are designed to strike a balance between their many <a href="http://www.cs.wustl.edu/%7Eschmidt/research.html">research -projects</a> and their commitment to the ACE+TAO <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE-users.html">user -community</a>. Naturally, we will be happy to accept well-tested +revised priorities for maintenance. The <A +HREF="docs/ACE-bug-process.html">bug fixing policies</A> followed by +the DOC group are designed to strike a balance between their many <A +HREF="http://www.cs.wustl.edu/~schmidt/research.html">research +projects</A> and their commitment to the ACE+TAO <A +HREF="http://www.cs.wustl.edu/~schmidt/ACE-users.html">user +community</A>. Naturally, we will be happy to accept well-tested patches from the ACE+TAO user community for any platforms that aren't -supported by the DOC group, Riverace, OCI or Remedy IT. </p><p> +supported by the DOC group, Riverace, OCI or Remedy IT. <P> -</p><p></p><hr><p> -</p><h3><a name="installpre">Installation prerequisites</a></h3> +<P><HR><P> +<H3><A NAME="installpre">Installation prerequisites</A></H3> ACE (including TAO and CIAO) uses MPC (MakeProjectCreator) to generate files useful for the build tools (such as GNUmakefiles for UNIX based @@ -169,44 +190,47 @@ of ACE (TAO and CIAO) includes GNUmakefiles for UNIX platforms, VC6 project files, and VC71 solution files. If it is necessary to generate files for build tools for other compilers such as Visual Age for IBM, and Windows CE users have to run MPC themselves to generate the -appropriate files. Please see <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/MPC/USAGE"> USAGE </a>, <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/MPC/README"> README </a> and <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/bin/MakeProjectCreator/README">README for ACE</a> files for +appropriate files. Please see <A HREF="MPC/USAGE"> USAGE </A>, <A +HREF="MPC/README"> README </A> and <A +HREF="bin/MakeProjectCreator/README">README for ACE</A> files for details. The options that have been used to generate the above build -files can be found in <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/bin/MakeProjectCreator/config/global.features"> -global.features</a> file. +files can be found in <A +HREF="bin/MakeProjectCreator/config/global.features"> +global.features</A> file. -<p></p><hr><p> -</p><h3><a name="installnotes">Installation Notes</a></h3> +<P><HR><P> +<H3><A NAME="installnotes">Installation Notes</A></H3> -<ul> - <li><b>Windows (Windows NT, 2000, XP, 2003, etc., and Windows '9x/ME) </b><p> +<UL> + <LI><B>Windows (Windows NT, 2000, XP, 2003, etc., and Windows '9x/ME) </B><P> All of ACE has been ported to the Win32 API (which includes Windows NT, Windows 2000, and Windows '95/98/ME) and Win64. The entire release now compiles using the Microsoft Visual C++ 6.0, and 7.1 (aka Visual C++ .NET 2003) compilers. ACE can be built as both a static (LIB) and dynamic (DLL) library, using the Win32 installation - process described below.</p><p> + process described below.<P> - Please see the <a href="#Non-static%20Object%20Manager">Non-static - ACE_Object_Manager</a> discussion below.</p><p> + Please see the <A HREF="#Non-static Object Manager">Non-static + ACE_Object_Manager</A> discussion below.<p> We've also added some support for - <a href="#mingw">GNU g++ with MinGW</a>, - <a href="#cygwin">GNU g++ with Cygwin</a> - <a href="#borland">Borland C++ 5.5, Borland C++ Builder 4.0/5.0/6.0 - and Borland C++ BuilderX</a>, and IBM's VisualAge C++ compiler. + <A HREF="#mingw">GNU g++ with MinGW</A>, + <A HREF="#cygwin">GNU g++ with Cygwin</A> + <A HREF="#borland">Borland C++ 5.5, Borland C++ Builder 4.0/5.0/6.0 + and Borland C++ BuilderX</A>, and IBM's VisualAge C++ compiler. Since we don't have these compilers we rely on the ACE+TAO users community to maintain these ports. Therefore, please send email - to the ACE mailing list if you run into problems. </p><p> + to the ACE mailing list if you run into problems. <P> - </p></li><li><b>Windows CE</b><p> + <li><b>Windows CE</b><p> - Take a look at (<a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/docs/CE-status.txt">CE-status.txt</a>) for - up-to-date information about ACE on CE.</p><p> + Take a look at (<a href="docs/CE-status.txt">CE-status.txt</a>) for + up-to-date information about ACE on CE.<P> - </p></li><li><b> Solaris 2.6, 7, 8, and 9 using Sun 5.5 - or Forte 9, Centerline C++ 2.x, GNU gcc 2.95 and later.</b><p> + <LI><B> Solaris 2.6, 7, 8, and 9 using Sun 5.5 + or Forte 9, Centerline C++ 2.x, GNU gcc 2.95 and later.</B><P> All the source code and tests should build and run without any problems on Solaris 7, 8, and 9 platforms using the above @@ -218,36 +242,38 @@ global.features</a> file. /usr/ccs/bin/as, if you want -gstabs+ and -pipe support. Thanks to Susan Liebeskind <shl@janis.gtri.gatech.edu> - for providing the following useful information:</p><p> + for providing the following useful information:<p> By default, ACE uses both the Solaris and POSIX thread interface. To disable use of the Solaris thread interface, add <code>-D_POSIX_PTHREAD_SEMANTICS</code> to the <code>CFLAGS</code> in your - <code>$(ACE_ROOT)/include/makeinclude/platform_macros.GNU</code>. - See the Solaris Intro (3) man page for more information.</p><p> + <code>ACE_wrappers/include/makeinclude/platform_macros.GNU</code>. + See the Solaris Intro (3) man page for more information.<p> To disable ACE thread support completely, build with the - <code>threads=0</code> make flag. See the <a href="#flags">Makefile Flags</a> section below for more - information on make flags.</p><p> + <code>threads=0</code> make flag. See the <a + href="#flags">Makefile Flags</a> section below for more + information on make flags.<p> If you use g++ on Solaris 7, you might need to rebuild it on a SunOS 5.7 (Solaris 7) host. Some versions of g++ and egcs provide replacements for system header files. The replacements on older SunOS systems are not compatible with the - SunOS 5.7 system headers. See <a href="http://www.cs.wustl.edu/%7Elevine/Hints.html">David Levine's + SunOS 5.7 system headers. See <a + href="http://www.cs.wustl.edu/~levine/Hints.html">David Levine's Hints page</a> for instructions on how to build egcs on a SunOS 5.7 host, using a g++ or egcs that was built on an older SunOS - host. </p><p> + host. <P> The Sun/C++ compilers until and including 5.4 has several problems with templates and we don't test very often with them. We regularly use and test with Sun/C++ 5.5.</p> - </li><li><b>AIX</b><p> + <LI><B>AIX</B><P> ACE has been ported to AIX 4.3 and higher using the IBM C/C++ - Compiler 3.6.6, Visual Age C++ 5 and 6, and g++ 3.2.</p><p> + Compiler 3.6.6, Visual Age C++ 5 and 6, and g++ 3.2.<p> To build ACE on AIX with Visual Age C++ 5 in incremental mode (i.e. with the IDE), use the @@ -257,7 +283,7 @@ global.features</a> file. include the general config-aix-4.x.h file which has support for all of the OS versions and compilers supported on AIX. Using the general config file is the recommended practice for g++, IBM - C/C++, and Visual Age C++ batch mode compilers.</p><p> + C/C++, and Visual Age C++ batch mode compilers.<p> Visual Age C++ 4 has also been supported on ACE 5.1, but is no longer supported. If you are still using this compiler, please use the @@ -265,81 +291,85 @@ global.features</a> file. config-aix-4.3.x.h ACE config file. Beware, however, that it hasn't been tested. - BTW, here's a technique from Rob Jordan <<a href="mailto:jordan@hursley.ibm.com">jordan@hursley.ibm.com</a>> + BTW, here's a technique from Rob Jordan <<A + HREF="mailto:jordan@hursley.ibm.com">jordan@hursley.ibm.com</A>> that can reduce the size of the ACE libraries by about one third, and can also be applied to applications. It works by optimising the sharing of template functions, which are created - in an "unusual" way under AIX. It also speeds up - compilation.</p><p> + in an "unusual" way under AIX. It also speeds up + compilation.<P> - Here's how to optimise the ACE library generation:</p><p> + Here's how to optimise the ACE library generation:<P> - Look at the <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/ace/GNUmakefile.ACE">ace/GNUmakefile.ACE</a> - in <code>$ACE_ROOT/ace</code>. Create a file called - <code>ACE_All_Src.cpp</code>, and add a line to #include + Look at the <A + HREF="ace/GNUmakefile.ACE">ace/GNUmakefile.ACE</a> + in <CODE>$ACE_ROOT/ace</CODE>. Create a file called + <CODE>ACE_All_Src.cpp</CODE>, and add a line to #include each of the source files - listed under <code>FILES=</code> in the GNUmakefile. Create a - file called <code>ACE_All_Tmp.h</code> + listed under <CODE>FILES=</CODE> in the GNUmakefile. Create a + file called <CODE>ACE_All_Tmp.h</CODE> and add a line to #include each of the .h files listed under - <code>TEMPLATE_FILES=</code> in the GNUmakefile. Now update the + <CODE>TEMPLATE_FILES=</CODE> in the GNUmakefile. Now update the GNUmakefile so that - <code>FILES=ACE_All_Src</code> and - <code>TEMPLATE_FILES=ACE_All_Tmp</code>.</p><p> + <CODE>FILES=ACE_All_Src</CODE> and + <CODE>TEMPLATE_FILES=ACE_All_Tmp</CODE>.<P> - </p></li><li><b><a name="Linux">Linux</a></b><p> + <LI><B><a name="Linux">Linux</a></B><P> - ACE has been ported to <a href="http://www.cs.wustl.edu/%7Ecleeland/ace/">Linux</a> on + ACE has been ported to <A + HREF="http://www.cs.wustl.edu/~cleeland/ace/">Linux</A> on Intel, Alpha, and PowerPC platforms. If you use a RedHat 5.x distribution, it's best to use RedHat 5.1 or later. ACE works without any modifications on RedHat 5.1 and later, and on Debian 2.1 on both Intel and Alpha. Use the <code>platform_linux.GNU</code> and <code>ace/config-linux.h</code> - in your <code>platform_macros.GNU</code> and - <code>config.h</code> files, respectively. The same + in your platform_macros.GNU and config.h files, respectively. The same files can be used on PowerPC, with LinuxPPC - 1999 (R5), with glibc 2.1.1.</p><p> + 1999 (R5), with glibc 2.1.1.<p> If you run out of memory, it's easy to add virtual memory on Linux. Please see the <code>mkswap</code> man page. You'll need at least 256 to 300 Mb of virtual memory (RAM + swap) to compile all of ACE+TAO. The <a href="#resource_requirements">System Resource Requirements section</a> has some suggestions on how - to reduce the memory requirement.</p><p> + to reduce the memory requirement.<p> The glibc 2.0 dynamic loader isn't thread safe. If you want to use the Invocation API you'll have to set <code>LD_BIND_NOW=true</code>. If you want to use <code>dlopen</code>, you should use <code>RTLD_NOW</code>. The - dynamic loader in glibc 2.1 is thread safe.</p><p> + dynamic loader in glibc 2.1 is thread safe.<p> The ACE <code>Tokens_Test</code> hangs with egcs 1.1b on Linux. It runs properly when built with egcs 1.0.2 and later. All other - ACE tests run properly with these egcs 1.0.2 and later.</p><p> + ACE tests run properly with these egcs 1.0.2 and later.<p> <strong>NOTE:</strong> The TAO NameService uses IP multicasting by default, though it is not required. IP multicast on Linux - requires the following:</p><p> + requires the following:<p> - </p><ul> + <ul> <li>Enable IP multicast in the Linux kernel. It is enabled in the default RedHat 5.1 kernel. In older distributions, you can enable it by rebuilding your kernel with CONFIG_IP_MULTICAST enabled.<p> - </p></li><li>Enable IP multicast in ACE. It is enabled by default in + <li>Enable IP multicast in ACE. It is enabled by default in <code>ace/config-linux-common.h</code>. If you don't use IP multicast, add <code>#define ACE_HAS_IP_MULTICAST 0</code> to your <code>ace/config.h</code> before building ACE.<p> - </p></li><li>There must be a network interface that is up and supports + <li>There must be a network interface that is up and supports multicast. If you have linuxconf, it's easiest to use that to add a network route for multicast (224.0.0.0) on one of your network interfaces, such as <code>eth0</code>. If you don't have or use linuxconf, try adding a multicast routing table entry using something like this:<p> - </p><pre> <code># route add -net 224.0.0.0 netmask 240.0.0.0 dev eth0</code> + <pre> + <code># route add -net 224.0.0.0 netmask 240.0.0.0 dev eth0</code> </pre><p> - </p></li></ul> + </ul> - With RedHat 5.0, you'll need some <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/os-patches/linux-patches.html">updates and possibly some + With RedHat 5.0, you'll need some <a + href="os-patches/linux-patches.html">updates and possibly some patches</a> to get ACE working with LinuxThreads. Some of the patches are necessary with Alpha CPUs and with some older kernels. egcs 1.0.1 can also be used, but it may need patches, @@ -350,56 +380,57 @@ global.features</a> file. best to install egcs in a different directory than <code>/usr</code>, such as <code>/usr/local</code>, and set your <code>PATH</code> and <code>LD_LIBRARY_PATH</code> - accordingly.</p><p> + accordingly.<p> Some of the ACE tests fail on older, pre-glibc2 Linux platforms, such as RedHat 4.2. The problems are with threads and - thread-specific storage.</p><p> + thread-specific storage.<p> - </p></li><li><b>SCO UNIX</b><p> + <LI><B>SCO UNIX</B><P> ACE has been ported to SCO UNIX using the GNU g++ 2.7.2 - compiler. Arturo Montes <<a href="mailto:mitosys@colomsat.net.co">mitosys@colomsat.net.co</a>> + compiler. Arturo Montes <<A + HREF="mailto:mitosys@colomsat.net.co">mitosys@colomsat.net.co</A>> maintains this code. In addition, he also maintains a version - of <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/FSU-threads.tar.gz">FSU pthreads</a>.</p><p> + of <A HREF="FSU-threads.tar.gz">FSU pthreads</A>.<P> - </p></li><li><b>SGI IRIX 5.x and 6.x</b><p> + <LI><B>SGI IRIX 5.x and 6.x</B><P> ACE used to build fine using the SGI C++ and GNU GCC compilers for IRIX 5.x. It has been ported to IRIX 6.x using the SGI MipsPro 7.1 C++ compiler; be aware that in IRIX 6.2 there is a number of patches that have to be installed and exceptions appear to fail with the O32 ABI. Please check the config files - for the details.</p><p> + for the details.<P> - </p></li><li><b> HP-UX 10.x and 11.x </b> <p> + <LI><B> HP-UX 10.x and 11.x </B> <P> HP sells 2 C++ compilers for HP-UX 10.x and 11.00: - </p><ul> - <li>HP C++ - this is CC, HP's cfront-based compiler. As of ACE 4.4, it + <UL> + <LI>HP C++ - this is CC, HP's cfront-based compiler. As of ACE 4.4, it can be used, but some people have problems with templates. Caveat emptor. It's been said that you should run version 10.24, if not later. ACE hasn't been tested with this compiler since the ACE 5.0 timeframe. - </li><li>HP aC++ - this is aCC, HP's new, ANSI compiler. It handles ACE + <LI>HP aC++ - this is aCC, HP's new, ANSI compiler. It handles ACE very well. You should use version A.01.27 (or higher) on HP-UX 10.x and version A.03.37 (or higher) on HP-UX 11. - </li></ul> - <p> + </UL> + <P> On HP-UX 10.20, a patch is required to compile ACE. The exact patch number depends on the platform - check with HP's patch database to locate the exact patch or its successor. For 9000 700 series machines - it is PHKL_8693 (s700 10.20 sys/time.h fix for select(2)/C++ defects).</p><p> + it is PHKL_8693 (s700 10.20 sys/time.h fix for select(2)/C++ defects).<p> Also see further notes on this platform at Riverace's - <a href="http://www.riverace.com/FAQ/faq.html">Frequently Asked - Questions</a> page. - </p><p> + <A HREF="http://www.riverace.com/FAQ/faq.html">Frequently Asked + Questions</A> page. + <P> - </p></li><li><b>OSF/1 3.2 and 4.0 (a.k.a. Digital UNIX 4.0)</b> <p> + <LI><B>OSF/1 3.2 and 4.0 (a.k.a. Digital UNIX 4.0)</B> <P> The Digital UNIX C++ 5.4 through 5.7 compilers have problems with ACE's templates. They compile the lib and most of the test @@ -407,14 +438,14 @@ global.features</a> file. run, some dump core. If you use a 5.x version of cxx, be sure to set the CXX_VER variable to CXX_5, either on your make command line or in an environment variable. The ACE Makefiles - assume by default that the cxx version is 6.x or later.</p><p> + assume by default that the cxx version is 6.x or later.<P> CXX 6.0 and 6.1 are much improved over 5.x: V6.0-020, V6.1-025, and later build all of ACE cleanly. All of the tests in - $(ACE_ROOT)/tests run successfully with CXX 6.0 and CXX 6.1. + ACE_wrappers/tests run successfully with CXX 6.0 and CXX 6.1. Please note that problems have been reported with some versions of CXX 6.1, notably versions -021 and earlier. It's best to use - V6.1-022 or later.</p><p> + V6.1-022 or later.<p> NOTE: if you use Digital UNIX 4.0f or later, you <strong>must</strong> use <code>ace/config-tru64.h</code> instead of @@ -423,14 +454,14 @@ global.features</a> file. Digital UNIX after and include 4.0. And, with 4.0f and later when using Digital CXX, you <strong>must</strong> use <code>include/makeinclude/platform_tru64_cxx.GNU</code> instead of - <code>include/makeinclude/platform_osf1_4.0.GNU</code>.</p> + <code>include/makeinclude/platform_osf1_4.0.GNU</code>.</P> - </li><li><b> FreeBSD </b><p> + <li><b> FreeBSD </b><p> FreeBSD is a fast evolving platform. However, it has the advantage of having standard releases. At this moment, ACE is only perodically tested against -stable (3.1R) and we rely a lot - on FreeBSD users' feedbacks. </p><p> + on FreeBSD users' feedbacks. <p> Notice that on older FreeBSD, <code>ld.so</code> only looks for so libraries with <b>version number</b> appended. ACE makefiles @@ -439,62 +470,65 @@ global.features</a> file. <code>$ACE_ROOT/ace</code> with appropriate ACE version. However, this does not work for libACE.so itself so you have to create it manually (If you figure out how to do this, please let - us know) like this: </p><p> + us know) like this: <p> - <code>ln -sf $ACE_ROOT/ace/libACE.so $ACE_ROOT/ace/libACE.so.4.5</code></p><p> + <code>ln -sf $ACE_ROOT/ace/libACE.so $ACE_ROOT/ace/libACE.so.4.5</code><p> - On newer FreeBSD (3.0 or later,) this is no longer necessary.</p><p> + On newer FreeBSD (3.0 or later,) this is no longer necessary.<p> - </p></li><li><b>NetBSD</b><p> + <li><b>NetBSD</b><p> Like older FreeBSD, NetBSD's <code>ld.so</code> also requires - versioned .so files.</p><p> + versioned .so files.<p> - </p></li><li><b>OpenBSD</b><p> + <li><b>OpenBSD</b><p> - ACE has been ported to OpenBSD 3.1 and GNU g++ 2.95.3.</p><p> + ACE has been ported to OpenBSD 3.1 and GNU g++ 2.95.3.<P> As with FreeBSD and NetBSD, OpenBSD requires versioned .so files. This is currently handled by the build files and no - additional work is needed.</p><p> + additional work is needed.<P> ACE has been ported to OpenBSD with and without pthreads enabled. When using pthreads, though, C++ exceptions must be disabled. This is a known problem with the current release of OpenBSD (see www.openbsd.org, bug #1750). ACE emulated - exceptions work fine.</p><p> + exceptions work fine.<P> Compiling TAO may require the user data segment size restrictions and possibly other options to be increased. This is done by modifying the default user class in /etc/login.conf or by adding a new class and modifying the master passwer file - accordingly.</p><p> + accordingly.<P> - </p></li><li><b> UnixWare </b> <p> + <LI><B> UnixWare </B> <P> - Steve Huston <<a href="mailto:shuston@riverace.com">shuston@riverace.com</a>> - has ported ACE to work with UnixWare 2.01 and g++.</p><p> + Steve Huston <<A + HREF="mailto:shuston@riverace.com">shuston@riverace.com</A>> + has ported ACE to work with UnixWare 2.01 and g++.<P> - Ganesh Pai <<a href="mailto:gpai@voicetek.com">gpai@voicetek.com</a>> - subsequently did the port for version 2.1.2, also with g++.</p><p> + Ganesh Pai <<A + HREF="mailto:gpai@voicetek.com">gpai@voicetek.com</A>> + subsequently did the port for version 2.1.2, also with g++.<P> - Phil Mesnier <<a href="mailto:mesnier_p@ociweb.com"> - mesnier_p@ociweb.com</a>> updated the port to support + Phil Mesnier <<A HREF="mailto:mesnier_p@ociweb.com"> + mesnier_p@ociweb.com</A>> updated the port to support UnixWare 7.1.0, with help from Michael Meissnitzer - <<a href="mailto:michael.meissnitzer@siemens.at"> - michael.meissnitzer@siemens.at</a>>, Christian Klepp < - <a href="mailto:christian.klepp@siemens.at">christian.klepp@siemens.at - </a>> and Engelbert Staller <<a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/engelbert.staller@siemens.at"> - engelbert.staller@siemens.at</a>> + <<A HREF="mailto:michael.meissnitzer@siemens.at"> + michael.meissnitzer@siemens.at</A>>, Christian Klepp < + <A HREF="mailto:christian.klepp@siemens.at">christian.klepp@siemens.at + </A>> and Engelbert Staller <<A HREF="engelbert.staller@siemens.at"> + engelbert.staller@siemens.at</A>> Building ACE (and TAO) on Unixware 7.1.0 requires a very specific g++ build environment. In particular, you must build and install g++ 2.95.2, along with binutils 2.9.1. The order (and the declaration of configuration) is extremely important. Using the gcc compiler provided on the Skunkware CD on a pentium system, here is the recipe I used to build a working environment (as root):<br> -</p><pre> mkdir /usr/local/newgnu -< ftp and untar binutils-2.9.1 > -< ftp and untar gcc-2.95.2 > +<pre> + mkdir /usr/local/newgnu +< ftp and untar binutils-2.9.1 > +< ftp and untar gcc-2.95.2 > mkdir -p build/binutils build/gcc cd build/binutils ../../binutils-2.9.1/configure i386-sco-sysv4 @@ -514,107 +548,111 @@ global.features</a> file. </pre> Once done, ACE and TAO will successfully build and link.<p> - </p></li><li><b>Chorus</b> <p> + <LI><B>Chorus</B> <P> - Wei Chiang <<a href="mailto:chiang@tele.nokia.fi">chiang@tele.nokia.fi</a>> - has ported ACE to Chorus 3.1 using GNU g++ 2.7.2.</p><p> + Wei Chiang <<A + HREF="mailto:chiang@tele.nokia.fi">chiang@tele.nokia.fi</A>> + has ported ACE to Chorus 3.1 using GNU g++ 2.7.2.<P> - </p></li><li><b><a name="LynxOS">LynxOS</a></b><p> + <LI><B><a name="LynxOS">LynxOS</a></B><P> ACE builds and runs properly on LynxOS 3.0.x, 3.1.x and 4.0.0 for Intel and PowerPC targets. LynxOS 2.5.x is no longer supported. To build ACE on LynxOS 3.0.x you need to update GCC to version 2.9-gnupro-98r2, which can be obtained from - <a href="ftp://ftp.lynuxworks.com/compilers/98r2-preview/"> - ftp://ftp.lynuxworks.com/compilers/98r2-preview/</a></p><p> + <A HREF="ftp://ftp.lynuxworks.com/compilers/98r2-preview/"> + ftp://ftp.lynuxworks.com/compilers/98r2-preview/</A><p> - If you run out of memory on LynxOS, these might help:</p><p> + If you run out of memory on LynxOS, these might help:<p> - </p><ul> + <ul> <li>Increase the limits in <code>/etc/starttab</code>, then reboot system. We use these limits: - <pre># Data, stack, and core file limits (in Kbytes) + <pre> +# Data, stack, and core file limits (in Kbytes) 80000 16000 102400</pre><p> - </p></li><li>Enable or expand virtual memory, with something like: - <pre># mkcontig /swap 320 + <li>Enable or expand virtual memory, with something like: + <pre> +# mkcontig /swap 320 # prio 17 vmstart /swap</pre> See the <code>mkcontig</code> and <code>vmstart</code> man pages, and <code>/bin/rc</code>.<p> - </p></li></ul> + </ul> Please see the comments in the - <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/include/makeinclude/platform_lynxos.GNU">ACE + <a href="include/makeinclude/platform_lynxos.GNU">ACE platform_lynxos.GNU file</a> for information on, and an example of, tailoring for your particular platform.<p> NOTE: if you want to use IP multicast on LynxOS, be sure to add - this line to your <code>/net/rc.network</code>, and reboot:</p><p> - </p><pre><code> + this line to your <code>/net/rc.network</code>, and reboot:<p> + <pre><code> /bin/route add "224.0.0.0" "$my_name" </code></pre> - </li><li><strong>VxWorks</strong><p> + <LI><STRONG>VxWorks</STRONG><P> - <a href="http://www.cs.wustl.edu/%7Elevine/">David Levine</a> - <<a href="mailto:levine@cs.wustl.edu">levine@cs.wustl.edu</a>> has + <A HREF="http://www.cs.wustl.edu/~levine/">David Levine</A> + <<A + HREF="mailto:levine@cs.wustl.edu">levine@cs.wustl.edu</A>> has ported ACE to VxWorks 5.2/5.3/5.3.1/5.4 with the GreenHills 1.8.8/1.8.9 and g++ compilers that are distributed with VxWorks/Tornado. An anonymous contributor has also - provided <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/os-patches/vxworks-5.1.txt">notes for using + provided <a href="os-patches/vxworks-5.1.txt">notes for using ACE with VxWorks 5.1.</a>. It is not possible to use VxWorks 5.4 and earlier with ACE anymore because the compilers delivered with - 5.4 and earlier don't support the C++ features ACE needs.</p><p> + 5.4 and earlier don't support the C++ features ACE needs.<P> Tornado 2.2/VxWorks 5.5 support IP multicast. That is not enabled by default in ACE for VxWorks, because it probably depends on kernel configuration. To enable it, add <code>#define ACE_HAS_IP_MULTICAST</code> to your - <code>ace/config.h</code>.</p><p> + <code>ace/config.h</code>.<p> In addition to all of the other benefits of ACE, it helps work around some deficiencies with VxWorks 5.3/5.3.1. Some of these apply only with g++, at least thru version 2.7.2. That is the version that is shipped with Tornado 1.0.1/ VxWorks 5.3.1. The - problems are:</p><p> + problems are:<P> - </p><ol> - <li>The program entry point cannot be called "main" with g++. ACE - renames it to "ace_main" (configurable via ACE_MAIN) on VxWorks. + <OL> + <LI>The program entry point cannot be called "main" with g++. ACE + renames it to "ace_main" (configurable via ACE_MAIN) on VxWorks. While this may seem trivial, it is important with legacy code. - ACE itself ran into this problem.<p> + ACE itself ran into this problem.<P> - </p></li><li>argc/argv isn't used with VxWorks entry points. ACE provides + <LI>argc/argv isn't used with VxWorks entry points. ACE provides a wrapper function that transparently converts shell command - line arguments to argc/argv form. See <a href="#spa">below</a> - for details.<p> + line arguments to argc/argv form. See <A HREF="#spa">below</a> + for details.<P> - </p></li><li>Unsigned long long support is not available with the g++ that + <LI>Unsigned long long support is not available with the g++ that is distributed with Tornado 1.0.1/VxWorks 5.3.1, or with GreenHills 1.8.8. The documentation says that it is supported by g++, but try using it :-) Wind River technical support verified that it doesn't work. ACE provides its own 64-bit unsigned integer type, ACE_hrtime_t, so you don't even have to worry about this - problem if you use it.<p> + problem if you use it.<P> - </p></li><li>There a gory problem with munch that is severely aggravated + <LI>There a gory problem with munch that is severely aggravated by the presence of a static in the Wind River/g++ iostream.h. ACE hides this and provides an easy-to-use workaround in the very unlikely situation where it becomes a problem. - Please see ace/config-vxworks5.x.h for more information.<p> - </p></li></ol> + Please see ace/config-vxworks5.x.h for more information.<P> + </OL> - In addition, as noted <a href="#g++">below</a> following the + In addition, as noted <A HREF="#g++">below</A> following the discussion of the g++ -fno-implicit-templates option, -fno-implicit-templates is broken for x86 targets. And, -O2 - is not supported on some targets.<p> + is not supported on some targets.<P> Please note that ACE uses one of the spare fields in the Wind River task control block, spare4, for thread- specific storage. This field is specified in only one place, in ace/OS.i, so it can easily be changed to one of the other spare fields, if - necessary.</p><p> + necessary.<P> Versions of ACE from 4.3.3 and beyond destroy dynamically allocated singletons in the ACE library. But, they may not @@ -622,14 +660,15 @@ global.features</a> file. running a program multiple times, it may be necessary to unload the module, using unld, and reload it between runs. Alternatively, you could try calling <code>cplusDtors</code> and - then <code>cplusCtors</code> between runs.</p><p> + then <code>cplusCtors</code> between runs.<P> - </p></li><li><b>MVS OpenEdition</b> <p> + <LI><B>MVS OpenEdition</B> <P> - All of ACE has been ported to OpenEdition by Chuck Gehr <<a href="mailto:gehr@sweng.stortek.com">gehr@sweng.stortek.com</a>&gt. + All of ACE has been ported to OpenEdition by Chuck Gehr <<A + HREF="mailto:gehr@sweng.stortek.com">gehr@sweng.stortek.com</A>>. The ACE library, all the tests and most of the examples and apps build clean. There are still some problems that need to be - ironed out:</p><p> + ironed out:<P> MVS does not support the dynamic linking dl...() calls that the Service Configurator uses to dynamically link services at run @@ -640,46 +679,53 @@ global.features</a> file. flex and yacc on a ascii (not ebcdic) machine and as a result they don't work very well with ebcdic svc.conf files. We should be able to regenerate these files on MVS but MVS doesn't have - flex. This is something that needs to be done.</p><p> + flex. This is something that needs to be done.<P> Some of the tests do not execute properly. This is a minority - and over time the goal is to get to 100%.</p><p> + and over time the goal is to get to 100%.<P> The make scheme for some of the apps still doesn't work perfectly on MVS. This is mainly due to the way shared - libraries are handled on MVS. See <a href="#mvs">additional - build tips for MVS</a> for more on this.</p><p> + libraries are handled on MVS. See <A HREF="#mvs">additional + build tips for MVS</A> for more on this.<P> - </p></li><li><strong>QNX Neutrino</strong><p> + <li><strong>QNX Neutrino</strong><p> - ACE has been ported to <a href="http://www.qnx.com/products/os/neutrino.html">QNX Neutrino + ACE has been ported to <a + href="http://www.qnx.com/products/os/neutrino.html">QNX Neutrino 2.0</a>. We cross-compile for Neutrino on a QNX4 host using g++ - 2.8.1, using the <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/ace/config-qnx-neutrino.h">ace/config-qnx-neutrino.h</a> - and <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/include/makeinclude/platform_qnx_neutrino.GNU">include/makeinclude/platform_qnx_neutrino.GNU</a> + 2.8.1, using the <a + href="ace/config-qnx-neutrino.h">ace/config-qnx-neutrino.h</a> + and <a + href="include/makeinclude/platform_qnx_neutrino.GNU">include/makeinclude/platform_qnx_neutrino.GNU</a> configuration files. Many of the ACE tests succeed, though some fail. As the porting effort progresses, we hope to eliminate these failures. If you know of fixes, please send them to - us.</p><p> - </p></li><li><strong>QNX RTP</strong><p> + us.<p> + <li><strong>QNX RTP</strong><p> - ACE has been ported to <a href="http://get.qnx.com/">QNX RTP + ACE has been ported to <a + href="http://get.qnx.com/">QNX RTP </a>. We compile for QNX RTP using the GCC compiler shipped with the - distribution, using the <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/ace/config-qnx-rtp.h">ace/config-qnx-rtp.h</a> - and <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/include/makeinclude/platform_qnx_rtp_gcc.GNU">include/makeinclude/platform_qnx_rtp_gcc.GNU</a> + distribution, using the <a + href="ace/config-qnx-rtp.h" >ace/config-qnx-rtp.h</a> + and <a + href="include/makeinclude/platform_qnx_rtp_gcc.GNU">include/makeinclude/platform_qnx_rtp_gcc.GNU</a> configuration files. Many of the ACE tests succeed, though some fail. As the porting effort progresses, we hope to eliminate these failures. If you know of fixes, please send them to - us.</p><p> + us.<p> <strong><blink><font color="#ff0000">WARNING:</font></blink></strong> Under the current version of QNX RTP ACE fails if compiled with - inline=0 . </p><p> + inline=0 . <p> - </p></li><li><strong>PharLap TNT Embedded ToolSuite (ETS)</strong><p> + <li><strong>PharLap TNT Embedded ToolSuite (ETS)</strong><p> - ACE has been ported to <a href="http://www.pharlap.com/">PharLap's</a> TNT Embedded + ACE has been ported to <a + href="http://www.pharlap.com">PharLap's</a> TNT Embedded ToolSuite (ETS) version 9.1. The port is being tested with - Microsoft Visual C++ 6.</p><p> To build for PharLap, use the + Microsoft Visual C++ 6.<p> To build for PharLap, use the ace/config-pharlap.h configuration file, and the instructions for building on Windows. Building the ACE library is the same as for regular Windows platforms, except you choose one of the PharLap @@ -689,11 +735,11 @@ global.features</a> file. binaries, see the tests directory. The tests_pharlap_msvc.lnk file is a LinkLoc commands file that the ACE tests are built with. It is likely that local sites may need to adjust this file - for their target environment.</p><p> + for their target environment.<P> -</p></li><li><strong>Mac OS X (10.2.x)</strong><p> +<li><strong>Mac OS X (10.2.x)</strong><p> - </p><p>ACE builds and runs on Mac OS X 10.2.x, but the following are + <p>ACE builds and runs on Mac OS X 10.2.x, but the following are needed to build it:</p> <p>1. The latest version of the Apple Developer Tools @@ -717,27 +763,29 @@ global.features</a> file. <p>The work to port ACE to Mac OS X was done by several people, John Zorko - <<a href="mailto:j.zorko@att.net">j.zorko@att.net</a>> is + <<A href="mailto:j.zorko@att.net">j.zorko@att.net</A>> is only one of them.</p> -</li></ul> +</UL> -<hr> -<h4><a name="g++">Compiling ACE with GNU g++</a></h4> +<HR> +<H4><A NAME="g++">Compiling ACE with GNU g++</A></H4> If you use the GNU GCC g++ compiler please note the following: -<ul> +<UL> <li>If you have problems building shared libraries with egcs 1.1 or 1.1.1 on SunOS 2.5 or 2.5.1 that look like this: - <pre> /usr/ccs/lib/libgen.a(reg_compile.o): In function `_get_vars_storage': + <pre> + /usr/ccs/lib/libgen.a(reg_compile.o): In function `_get_vars_storage': reg_compile.o(.text+0x30): relocation truncated to fit: R_SPARC_GOT13 free </pre> the suggested workaround is to comment out the <code>ACE_HAS_REGEX</code> <code>#define</code> in <code>ace/config-sunos5.5.h</code>. Or better, create an <code>ace/config.h</code> that looks like: - <pre> #ifndef ACE_CONFIG_H + <pre> + #ifndef ACE_CONFIG_H // ACE_CONFIG_H is defined by the following #included header. #include "ace/config-sunos5.5.h" @@ -749,14 +797,14 @@ If you use the GNU GCC g++ compiler please note the following: We don't know what causes the link problem, though the workaround solves it.<p> - </p></li><li>ACE/TAO don't seem to build well with g++ 2.8.*. We routinely + <li>ACE/TAO don't seem to build well with g++ 2.8.*. We routinely use g++ 2.95.x and g++ 3.x, and recommend those versions or better.<p> - </p></li><li>Earlier (prior to 2.95.2) versions of g++ may not compile + <LI>Earlier (prior to 2.95.2) versions of g++ may not compile certain parts of ACE correctly due to compiler bugs. Please - upgrade to g++ 2.95.2 or greater.<p> + upgrade to g++ 2.95.2 or greater.<P> - </p></li><li>Make sure to update your gcc <code>config.status</code> + <LI>Make sure to update your gcc <code>config.status</code> file. This file is produced when installing gcc; it specifies where to install the binary files that gcc uses. For example, it specifies whether to use Solaris's <code>/usr/ccs/bin</code> @@ -764,52 +812,52 @@ If you use the GNU GCC g++ compiler please note the following: <code>config.status</code> file is an output of the gcc <code>configure</code> script; it is preferable to use the <code>--prefix</code> option to <code>configure</code> instead - of hacking its output.<p> + of hacking its output.<P> - </p></li><li>If you are getting weird link errors when building libACE + <LI>If you are getting weird link errors when building libACE on Solaris you are probably using the GNU linker. Try using the Sun linker (/usr/ccs/bin/ld) instead. Note that gcc first looks for the GNU linker if it is installed along with gcc. The only way to not use the GNU linker is to delete it from the installation or to build your own compiler with no linker. Be - aware that you still need the libraries and includes of gcc.<p> + aware that you still need the libraries and includes of gcc.<P> NOTE: if you do use the GNU linker, you might need to change the <code>-G</code> flag to <code>-shared</code> in the <code>SOFLAGS</code> definition in your - <code>include/makeinclude/platform_macros.GNU</code>.</p><p> + <code>include/makeinclude/platform_macros.GNU</code>.<p> - </p></li><li>Don't get too confused about contradictory statements in + <LI>Don't get too confused about contradictory statements in the gcc documentation. It was written by different - people...<p> + people...<P> - </p></li><li>Make sure that the linker invoked by gcc produces code + <LI>Make sure that the linker invoked by gcc produces code that initializes static objects. Please see gcc's - documentation for using <code>collect2</code>.<p> + documentation for using <CODE>collect2</CODE>.<P> - </p></li><li>On VxWorks only, g++ (thru version 2.9.6, distributed + <LI>On VxWorks only, g++ (thru version 2.9.6, distributed with Tornado 2.2/VxWorks 5.5), for x86 targets, -fno-implicit-templates is broken. In addition, -O2 - is not supported on some targets.<p> -</p></li></ul> + is not supported on some targets.<P> +</UL> -<p></p><hr> -<h4><a name="egcs">Compiling ACE with egcs</a></h4> +<P><HR> +<H4><A NAME="egcs">Compiling ACE with egcs</A></H4> <ul> <li>ACE transparently supports egcs, for the most part. Please see <a href="#g++">Compiling ACE with g++</a> in this document. And, please use the appropriate g++ config and platform files for the OS on which you will use egcs.<p> - </p></li><li><strong><blink><font color="#ff0000">WARNING:</font></blink></strong> + <li><strong><blink><font color="#ff0000">WARNING:</font></blink></strong> The default behavior of the ACE Makefiles is to enable native exception support. To disable exception handling, add <code>exceptions=0</code> to your <code>make</code> command line invocation, or to your <code>$ACE_ROOT/include/makeinclude/platform_macros.GNU</code> file.<p> - </p></li><li>egcs may have trouble linking some executables, such as the ACE + <li>egcs may have trouble linking some executables, such as the ACE IOStream_Test, if its static libraries are used. Though <a href="mailto:trose@bridgewatersys.com">Tim Rose</a> reports that egcs 1.1.1 static libraries work just fine on Solaris 2.6 @@ -821,21 +869,21 @@ If you use the GNU GCC g++ compiler please note the following: <code>--enable-shared</code> option is <strong>not</strong> an egcs run-time option. Build egcs in a way similar to the following example: - </p><pre><code> + <pre><code> $ ./configure --enable-shared $ make bootstrap </code></pre> Be sure to set your <code>LD_LIBRARY_PATH</code> environment variable, if necessary, to pick up those shared libraries.<p> - </p></li><li>On DEC Alpha, egcs through version 1.03a, at least, may fail + <li>On DEC Alpha, egcs through version 1.03a, at least, may fail to build ACE if debugging (-g) is enabled. The fix is to edit the egcs gcc/mips-file.c file, at line 976, and change <code>PAGE_SIZE</code> to 8192. Then rebuild ACE. Thanks to <a href="mailto:gpai@voicetek.com">Ganesh Pai</a> for this information.<p> - </p></li><li>Sun OS 5.6 using egcs1.1.2/egcs 2.95 with + <li>Sun OS 5.6 using egcs1.1.2/egcs 2.95 with ld:Software Generation Utilities - Solaris/ELF (3.0) as: WorkShop Compilers 4.X dev 18 Sep 1996<p> @@ -843,7 +891,8 @@ If you use the GNU GCC g++ compiler please note the following: Example: - </p><pre> -I/opt/ace/SunOS-1.0 -DACE_HAS_EXCEPTIONS -o Cached_Accept_Conn_Test + <pre> + -I/opt/ace/SunOS-1.0 -DACE_HAS_EXCEPTIONS -o Cached_Accept_Conn_Test .obj/Cached_Accept_Conn_Test.o -L/opt/ace/SunOS-1.0/ace -L./ -lACE -lsocket -ldl -lgen -lnsl -lposix4 -lthread ld: warning: relocation error: R_SPARC_32: file @@ -854,36 +903,36 @@ If you use the GNU GCC g++ compiler please note the following: Client_Svc_HandlerZUiZt8ACE_Hash1Zt30...</pre> external symbolic relocation against non-allocatable section .stab; - cannot be processed at runtime: relocation ignored<p> + cannot be processed at runtime: relocation ignored<P> - Solution:</p><p> + Solution:<P> Install the "binutils" package from GNU (www.gnu.org); specifically, - "as" and "ld".</p><p> + "as" and "ld".<P> - Conclusion:</p><p> + Conclusion:<P> - Perfect build stats:</p><p> + Perfect build stats:<P> OS: - Kernel version: SunOS 5.6 Generic 105181-03 December 1999.</p><p> + Kernel version: SunOS 5.6 Generic 105181-03 December 1999.<P> compiler: - gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release)</p><p> + gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release)<P> loader: GNU ld version 2.9.1 (with BFD 2.9.1) Supported emulations: - elf32_sparc</p><p> + elf32_sparc<P> assembler: GNU assembler version 2.9.1 (sparc-sun-solaris2.6), using - BFD version 2.9.1</p><p> + BFD version 2.9.1<P> Thanks to <a href="mailto:johng@keck.hawii.edu">John Gathright</a> for providing this - information.</p><p> + information.<P> - </p></li><li>Compiling using the <code>-fsquangle</code> option helps to shorten long + <li>Compiling using the <code>-fsquangle</code> option helps to shorten long symbol names and is a boon to linkers and assemblers which cant grok long names. @@ -892,62 +941,62 @@ If you use the GNU GCC g++ compiler please note the following: option with egcs.<p> Heres a note on how to go about this (contributed by Skye - Sweeney):</p><p> + Sweeney):<p> - 1) -fsquangle the name is a combination of squash and mangle!</p><p> + 1) -fsquangle the name is a combination of squash and mangle!<p> - 2) -fsquangle compresses the mangled names.</p><p> + 2) -fsquangle compresses the mangled names.<p> 3) All libraries must be compiles with the option. You cannot simply compile modules that have large names with it. This includes system - libraries and vendor libraries like RogueWave.</p><p> + libraries and vendor libraries like RogueWave.<p> 4) The "simple" solution is not to add the option to each makefile, but rather recompile the compiler to have the option on by default. This is done by editing the file `gcc/cp/decl2.c', setting `flag_do_squangling = 1', then rebuilding the compiler and - libraries.</p><p> + libraries.<p> 5) After many false starts and linking snafus, I can recompile my - ACE/TAO/RogueWave/Lex/Yacc 100 Meg application.</p><p> + ACE/TAO/RogueWave/Lex/Yacc 100 Meg application.<p> -</p></li></ul> +</ul> -<p></p><hr> -<h3><a name="aceinstall">Building and Installing ACE</a></h3> +<P><HR> +<H3><A NAME="aceinstall">Building and Installing ACE</A></H3> -The following explains how to build ACE on <a href="#unix">UNIX</a> -and <a href="#win32">Windows</a>. +The following explains how to build ACE on <A HREF="#unix">UNIX</A> +and <A HREF="#win32">Windows</A>. <h4>General Rules</h4> -<ul> +<UL> <li><p>Many features in ACE can be modified by defining some macros in <code>$ACE_ROOT/ace/config.h</code>. These macros should <em><b>always</b></em> appear <em><b>before</b></em> including your platform specific config file.</p> - </li><li><p>However, if you want to undefine/redefine macros defined in the + <li><p>However, if you want to undefine/redefine macros defined in the platform specific config file, these <code>#undef</code> should come <em><b>after</b></em> the config file.</p> - </li><li> If you're planning to build ACE on multiple platforms, you may - want to consider <a href="#cloning">cloning the source tree</a> - before you start. <p> -</p></li></ul> + <LI> If you're planning to build ACE on multiple platforms, you may + want to consider <A HREF="#cloning">cloning the source tree</A> + before you start. <P> +</UL> -<hr align="left" width="50%"> -<h4><a name="unix">Building and Installing ACE on UNIX</a></h4> +<hr align=left width="50%"> +<H4><A NAME="unix">Building and Installing ACE on UNIX</A></H4> As of ACE 5.4, you can choose between two methods of building ACE on UNIX: -<ol> - <li><a href="#unix_autoconf">GNU Autoconf</a></li> - <li><a href="#unix_traditional">Traditional ACE/GNU Make Configuration</a></li> -</ol> -The <a href="#win32">build process</a> for Windows is different from both of +<OL> + <LI><A HREF="#unix_autoconf">GNU Autoconf</A></LI> + <LI><A HREF="#unix_traditional">Traditional ACE/GNU Make Configuration</A></LI> +</OL> +The <A HREF="#win32">build process</A> for Windows is different from both of the UNIX methods. -<h5><a name="unix_autoconf">Building ACE with GNU Autoconf</a></h5> -<p> +<H5><A NAME="unix_autoconf">Building ACE with GNU Autoconf</A></H5> +<P> GNU Autoconf support is available in the ACE only distribution in the DOC group website. More, precisely support for Autoconf will be missing in distributions that have TAO and CIAO bundled along. @@ -960,138 +1009,140 @@ your applications. The traditional configuration method is still more reliable. Any help you can lend to improve the ACE build process using GNU Autoconf would be very much appreciated. Please send any fixes to the -<a href="mailto:ace-users@cs.wustl.edu">ACE users</a> mailing list.</p> -<p> +<A HREF="mailto:ace-users@cs.wustl.edu">ACE users</A> mailing list.</P> +<P> The ACE only kit has been bootstrapped so you do not need to install the GNU Autotools (autoconf, automake, libtool) unless you want to participate in testing and developing this process further. To simply configure and build ACE, do: -</p><ol> - <li><code>cd</code> to the top-level <code>ACE_wrappers</code> directory.</li> - <li>Create a subdirectory to hold your build's configuration and built +<OL> + <LI><CODE>cd</CODE> to the top-level <CODE>ACE_wrappers</CODE> directory.</LI> + <LI>Create a subdirectory to hold your build's configuration and built ACE version, and then change to the new directory: - <pre> mkdir build + <pre> + mkdir build cd build </pre> Note that you do not run the <code>create_ace_build</code> utility - mentioned in the <a href="#cloning">Cloning the Source Tree</a> + mentioned in the <A HREF="#cloning">Cloning the Source Tree</A> section. The configure script takes care of creating all files - and links that are needed.</li> - <li>Configure ACE for your platform by issuing the following command: - <pre> ../configure [options] + and links that are needed.</LI> + <LI>Configure ACE for your platform by issuing the following command: + <pre> + ../configure [options] </pre> <code>options</code> can be a variable setting (such as setting <code>CXX</code> to your C++ compiler command) any standard GNU configure options, or any of the following ACE configure options (default values are in parentheses): - <ul> - <li><code>--enable-alloca</code> (no): Enable <code>alloca()</code> - support.</li> - <li><code>--enable-debug</code> (yes): Build ACE with debugging - support.</li> - <li><code>--enable-exceptions</code> (yes): Build ACE with C++ - exception support compiled in.</li> - <li><code>--enable-fast</code> (no): Use the Sun C++ <code>-fast</code> - option to build. Only used on Solaris.</li> - <li><code>--enable-ipv4-ipv6</code> (no): Enable IPv4/IPv6 migration support.</li> - <li><code>--enable-ipv6</code> (no): Enable IPv6 support.</li> - <li><code>--enable-inline</code> (yes): Enable inline functions.</li> - <li><code>--enable-optimize</code> (yes): Enable building optimized.</li> - <li><code>--enable-prof</code> (no): Enable profiling support.</li> - <li><code>--enable-purify</code> (no): Build with support for - IBM Rational Purify.</li> - <li><code>--enable-quantify</code> (no): Build with support for - IBM Rational Quantify.</li> - <li><code>--enable-repo</code> (no): Enable the GNU g++ - <code>-frepo</code> option. Only useful for pre-3.0 g++ and egcs.</li> - <li><code>--enable-rtti</code> (yes): Compile with C++ run-time type - information RTTI support.</li> - <li><code>--enable-stdcpplib</code> (yes): Build with support for the - standard C++ library, as opposed to the older iostreams library.</li> - <li><code>--enable-log-msg-prop</code> (yes): Enable + <UL> + <LI><code>--enable-alloca</code> (no): Enable <code>alloca()</code> + support.</LI> + <LI><code>--enable-debug</code> (yes): Build ACE with debugging + support.</LI> + <LI><code>--enable-exceptions</code> (yes): Build ACE with C++ + exception support compiled in.</LI> + <LI><code>--enable-fast</code> (no): Use the Sun C++ <code>-fast</code> + option to build. Only used on Solaris.</LI> + <LI><code>--enable-ipv4-ipv6</code> (no): Enable IPv4/IPv6 migration support.</LI> + <LI><code>--enable-ipv6</code> (no): Enable IPv6 support.</LI> + <LI><code>--enable-inline</code> (yes): Enable inline functions.</LI> + <LI><code>--enable-optimize</code> (yes): Enable building optimized.</LI> + <LI><code>--enable-prof</code> (no): Enable profiling support.</LI> + <LI><code>--enable-purify</code> (no): Build with support for + IBM Rational Purify.</LI> + <LI><code>--enable-quantify</code> (no): Build with support for + IBM Rational Quantify.</LI> + <LI><code>--enable-repo</code> (no): Enable the GNU g++ + <code>-frepo</code> option. Only useful for pre-3.0 g++ and egcs.</LI> + <LI><code>--enable-rtti</code> (yes): Compile with C++ run-time type + information RTTI support.</LI> + <LI><code>--enable-stdcpplib</code> (yes): Build with support for the + standard C++ library, as opposed to the older iostreams library.</LI> + <LI><code>--enable-log-msg-prop</code> (yes): Enable <code>ACE_Log_Msg</code> property propagation to ACE-created - threads.</li> - <li><code>--enable-logging</code> (yes): Enable the ACE logging - macros.</li> - <li><code>--enable-malloc-stats</code> (no): Compile in additional code - for collecting memory allocation statistics.</li> - <li><code>--enable-pi-pointers</code> (yes): Enable - position-independent pointers for shared memory classes.</li> - <li><code>--enable-probe</code> (no): Enable the - <code>ACE_Timeprobe</code> class.</li> - <li><code>--enable-reentrant</code> (yes): Enable use of platform's - reentrant functions.</li> - <li><code>--enable-static-obj-mgr</code> (yes): Enable use of a - static <code>ACE_Object_Manager</code>.</li> - <li><code>--enable-threads</code> (yes): Enable threading support.</li> - <li><code>--enable-verb-not-sup</code> (no): Enable verbose ENOTSUP - reports at run time.</li> - <li><code>--enable-trace</code> (no): Enable ACE execution tracing - support.</li> - <li><code>--enable-xt-reactor</code> (no): Enable support for the - <code>ACE_XtReactor</code> class.</li> - <li><code>--enable-fl-reactor</code> (no): Enable support for the - <code>ACE_FlReactor</code> class.</li> - <li><code>--with-gperf</code> (yes): Build the implementation of - gperf that comes with ACE.</li> - <li><code>--with-rmcast</code> (yes): Include the ACE_RMCast library - when building ACE.</li> - <li><code>--with-qos</code> (no): Include the ACE_QoS library when - building ACE.</li> - <li><code>--with-ssl</code> (yes): Include the ACE_SSL library when + threads.</LI> + <LI><code>--enable-logging</code> (yes): Enable the ACE logging + macros.</LI> + <LI><code>--enable-malloc-stats</code> (no): Compile in additional code + for collecting memory allocation statistics.</LI> + <LI><code>--enable-pi-pointers</code> (yes): Enable + position-independent pointers for shared memory classes.</LI> + <LI><code>--enable-probe</code> (no): Enable the + <code>ACE_Timeprobe</code> class.</LI> + <LI><code>--enable-reentrant</code> (yes): Enable use of platform's + reentrant functions.</LI> + <LI><code>--enable-static-obj-mgr</code> (yes): Enable use of a + static <code>ACE_Object_Manager</code>.</LI> + <LI><code>--enable-threads</code> (yes): Enable threading support.</LI> + <LI><code>--enable-verb-not-sup</code> (no): Enable verbose ENOTSUP + reports at run time.</LI> + <LI><code>--enable-trace</code> (no): Enable ACE execution tracing + support.</LI> + <LI><code>--enable-xt-reactor</code> (no): Enable support for the + <code>ACE_XtReactor</code> class.</LI> + <LI><code>--enable-fl-reactor</code> (no): Enable support for the + <code>ACE_FlReactor</code> class.</LI> + <LI><code>--with-gperf</code> (yes): Build the implementation of + gperf that comes with ACE.</LI> + <LI><code>--with-rmcast</code> (yes): Include the ACE_RMCast library + when building ACE.</LI> + <LI><code>--with-qos</code> (no): Include the ACE_QoS library when + building ACE.</LI> + <LI><code>--with-ssl</code> (yes): Include the ACE_SSL library when building ACE. Requires the SSL components to be available using the - compiler's and linker's default search directories.</li> - <li><code>--with-tli-device</code> (/dev/tcp): Specifies the device - name for opening a TLI device at run time.</li> - </ul> - </li> - <li>Build ACE by typing <code>make</code>. - </li><li>(Optional) Install ACE by typing <code>make install</code>. -</li></ol> - -<h5><a name="unix_traditional">Using the Traditional ACE/GNU Configuration</a></h5> -<p> + compiler's and linker's default search directories.</LI> + <LI><code>--with-tli-device</code> (/dev/tcp): Specifies the device + name for opening a TLI device at run time.</LI> + </UL> + </LI> + <LI>Build ACE by typing <code>make</code>. + <LI>(Optional) Install ACE by typing <code>make install</code>. +</OL> + +<H5><A NAME="unix_traditional">Using the Traditional ACE/GNU Configuration</A></H5> +<P> Here's what you need to do to build ACE using GNU Make and ACE's traditional -per-platform configuration method:</p> +per-platform configuration method:</P> -<ol> - <li>Install <a href="http://ftp.gnu.org/pub/gnu/make/">GNU make</a> +<OL> + <LI>Install <A HREF="http://ftp.gnu.org/pub/gnu/make/">GNU make</A> 3.79.1 or greater on your system (available via <code>http</code> anonymous <code>ftp</code> from <code>ftp.gnu.org</code> in the <code>pub/gnu/make/</code> directory). - You <em>must</em> use GNU make when using ACE's traditional - per-platform configuration method or ACE won't compile.<p> + You <EM>must</EM> use GNU make when using ACE's traditional + per-platform configuration method or ACE won't compile.<P> - </p></li><li>Add an environment variable called ACE_ROOT that contains the + <LI>Add an environment variable called ACE_ROOT that contains the name of the root of the directory where you keep the ACE wrapper source tree. The ACE recursive Makefile scheme needs this information. There are several ways to set the ACE_ROOT variable. For - instance, in my .login file for TSCH/CSH I have the following entry:<p> + instance, in my .login file for TSCH/CSH I have the following entry:<P> - </p><pre><code> + <pre><code> setenv ACE_ROOT /home/cs/faculty/schmidt/ACE_wrappers - </code></pre><p> + </code></pre><P> BTW, if you're running BASH or Bourne Shell you'll need to do the following: - </p><pre><code> + <pre><code> ACE_ROOT=/home/cs/faculty/schmidt/ACE_wrappers; export ACE_ROOT - </code></pre><p> + </code></pre><P> If you're building a number of versions of ACE, however, (e.g., for different OS platforms or for different releases of ACE) you might use the following approach (again assuming TCSH/CSH): - </p><pre><code> + <pre><code> setenv ACE_ROOT $cwd </code></pre> - </li><li>Create a configuration file, <code>$ACE_ROOT/ace/config.h</code>, + <LI>Create a configuration file, <code>$ACE_ROOT/ace/config.h</code>, that includes the appropriate platform/compiler-specific header configurations from the ACE source directory. For example: -<blockquote><code> +<BLOCKQUOTE><CODE> #include "ace/config-sunos5-sunc++-4.x.h" -</code></blockquote> +</CODE></BLOCKQUOTE> The platform/compiler-specific configuration file contains the #defines that are used throughout ACE to indicate which features your system supports. See the @@ -1099,170 +1150,173 @@ per-platform configuration method:</p> macro settings. If you desire to add some site-specific or build-specific changes, you can add them to your config.h file; place them <strong>before</strong> the inclusion of the platform-specific - header file.<p> + header file.<P> There are config files for most versions of UNIX. If there isn't a version of this file that matches your platform/compiler, you'll need to make one. Please send me email if you get it working so I can add it to the master ACE - release.</p><p> + release.<P> - </p></li><li>Create a build configuration file, + <LI>Create a build configuration file, <code>$ACE_ROOT/include/makeinclude/platform_macros.GNU</code>, that contains the appropriate platform/compiler-specific Makefile configurations, e.g., -<blockquote><code> +<BLOCKQUOTE><CODE> include $(ACE_ROOT)/include/makeinclude/platform_sunos5_sunc++.GNU -</code></blockquote> +</CODE></BLOCKQUOTE> This file contains the compiler and Makefile directives that are platform/compiler-specific. If you'd like to add make options, you - can add them before including the paltform-specific configuration.<p> + can add them before including the paltform-specific configuration.<P> - </p></li><li>Note that because ACE builds shared libraries, you'll need to set + <LI>Note that because ACE builds shared libraries, you'll need to set LD_LIBRARY_PATH to whereever you put the binary version of the ACE library. For example, you probably want to do something - like the following<p> + like the following<P> - </p><pre><code> + <pre><code> % setenv LD_LIBRARY_PATH $ACE_ROOT/ace:$ACE_ROOT/lib:$LD_LIBRARY_PATH - </code></pre><p> + </code></pre><P> - </p></li><li>When all this is done, hopefully all you'll need to do is type:<p> + <LI>When all this is done, hopefully all you'll need to do is type:<P> - </p><pre><code> + <pre><code> % make - </code></pre><p> + </code></pre><P> at the root of the ACE source tree. This will build the ACE library, tests, the examples, and the sample applications. Building the entire ACE release can take a long time and consume lots of disk space, however. Therefore, you might consider - cd'ing into the <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/ace">$ACE_ROOT/ace/</a> directory and - running <code>make</code> there to build just the ACE library. + cd'ing into the <A HREF="ace">$ACE_ROOT/ace/</a> directory and + running <CODE>make</CODE> there to build just the ACE library. As a sanity check, you might also want to build and run the - automated <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/tests/README">"one-button" tests</a> in <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/tests/">$ACE_ROOT/tests/</a>. Finally, if you're also - planning on building <a href="http://www.cs.wustl.edu/%7Eschmidt/TAO.html">TAO</a>, you - should build the <a href="http://www.cs.wustl.edu/%7Eschmidt/PDF/gperf.pdf">gperf</a> - perfect hash function generator application in <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/apps/gperf">$ACE_ROOT/apps/gperf/</a>.</p><p> + automated <A HREF="tests/README">"one-button" tests</A> in <A + HREF="tests/">$ACE_ROOT/tests/</a>. Finally, if you're also + planning on building <A + HREF="http://www.cs.wustl.edu/~schmidt/TAO.html">TAO</A>, you + should build the <A + HREF="http://www.cs.wustl.edu/~schmidt/PDF/gperf.pdf">gperf</A> + perfect hash function generator application in <A + HREF="apps/gperf">$ACE_ROOT/apps/gperf/</A>.<P> - </p></li><li>If you need to regenerate the Svc_Conf_y.cpp file, you'll need to - get <a href="http://ftp.gnu.org/pub/gnu/bison/">GNU Bison</a>. - However, you should rarely, if ever, need to do this.<p> + <LI>If you need to regenerate the Svc_Conf_y.cpp file, you'll need to + get <A HREF="http://ftp.gnu.org/pub/gnu/bison/">GNU Bison</A>. + However, you should rarely, if ever, need to do this.<P> -</p></li></ol> +</OL> -<p></p><hr align="left" width="50%"><p> -</p><h4><a name="win32">Building and Installing ACE on Windows</a></h4> +<P><hr align=left width="50%"><P> +<H4><A NAME="win32">Building and Installing ACE on Windows</A></H4> -Below are instructions for building ACE with <a href="#borland">Borland C++Builder</a>, <a href="#msvc">Microsoft -Visual C++</a>, <a href="#mingw">MinGw</a>, and <a href="#cygwin">Cygwin</a>.<p> +Below are instructions for building ACE with <A +HREF="#borland">Borland C++Builder</A>, <A HREF="#msvc">Microsoft +Visual C++</A>, <A HREF="#mingw">MinGw</A>, and <A HREF="#cygwin">Cygwin</A>.<P> First, if you are upgrading from an older release, clean up everything and rebuild from scratch to ensure that everything is rebuilt correctly. You might have to manually go through the ACE directories and delete all *.obj, *.dll, *.lib, *.ilk, *.pdb, *.idb, *.ncb, *.opt, and *.exp files in order to start over from scratch (the Clean command -in MSVC may not do this). </p><p> +in MSVC may not do this). <P> ACE contains project files for Microsoft Visual C++ 6.0 (*.dsp/.dsw) and Visual C++ .NET 2003 (*.vcproj/.sln). There are also Makefile.bor files to compile ACE, and the ACE one-button tests with -Borland C++ Builder. </p><p> +Borland C++ Builder. <P> -</p><p></p><hr align="left" width="50%"><p> -</p><h4><a name="borland">Building and Installing ACE on Windows with Borland -C++</a></h4> +<P><hr align=left width="50%"><P> +<H4><A NAME="borland">Building and Installing ACE on Windows with Borland +C++</A></H4> If you are building for a machine without a network card, you may want -to check <a href="#win32nonic">here</a> first. <p> +to check <A HREF="#win32nonic">here</A> first. <P> -</p><ol> - <li>Uncompress the ACE distribution into a directory, where it will +<OL> + <LI>Uncompress the ACE distribution into a directory, where it will create an ACE_wrappers directory containing the source. The ACE_wrappers directory will be referred to as ACE_ROOT in the following steps -- so ACE_ROOT\ace would be C:\ACE_wrappers\ace if you uncompressed into the - root directory.<br> - <br> - </li><li>Create a file called <code>config.h</code> in the ACE_ROOT\ace - directory that contains: <br> - <br> - <code>#include "ace/config-win32.h"</code><br> - <br> + root directory.<BR> + <BR> + <LI>Create a file called <code>config.h</code> in the ACE_ROOT\ace + directory that contains: <BR> + <BR> + <CODE>#include "ace/config-win32.h"</CODE><BR> + <BR> If you are building for Windows NT 4, Windows 2000, or Windows XP, then you can start without any more changes. If you are building - on Windows 9x/Me, then you should add the line <br> - <br> - <code>#define ACE_HAS_WINNT4 0</code><br> - <br> + on Windows 9x/Me, then you should add the line <BR> + <BR> + <CODE>#define ACE_HAS_WINNT4 0</CODE><BR> + <BR> before the #include statement in ACE_ROOT\ace\config.h and it - will turn off some WinNT/Win2K-specific code in ACE.<br> - <br> - </li><li>Open a Command Prompt (DOS Box).<br> - <br> - </li><li>Set the ACE_ROOT environment variable to point to the ACE_wrappers - directory. For example:<br> - <br> - <code>set ACE_ROOT=C:\ACE_wrappers</code><br> - <br> - </li><li>Set the BCBVER environment vairable to the main version of your Borland C++ compiler. - Currently only 6 is supported, 4 and 5 are options but not supported. For example:<br> - <br> - <code>set BCBVER=6</code><br> - <br> - </li><li>Change to the ACE_ROOT\ace directory.<br> - <br> - </li><li>Build release DLLs for ACE by going:<br> - <br> - <code>make -f Makefile.bor all</code><br> - <br> - </li><li>You can build several different versions of ACE by setting environment + will turn off some WinNT/Win2K-specific code in ACE.<BR> + <BR> + <LI>Open a Command Prompt (DOS Box).<BR> + <BR> + <LI>Set the ACE_ROOT environment variable to point to the ACE_wrappers + directory. For example:<BR> + <BR> + <CODE>set ACE_ROOT=C:\ACE_wrappers</CODE><BR> + <BR> + <LI>Set the BCBVER environment vairable to the main version of your Borland C++ compiler. + Currently only 6 is supported, 4 and 5 are options but not supported. For example:<BR> + <BR> + <CODE>set BCBVER=6</CODE><BR> + <BR> + <LI>Change to the ACE_ROOT\ace directory.<BR> + <BR> + <LI>Build release DLLs for ACE by going:<BR> + <BR> + <CODE>make -f Makefile.bor all</CODE><BR> + <BR> + <LI>You can build several different versions of ACE by setting environment variables - before you run make:<br> - <br> - Set the environment variable below to build a debug version of ACE<br> - <code>set DEBUG=1</code><br> - <br> - Set the environment variable below to build a static version of ACE<br> - <code>set STATIC=1</code><br> - <br> - Set the environment variable below to build a unicode version of ACE<br> - <code>set UNICODE=1</code><br> - <br> -Set the environment variable below to build a version of ACE with -Codeguard support. Should only be used when DEBUG is also set<br> - <code>set CODEGUARD=1</code><br> - <br> -Set the environment variable below to build a version of ACE that is -build against the VCL-compatible run-time library. This can only be -used with BCB version 4<br> - <code>set PASCAL=1</code><br> - <br> + before you run make:<BR> + <BR> + Set the environment variable below to build a debug version of ACE<BR> + <CODE>set DEBUG=1</CODE><BR> + <BR> + Set the environment variable below to build a static version of ACE<BR> + <CODE>set STATIC=1</CODE><BR> + <BR> + Set the environment variable below to build a unicode version of ACE<BR> + <CODE>set UNICODE=1</CODE><BR> + <BR> + Set the environment variable below to build a version of ACE with Codeguard support. Should only be used when DEBUG is also set<BR> + <CODE>set CODEGUARD=1</CODE><BR> + <BR> + Set the environment variable below to build a version of ACE that is build against the VCL-compatible run-time library. This can only be used with BCB version 4<BR> + <CODE>set PASCAL=1</CODE><BR> + <BR> Set the environment variable below to build a version of ACE using the C++BuilderX preview compiler. This compiler isn't supported at this moment but by setting this environment variable the new compiler is used and - you can expirement with this compiler.<br> - <code>set CBX=1</code><br> - <br> + you can expirement with this compiler.<BR> + <CODE>set CBX=1</CODE><BR> + <BR> You can then start the build with the command - <br><code>make -f Makefile.bor</code><br> - <br> - You may also enable the options by passing them as command line options to make, for example:<br> - <code>make -f Makefile.bor -DDEBUG -DPASCAL</code><br> - <br> - </li><li>Optionally install the ACE header files, libraries and executables + <BR><CODE>make -f Makefile.bor</CODE><BR> + <BR> + You may also enable the options by passing them as command line options to make, for example:<BR> + <CODE>make -f Makefile.bor -DDEBUG -DPASCAL</CODE><BR> + <BR> + <LI>Optionally install the ACE header files, libraries and executables for use - in your applications. Here we are installing them into C:\ACETAO: <br> - <br> - <code>make -f Makefile.bor -DINSTALL_DIR=C:\ACETAO install</code><br> - <br> -</li></ol> + in your applications. Here we are installing them into C:\ACETAO: <BR> + <BR> + <CODE>make -f Makefile.bor -DINSTALL_DIR=C:\ACETAO install</CODE><BR> + <BR> +</OL> These instructions do not cover all possible build configurations. Please -see <a href="http://www.tenermerx.com/tao_bcb/index.html">http://www.tenermerx.com/tao_bcb/index.html</a> +see <A +HREF="http://www.tenermerx.com/tao_bcb/index.html">http://www.tenermerx.com/tao_bcb/index.html</A> for more detailed information on building and using ACE+TAO with Borland C++ -Builder. <p> +Builder. <P> If you are using C++Builder 4, then the libraries built using the above instructions are intended for use with generic console or windows applications @@ -1271,82 +1325,85 @@ created using BCB4's RAD environment must link against the VCL-compatible (ie pascal-compatible) runtime library. To tell the difference between these libraries the VCL-compatible ones have a 'p' in the suffix (i.e., 'p' for pascal). To build VCL compatible libraries try -</p><blockquote><pre><code>set PASCAL=1 +<BLOCKQUOTE><PRE><CODE>set PASCAL=1 make -f Makefile.bor -</code></pre></blockquote> <p> +</CODE></PRE></BLOCKQUOTE> <P> -The Borland C++ Builder 4.0/5.0/6.0 port has been done by <a href="mailto:jody@atdesk.com">Jody Hagins</a>, <a href="mailto:chris@kohlhoff.com">Christopher Kohlhoff</a> and <a href="mailto:jwillemsen@remedy.nl">Johnny Willemsen</a>. </p><p> +The Borland C++ Builder 4.0/5.0/6.0 port has been done by <A +HREF="mailto:jody@atdesk.com">Jody Hagins</A>, <A +HREF="mailto:chris@kohlhoff.com">Christopher Kohlhoff</A> and <A +HREF="mailto:jwillemsen@remedy.nl">Johnny Willemsen</A>. <P> -<b>ACE TESTS</b></p><p> +<B>ACE TESTS</B><P> The tests are located in ACE_ROOT\tests. You build the tests using the -Makefile.bor file, that is:</p><p> -</p><blockquote><code> +Makefile.bor file, that is:<P> +<BLOCKQUOTE><CODE> make -f Makefile.bor -</code></blockquote><p> +</CODE></BLOCKQUOTE><P> -Once you build all the tests, you can run the perl script:</p><p> -</p><blockquote><code>run_test.pl</code></blockquote><p> in the +Once you build all the tests, you can run the perl script:<P> +<BLOCKQUOTE><CODE>run_test.pl</CODE></BLOCKQUOTE><P> in the <code>tests</code> directory to try all the tests. You need to make sure the ACE bin and lib directory (in this case -<code>ACE_ROOT\bin</code> and <code>ACE_ROOT\lib</code>) -are on the path before you try to run the tests.</p><p> +<CODE>ACE_ROOT\bin</CODE> and <CODE>ACE_ROOT\lib</CODE>) +are on the path before you try to run the tests.<p> -</p><p></p><hr align="left" width="50%"><p> -</p><h4><a name="msvc">Building and Installing ACE on Windows with -Microsoft Visual C++</a></h4> +<P><hr align=left width="50%"><P> +<H4><A NAME="msvc">Building and Installing ACE on Windows with +Microsoft Visual C++</A></H4> -<ol> - <li>Uncompress the ACE distribution into a directory, where it will +<OL> + <LI>Uncompress the ACE distribution into a directory, where it will create a ACE_wrappers directory containing the distribution. The ACE_wrappers directory will be referred to as ACE_ROOT in the following steps -- so ACE_ROOT\ace would be C:\ACE_wrappers\ace if - you uncompressed into the root directory.<br> - <br> - </li><li>Create a file called <code>config.h</code> in the ACE_ROOT\ace - directory that contains: <br> - <br> - <code>#include "ace/config-win32.h"</code><br> - <br> - - </li><li>The static, DLL and MFC library builds are kept in + you uncompressed into the root directory.<BR> + <BR> + <LI>Create a file called <code>config.h</code> in the ACE_ROOT\ace + directory that contains: <BR> + <BR> + <CODE>#include "ace/config-win32.h"</CODE><BR> + <BR> + + <LI>The static, DLL and MFC library builds are kept in different workspaces. Files with names *_Static contain project files for static builds. Workspaces for static and DLL builds will be available through the stock release at DOC group's website. The workspaces for MFC are not available and have to be generated using - MPC. Please see <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/MPC/README">MPC's README</a> for - details.<br> - </li><li>Now load the workspace file for ACE (ACE_ROOT/ACE.dsw).<br> - <br> - </li><li>Make sure you are building the configuration (i.e, Debug/Release) + MPC. Please see <A HREF=MPC/README>MPC's README</A> for + details.<BR> + <LI>Now load the workspace file for ACE (ACE_ROOT/ACE.dsw).<BR> + <BR> + <LI>Make sure you are building the configuration (i.e, Debug/Release) the one you'll use (for example, the debug tests need the debug version of ACE, and so on). All these different configurations are provided for your convenience. You can either adopt the scheme to build your applications with different configurations, or use <code>ace/config.h</code> to tweak with the default settings on - NT.<br> <strong>Note:</strong> If you use the dynamic libraries, + NT.<BR> <STRONG>Note:</STRONG> If you use the dynamic libraries, make sure you include ACE_ROOT\lib in your PATH whenever you run programs that uses ACE. Otherwise you may experience problems - finding ace.dll or aced.dll.<br> - <br> - </li><li>If you are building for Windows NT 4 or later (Windows 2000, XP, etc.) + finding ace.dll or aced.dll.<BR> + <BR> + <LI>If you are building for Windows NT 4 or later (Windows 2000, XP, etc.) then you can start building without anymore changes. If you are building - on Windows 9x/Me, then you should add the line <br> - <br> - <code>#define ACE_HAS_WINNT4 0</code><br> - <br> + on Windows 9x/Me, then you should add the line <BR> + <BR> + <CODE>#define ACE_HAS_WINNT4 0</CODE><BR> + <BR> before the #include statement in ACE_ROOT\ace\config.h and it - will turn off some WinNT/Win2K-specific code in ACE.<br> - <br> - </li><li>If you want to use the standard C++ headers (iostream, cstdio, ... + will turn off some WinNT/Win2K-specific code in ACE.<BR> + <BR> + <li>If you want to use the standard C++ headers (iostream, cstdio, ... as defined by the C++ Standard Draft 2) that comes with MSVC, - then add the line: <br> - <br> - <code>#define ACE_HAS_STANDARD_CPP_LIBRARY 1</code><br> - <br> - before the #include statement in ACE_ROOT\ace\config.h.<br> + then add the line: <BR> + <BR> + <CODE>#define ACE_HAS_STANDARD_CPP_LIBRARY 1</CODE><BR> + <BR> + before the #include statement in ACE_ROOT\ace\config.h.<BR> <br> - </li><li>To use ACE with MFC libraries, also add the following to + <li>To use ACE with MFC libraries, also add the following to your <code>config.h</code> file. Notice that if you want to spawn a new thread with CWinThread, make sure you spawn the thread with THR_USE_AFX flag set.<br> @@ -1363,424 +1420,446 @@ Microsoft Visual C++</a></h4> <code>config.h</code> file. However, if you would like to link everything (including the MSVC run-time libraries) statically, you'll need to modify the project files in ACE yourself.<p> - </p></li><li>Static version of ACE libraries are built with + <li>Static version of ACE libraries are built with <code>ACE_AS_STATIC_LIBS</code><br> defined. This macro should also be used in application projects that link to static ACE - libraries<br> - <br> - Optionally you can also add the line <br> - <br> - <code>#define ACE_NO_INLINE</code><br> - <br> + libraries<BR> + <BR> + Optionally you can also add the line <BR> + <BR> + <CODE>#define ACE_NO_INLINE</CODE><BR> + <BR> before the #include statement in ACE_ROOT\ace\config.h to disable inline function and reduce the size of static libraries (and your - executables.)<br> - <br> - </li><li>ACE DLL and LIB naming scheme:<br> + executables.)<BR> + <BR> + <li>ACE DLL and LIB naming scheme:<br> <br> We use the following rules to name the DLL and LIB files in ACE when using MSVC.<br> <br> - "Library/DLL name" + (Is static library ? "s" : - "") + (Is Debugging enable ? "d" : "") - + {".dll"|".lib"}<br> + "Library/DLL name" + (Is static library ? "s" : + "") + (Is Debugging enable ? "d" : "") + + {".dll"|".lib"}<br> <br> -</li></ol> +</Ol> -<p>More information for ACE/TAO on MSVC can be found -<a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/docs/msvc_notes.txt">here</a>. The doxygen version of this -document is available under Related Topics in the ACE Library.</p> +<P>More information for ACE/TAO on MSVC can be found +<A HREF="docs/msvc_notes.txt">here</A>. The doxygen version of this +document is available under Related Topics in the ACE Library.</P> -<b>ACE TESTS</b><p> +<B>ACE TESTS</B><P> The tests are located in ACE_ROOT\tests. There is also a workspace in -that directory to build all the tests (tests.dsw)</p><p> +that directory to build all the tests (tests.dsw)<P> Once you build all the tests (Batch Build works well for this), you can run perl script <code>run_test.pl</code> in the -<code>tests</code> directory to try all the tests.</p><p> +<code>tests</code> directory to try all the tests.<p> -<a name="win32nonic"> -<b> BUILDING ACE ON A WIN32 MACHINE THAT LACKS A NETWORK CARD </b></a></p><p> +<A NAME="win32nonic"> +<B> BUILDING ACE ON A WIN32 MACHINE THAT LACKS A NETWORK CARD </B><P> -<a name="win32nonic">You may want to run ACE on a non-networked machine. To do so, you must +You may want to run ACE on a non-networked machine. To do so, you must install TCP/IP and configure it to ignore the absence of a network card. This is one method: -</a></p><ol> -<a name="win32nonic"> <li>Run Control Panel - </li><li>Choose Network from Control Panel - </li><li>Add Adapter: MS Loopback Adapter - </li><li>Configure MS Loopback Adapter with 802.3 (default) - </li><li>Add Protocol: TCP/IP Protocol - </li><li>Configure TCP/IP Protocol with a valid IP address and subnet mask. +<OL> + <LI>Run Control Panel + <LI>Choose Network from Control Panel + <LI>Add Adapter: MS Loopback Adapter + <LI>Configure MS Loopback Adapter with 802.3 (default) + <LI>Add Protocol: TCP/IP Protocol + <LI>Configure TCP/IP Protocol with a valid IP address and subnet mask. Leave everything else at the default settings. - </li><li>Add Service: Workstation - </li><li>Exit and Restart System - </li><li>Run Control Panel again - </li><li>Choose Services from Control Panel - </li><li>The following services are not necessary and may - be set to Disabled Startup: <br> - Alerter<br> - Computer Browser<br> - Net logon<br> - Messanger<br> - </li><li>Choose Network from Control Panel - </li><li>Confirm the following setup. This is all you need to run ACE:<br> - Installed Software:<br> - Computer Browser<br> - MS Loopback Adapter Driver<br> - TCP/IP Protocol<br> - Workstation<br> - Installed Adapter Cards:<br> - MS Loopback Adapter<p> -</p></li></a></ol> - -<a name="win32nonic"><b>WIN32 ALPHA CONFIGURATIONS</b> - -</a><p><a name="win32nonic">The project files for Visual C++ no longer contain any configurations + <LI>Add Service: Workstation + <LI>Exit and Restart System + <LI>Run Control Panel again + <LI>Choose Services from Control Panel + <LI>The following services are not necessary and may + be set to Disabled Startup: <BR> + Alerter<BR> + Computer Browser<BR> + Net logon<BR> + Messanger<BR> + <LI>Choose Network from Control Panel + <LI>Confirm the following setup. This is all you need to run ACE:<BR> + Installed Software:<BR> + Computer Browser<BR> + MS Loopback Adapter Driver<BR> + TCP/IP Protocol<BR> + Workstation<BR> + Installed Adapter Cards:<BR> + MS Loopback Adapter<P> +</OL> + +<B>WIN32 ALPHA CONFIGURATIONS</B> + +<P>The project files for Visual C++ no longer contain any configurations targetted to Windows NT on the DEC Alpha. Below are the steps needed to -recreate the Alpha configurations:</a></p> - -<ol> -<a name="win32nonic"> <li>Load the project on the Alpha machine. - </li><li>Go to the Build menu and then select Configurations. - </li><li>Select the project that you want to convert. - </li><li>Click on Add. - </li><li>Select the x86 configuration to "Copy settings from" +recreate the Alpha configurations:</P> + +<OL> + <LI>Load the project on the Alpha machine. + <LI>Go to the Build menu and then select Configurations. + <LI>Select the project that you want to convert. + <LI>Click on Add. + <LI>Select the x86 configuration to "Copy settings from" (either Debug or Release versions). - </li><li>Prepend "Alpha " to the beginning of the name under - "Configuration". - </li><li>Click OK. - </li><li>Close the "Configurations" window. - </li><li>Now go to the Project settings. - </li><li>For the General Settings, change the output directories to standard ACE - output directories. Intermediate Directories are "Debug" and - "Release" in most cases. The Output Directories are blank, + <LI>Prepend "Alpha " to the beginning of the name under + "Configuration". + <LI>Click OK. + <LI>Close the "Configurations" window. + <LI>Now go to the Project settings. + <LI>For the General Settings, change the output directories to standard ACE + output directories. Intermediate Directories are "Debug" and + "Release" in most cases. The Output Directories are blank, except for Release versions of executables, in which it is also - "Release". - </li><li>For the C/C++ Settings, make sure that the Code Generation's runtime - library is set to "Multithreaded DLL" or "Debug Multithreaded - DLL". -</li></a></ol> + "Release". + <LI>For the C/C++ Settings, make sure that the Code Generation's runtime + library is set to "Multithreaded DLL" or "Debug Multithreaded + DLL". +</OL> -<p><a name="win32nonic"><b>Note:</b> MSVC 6 has a bug where if a .dsp is converted from version 5 to 6 on +<P><B>Note:</B> MSVC 6 has a bug where if a .dsp is converted from version 5 to 6 on x86, the Alpha configuration can get corrupted. This seems to happen when additional include or library directories are specified using backslashes instead of forward -slashes. If this occurs, the easiest way to fix it is to recreate it.</a></p> +slashes. If this occurs, the easiest way to fix it is to recreate it.</P> -<p></p><hr align="left" width="50%"><p> -</p><h4><a name="mingw">Building and Installing ACE on Win32 with MinGW/ MSYS</a></h4> +<P><hr align=left width="50%"><P> +<H4><A NAME="mingw">Building and Installing ACE on Win32 with MinGW/ MSYS</A></H4> <p> If you are building for a machine without a network card, you may want -to check <a href="#win32nonic">here</a> first. +to check <A HREF="#win32nonic">here</A> first. -</p><p> -Building and installing ACE on <a href="http://www.mingw.org/">MinGW</a> -uses a mix of a <a href="#unix">UNIX</a> building process and -<a href="#win32">Win32</a> configuration files. +<p> +Building and installing ACE on <A HREF="http://www.mingw.org">MinGW</A> +uses a mix of a <A HREF="#unix">UNIX</A> building process and +<A HREF="#win32">Win32</A> configuration files. Also, as MinGW uses GNU g++, you may want to take -a look at the <a href="#g++">Compiling ACE with GNU g++</a> section. +a look at the <A HREF="#g++">Compiling ACE with GNU g++</A> section. -</p><p> +<p> You will need the MinGW build tools and libraries, downloable from -<a href="http://www.mingw.org/"><tt>http://www.mingw.org</tt></a>. +<A HREF="http://www.mingw.org"><TT>http://www.mingw.org</TT></A>. -<br> +<BR> For our build we require the packages -<b><tt>MinGW</tt></b> and <b><tt>MSYS</tt></b>. +<B><TT>MinGW</TT></B> and <B><TT>MSYS</TT></B>. -</p><ol> +<OL> - <li> Install the MinGW tools into a common directory, say c:/mingw. - <br><br> + <LI> Install the MinGW tools into a common directory, say c:/mingw. + <BR><BR> - </li><li> Install the MSYS tools into a common directory, say c:/msys. - <br><br> + <LI> Install the MSYS tools into a common directory, say c:/msys. + <BR><BR> - </li><li> Open a MSYS shell. Set your <tt>PATH</tt> environment variable so - your MinGW's <tt>bin</tt> directory is first: + <LI> Open a MSYS shell. Set your <TT>PATH</TT> environment variable so + your MinGW's <TT>bin</TT> directory is first: - <blockquote><code></code><pre> % export PATH=/c/mingw/bin:$PATH - </pre></blockquote> + <blockquote><code><pre> + % export PATH=/c/mingw/bin:$PATH + </pre></code></blockquote> - </li><li> Add an <tt>ACE_ROOT</tt> environment variable pointing to the + <LI> Add an <TT>ACE_ROOT</TT> environment variable pointing to the root of your ACE wrappers source tree: - <blockquote><code></code><pre> % export ACE_ROOT=/c/work/mingw/ACE_wrappers - </pre></blockquote> + <blockquote><code><pre> + % export ACE_ROOT=/c/work/mingw/ACE_wrappers + </pre></code></blockquote> From now on, we will refer to the root directory of the ACE - source tree as <tt>$ACE_ROOT</tt>. - <br><br> + source tree as <TT>$ACE_ROOT</TT>. + <BR><BR> - </li><li> Create a file called <tt>config.h</tt> in the - <tt>$ACE_ROOT/ace</tt> directory that contains: + <LI> Create a file called <TT>config.h</TT> in the + <TT>$ACE_ROOT/ace</TT> directory that contains: - <blockquote><code></code><pre> #include "ace/config-win32.h" - </pre></blockquote> + <blockquote><code><pre> + #include "ace/config-win32.h" + </pre></code></blockquote> - If you are building for Windows 9X/Me (ie, <em>not</em> WinNT or + If you are building for Windows 9X/Me (ie, <EM>not</EM> WinNT or Win2K), you will need to add: - <blockquote><code></code><pre> #define ACE_HAS_WINNT4 0 - </pre></blockquote> + <blockquote><code><pre> + #define ACE_HAS_WINNT4 0 + </pre></code></blockquote> - before the <code>#include</code> line. - <br><br> + before the <CODE>#include</CODE> line. + <BR><BR> - </li><li> Create a file called <tt>platform_macros.GNU</tt> in the - <tt>$ACE_ROOT/include/makeinclude</tt> directory containing: + <LI> Create a file called <TT>platform_macros.GNU</TT> in the + <TT>$ACE_ROOT/include/makeinclude</TT> directory containing: - <blockquote><code></code><pre> include $(ACE_ROOT)/include/makeinclude/platform_mingw32.GNU - </pre></blockquote> + <blockquote><code><pre> + include $(ACE_ROOT)/include/makeinclude/platform_mingw32.GNU + </pre></code></blockquote> - In the above text, don't replace <tt>$(ACE_ROOT)</tt> with the + In the above text, don't replace <TT>$(ACE_ROOT)</TT> with the actual directory, GNU make will take the value from the environment variable you defined previously. <p> If you lack Winsock 2, add the line - </p><blockquote><code></code><pre> winsock2 = 0 - </pre></blockquote> + <blockquote><code><pre> + winsock2 = 0 + </pre></code></blockquote> before the previous one. - <br><br> + <BR><BR> - </li><li> In the MSYS shell, change to the $ACE_ROOT/ace directory and + <LI> In the MSYS shell, change to the $ACE_ROOT/ace directory and run make: - <blockquote><code></code><pre> % cd $ACE_ROOT/ace + <blockquote><code><pre> + % cd $ACE_ROOT/ace % make - </pre></blockquote> + </pre></code></blockquote> <p> - This should create <tt>libACE.dll</tt> (the Win32 shared library) and - <tt>libACE.dll.a</tt> (the Win32 import library for the DLL). + This should create <TT>libACE.dll</TT> (the Win32 shared library) and + <TT>libACE.dll.a</TT> (the Win32 import library for the DLL). Note that the name for the ACE DLL follows the MinGW convention, which itself resembles UNIX. - </p><p> + <p> If you want static libs also, you may run: - </p><blockquote><code></code><pre> % make static_libs=1 - </pre></blockquote> + <blockquote><code><pre> + % make static_libs=1 + </pre></code></blockquote> - </li><li> <a name="mingwrunpath"> + <LI> <A NAME="mingwrunpath"> The same rules for Win32 search of DLLs apply for MinGW. If you want to run some ACE programs from the MSYS shell, you may - need to add the directory for <tt>libACE.dll</tt> to your PATH: + need to add the directory for <TT>libACE.dll</TT> to your PATH: - </a><blockquote><code></code><pre><a name="mingwrunpath"> % export PATH=/c/work/mingw/ACE_wrappers/ace:$PATH - </a></pre></blockquote> + <blockquote><code><pre> + % export PATH=/c/work/mingw/ACE_wrappers/ace:$PATH + </pre></code></blockquote> -</li></ol> +</OL> -<a name="mingwrunpath"><b>ACE TESTS</b></a><p> +<B>ACE TESTS</B><P> -<a name="mingwrunpath">The tests are located in <tt>$ACE_ROOT/tests</tt>. +The tests are located in <TT>$ACE_ROOT/tests</TT>. After building the library, you can change to that directory and run make: - </a></p><blockquote><code></code><pre><a name="mingwrunpath"> % cd $ACE_ROOT/tests + <blockquote><code><pre> + % cd $ACE_ROOT/tests % make - </a></pre></blockquote> + </pre></code></blockquote> <p> -<a name="mingwrunpath">Once you build all the tests, you can run +Once you build all the tests, you can run <code>run_tests.pl</code> in the <code>tests</code> directory to try all the tests: - </a></p><blockquote><code></code><pre><a name="mingwrunpath"> % perl run_test.pl - </a></pre></blockquote> + <blockquote><code><pre> + % perl run_test.pl + </pre></code></blockquote> <p> -<a name="mingwrunpath">If you are using ACE as a DLL, you will need to modify your PATH -variable as explained </a><a href="#mingwrunpath">above</a>. +If you are using ACE as a DLL, you will need to modify your PATH +variable as explained <A HREF="#mingwrunpath">above</A>. -</p><p> +<p> You may want to check <tt>$ACE_ROOT/tests/README</tt> for the status of the various tests on MinGW and the different Windows flavors. -</p><p></p><hr align="left" width="50%"><p> -</p><h4><a name="cygwin">Building and Installing ACE on Win32 with Cygwin</a></h4> +<P><hr align=left width="50%"><P> +<H4><A NAME="cygwin">Building and Installing ACE on Win32 with Cygwin</A></H4> <p> If you are building for a machine without a network card, you may want -to check <a href="#win32nonic">here</a> first. +to check <A HREF="#win32nonic">here</A> first. -</p><p> -Building and installing ACE on <a href="http://www.cygwin.com/">Cygwin</a> -uses the <a href="#unix">UNIX</a> building process. +<p> +Building and installing ACE on <A HREF="http://www.cygwin.com">Cygwin</A> +uses the <A HREF="#unix">UNIX</A> building process. Also, as Cygwin uses GNU g++, you may want to take -a look at the <a href="#g++">Compiling ACE with GNU g++</a> section. +a look at the <A HREF="#g++">Compiling ACE with GNU g++</A> section. -</p><p> +<p> You will need the Cygwin build tools and libraries, downloable from -<a href="http://www.cygwin.com/"><tt>http://www.cygwin.com</tt></a>. +<A HREF="http://www.cygwin.com"><TT>http://www.cygwin.com</TT></A>. For our build we require the following packages besides the packages the setup selects by default: -<a name="cygwinpacks"> -</a></p><blockquote> -<a name="cygwinpacks"><b><tt>gcc (version 3.3.3), cygipc, make, perl</tt></b>. -</a></blockquote> +<A NAME="cygwinpacks"> +<blockquote> +<B><TT>gcc (version 3.2.3), cygipc, make, perl</TT></B>. +</blockquote> -<ol> +<OL> -<a name="cygwinpacks"> <li> Install Cygwin (this can be easy downloading and running - </li></a><a href="http://cygwin.com/setup.exe"><tt>setup.exe</tt></a> + <LI> Install Cygwin (this can be easy downloading and running + <A HREF="http://cygwin.com/setup.exe"><tt>setup.exe</tt></A> from the Cygwin site). For working with ACE we recommend to select <code>DOS</code> as default text file type. - <br><br> + <BR><BR> - <li> Open a Cygwin shell. Set your <tt>PATH</tt> environment variable so - your CYgwin <tt>bin</tt> directory is first: + <LI> Open a Cygwin shell. Set your <TT>PATH</TT> environment variable so + your CYgwin <TT>bin</TT> directory is first: - <blockquote><code></code><pre> % export PATH=//c/cygwin/bin:$PATH - </pre></blockquote> + <blockquote><code><pre> + % export PATH=//c/cygwin/bin:$PATH + </pre></code></blockquote> <p> - Note Cygwin uses ``<tt>/</tt>'' as directory separator, - and ``<tt>//X</tt>'' as a notation for Win32 drive <tt>X</tt>. - Note also that you <em>can't</em> use ``<tt>c:/cygwin/bin</tt>'' + Note Cygwin uses ``<TT>/</TT>'' as directory separator, + and ``<TT>//X</TT>'' as a notation for Win32 drive <TT>X</TT>. + Note also that you <EM>can't</EM> use ``<TT>c:/cygwin/bin</TT>'' because, for Cygwin, - ``<tt>:</tt>'' is path separator character, as in UNIX. - <br><br> + ``<TT>:</TT>'' is path separator character, as in UNIX. + <BR><BR> - </p></li><li> Add an <tt>ACE_ROOT</tt> environment variable pointing to the + <LI> Add an <TT>ACE_ROOT</TT> environment variable pointing to the root of your ACE wrappers source tree: - <blockquote><code></code><pre> % export ACE_ROOT=c:/work/cygwin/ACE_wrappers - </pre></blockquote> + <blockquote><code><pre> + % export ACE_ROOT=c:/work/cygwin/ACE_wrappers + </pre></code></blockquote> <p> - Note here you <em>can't</em> use the ``<tt>//X</tt>'' Cygwin + Note here you <EM>can't</EM> use the ``<TT>//X</TT>'' Cygwin notation as this is seen by Cygwin's compiler and it doesn't - support that (it <em>does</em> support ``<tt>/</tt>'' as directory + support that (it <EM>does</EM> support ``<TT>/</TT>'' as directory separator however). - </p><p> + <p> From now on, we will refer to the root directory of the ACE - source tree as <tt>$ACE_ROOT</tt>. - <br><br> + source tree as <TT>$ACE_ROOT</TT>. + <BR><BR> - </p></li><li> Create a file called <tt>config.h</tt> in the - <tt>$ACE_ROOT/ace</tt> directory that contains: + <LI> Create a file called <TT>config.h</TT> in the + <TT>$ACE_ROOT/ace</TT> directory that contains: - <blockquote><code></code><pre> #include "ace/config-cygwin32.h" - </pre></blockquote> + <blockquote><code><pre> + #include "ace/config-cygwin32.h" + </pre></code></blockquote> - </li><li> Create a file called <tt>platform_macros.GNU</tt> in the - <tt>$ACE_ROOT/include/makeinclude</tt> directory containing: + <LI> Create a file called <TT>platform_macros.GNU</TT> in the + <TT>$ACE_ROOT/include/makeinclude</TT> directory containing: - <blockquote><code></code><pre> include $(ACE_ROOT)/include/makeinclude/platform_cygwin32.GNU - </pre></blockquote> + <blockquote><code><pre> + include $(ACE_ROOT)/include/makeinclude/platform_cygwin32.GNU + </pre></code></blockquote> - In the above text, don't replace <tt>$(ACE_ROOT)</tt> with the + In the above text, don't replace <TT>$(ACE_ROOT)</TT> with the actual directory, GNU make will take the value from the environment variable you defined previously. - </li><li> On the Cygwin shell, change to the $ACE_ROOT/ace directory and + <LI> On the Cygwin shell, change to the $ACE_ROOT/ace directory and run make: - <blockquote><code></code><pre> % cd $ACE_ROOT/ace + <blockquote><code><pre> + % cd $ACE_ROOT/ace % make - </pre></blockquote> + </pre></code></blockquote> <p> - This should create <tt>libACE.dll</tt> (the Win32 shared library) and - <tt>libACE.dll.a</tt> (the Win32 import library for the DLL). + This should create <TT>libACE.dll</TT> (the Win32 shared library) and + <TT>libACE.dll</TT> (the Win32 import library for the DLL). Note the name for the ACE DLL on Cygwin follows the UNIX convention. - <br><br> + <BR><BR> - </p><p> + <p> If you want static libs also, you may run: - </p><blockquote><code></code><pre> % make static_libs=1 - </pre></blockquote> + <blockquote><code><pre> + % make static_libs=1 + </pre></code></blockquote> - </li><li> <a name="cygwinrunpath"> + <LI> <A NAME="cygwinrunpath"> The same rules for Win32 search of DLLs apply for Cygwin. If you want to run some ACE programs from the Cygwin shell, you may - need to add the directory for <tt>libACE.dll</tt> to your PATH: + need to add the directory for <TT>libACE.dll</TT> to your PATH: - </a><blockquote><code></code><pre><a name="cygwinrunpath"> # export PATH=//c/work/cygwin/ACE_wrappers/ace:$PATH - </a></pre></blockquote> + <blockquote><code><pre> + # export PATH=//c/work/cygwin/ACE_wrappers/ace:$PATH + </pre></code></blockquote> -<a name="cygwinrunpath"> If you are using MPC-generated Makefiles, then the DLLs have been + If you are using MPC-generated Makefiles, then the DLLs have been placed in the lib directory instead of ace and thus your PATH addition would need to look like this: - </a><blockquote><code></code><pre><a name="cygwinrunpath"> # export PATH=//c/work/mingw/ACE_wrappers/lib:$PATH - </a></pre></blockquote> + <blockquote><code><pre> + # export PATH=//c/work/mingw/ACE_wrappers/lib:$PATH + </pre></code></blockquote> -</li></ol> +</OL> -<a name="cygwinrunpath"><b>ACE TESTS</b></a><p> +<B>ACE TESTS</B><P> -<a name="cygwinrunpath">The tests are located in <tt>$ACE_ROOT/tests</tt>. +The tests are located in <TT>$ACE_ROOT/tests</TT>. After building the library, you can change to that directory and run make: - </a></p><blockquote><code></code><pre><a name="cygwinrunpath"> % cd $ACE_ROOT/tests + <blockquote><code><pre> + % cd $ACE_ROOT/tests % make - </a></pre></blockquote> + </pre></code></blockquote> <p> -<a name="cygwinrunpath">Once you build all the tests, you can run +Once you build all the tests, you can run <code>run_tests.pl</code> in the <code>tests</code> directory to try all the tests: - </a></p><blockquote><code></code><pre><a name="cygwinrunpath"> % perl run_test.pl - </a></pre></blockquote> + <blockquote><code><pre> + % perl run_test.pl + </pre></code></blockquote> <p> -<a name="cygwinrunpath">If you are using ACE as a DLL, you will need to modify your PATH -variable as explained </a><a href="#cygwinrunpath">above</a>. +If you are using ACE as a DLL, you will need to modify your PATH +variable as explained <A HREF="#cygwinrunpath">above</A>. -</p><p> +<p> You may want to check <tt>$ACE_ROOT/tests/README</tt> for the status of the various tests on Cygwin and the different Windows flavors. -</p><p></p><hr align="left" width="50%"><p> -</p><h4><a name="vxworks">Building and Installing ACE on VxWorks</a></h4> +<P><hr align=left width="50%"><P> +<H4><A NAME="vxworks">Building and Installing ACE on VxWorks</A></H4> For the most part, you should be able to follow the instructions above to build ACE and applications that use it. Start with the <a href="#unix">Unix instructions</a> above to build ACE and the applications that use it. Please see below for more information on -<a href="#VxWorks/NT">building ACE on NT hosts for VxWorks targets</a>.<p> +<a href="#VxWorks/NT">building ACE on NT hosts for VxWorks targets</a>.<P> A few notes on VxWorks builds (thanks to <a href="mailto:Paul_von_Behren@stortek.com">Paul von Behren</a> -for these notes):</p><p> -</p><ul> - <li>VxWorks builds are done with a cross compiler, i.e., the compiles +for these notes):<p> +<UL> + <LI>VxWorks builds are done with a cross compiler, i.e., the compiles are done on a workstation creating object modules which are downloaded and loaded into the VxWorks target system.<p> - </p></li><li>C++ object modules must be post-processed by a VxWorks - utility called "munch." ACE includes a perl script called - <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/bin/ace_ld">$ACE_ROOT/bin/ace_ld</a>, + <LI>C++ object modules must be post-processed by a VxWorks + utility called "munch." ACE includes a perl script called + <A + HREF="bin/ace_ld">$ACE_ROOT/bin/ace_ld</A>, which is called from the Makefiles, replacing the traditional <code>ld</code> step. You must have perl installed to use <code>ace_ld</code>. If perl is not on your path, you'll have to set <code>PERL_PATH</code> to the full path (including perl.exe), either in your <code>$(ACE_ROOT)/include/makeinclude/platform_macros.GNU</code> - or in your environment.<p> - </p></li><li>Wind River provides GCC/G++ cross-compilers for the + or in your environment.<P> + <LI>Wind River provides GCC/G++ cross-compilers for the supported target platforms. The executables are named cc<target> and g++<target>; for example, ccppc and g++cpp for PowerPC targets.<p> -</p></li></ul> +</UL> You'll have to let ACE know the target type at compile time. There are several ways to do this; please see the <code>$ACE_ROOT/include/makeinclude/platform_vxworks5.x_g++.GNU</code> -platform file for detailed information.<p> +platform file for detailed information.<P> The VxWorks platform_vxworks*.GNU files are set up so that shared libraries are not built on VxWorks, by default. Only static @@ -1789,16 +1868,17 @@ necessary to set the LD_LIBRARY_PATH environment variable on your host system when building for VxWorks targets. Please note, however, if you use TAO on VxWorks that you will need to set your LD_LIBRARY_PATH to find the TAO IDL compiler libraries (installed in the ace -directory) on the host.</p><p> +directory) on the host.<P> With g++, $ACE_ROOT/bin/ace_ld is used to munch object files and libraries to set up calls to static constructors and destructors. -bin/ace_ld requires perl on the host platform.</p><p> +bin/ace_ld requires perl on the host platform.<P> These non-default VxWorks kernel configuration <code>#defines</code> -are required with ACE:</p><p> +are required with ACE:<P> -</p><pre>#define INCLUDE_CPLUS /* include C++ support */ +<pre> +#define INCLUDE_CPLUS /* include C++ support */ #define INCLUDE_CPLUS_IOSTREAMS /* include iostreams classes */ #define INCLUDE_POSIX_ALL /* include all available POSIX functions */ </pre> @@ -1806,7 +1886,8 @@ are required with ACE:</p><p> For completeness, here are the non-default <code>#defines</code> that we used for VxWorks 5.3.1/g++ 2.7.2: -<pre>#define INCLUDE_CPLUS /* include C++ support */ +<pre> +#define INCLUDE_CPLUS /* include C++ support */ #define INCLUDE_CPLUS_IOSTREAMS /* include iostreams classes */ #define INCLUDE_CONFIGURATION_5_2 /* pre-tornado tools */ #define INCLUDE_DEBUG /* pre-tornado debugging */ @@ -1835,58 +1916,58 @@ should be enabled.<p> If you use TAO, it's also a good idea to increase the <code>NUM_FILES</code> parameter from its default of 50 to, -say, 1000.</p><p> +say, 1000.<p> Please note that those VxWorks kernel configuration parameters are set in the VxWorks configAll.h file. You must rebuild your -VxWorks kernel after modifying that file.</p><p> +VxWorks kernel after modifying that file.<p> If you're first getting started with ACE and/or VxWorks, I recommend just building the ACE library and tests first. (Some of the ACE examples, in System_V_IPC, don't build on VxWorks yet.) Then try running the tests. Please see $ACE_ROOT/tests/README for the latest -status of the ACE tests on VxWorks.</p><p> +status of the ACE tests on VxWorks.<P> Please note that the <code>main</code> entry point is renamed to <code>ace_main</code> (configurable via ACE_MAIN) on VxWorks with g++, to comply with its restriction against using <code>main</code>. In addition, ACE_HAS_NONSTATIC_OBJECT_MANAGER is enabled by default to cleanly support construction and destruction of static objects. -Please see the <a href="#Non-static%20Object%20Manager">Non-static -ACE_Object_Manager</a> discussion for the important implication -of this feature.</p><p> +Please see the <A HREF="#Non-static Object Manager">Non-static +ACE_Object_Manager</A> discussion for the important implication +of this feature.<p> ACE threads (VxWorks tasks) can be named, for example, by supplying a non-null argument to the Thread_Manager spawn routines. However, names beginning with <code>"==ace_t=="</code> are forbidden because -that prefix is used internally by ACE.</p><p> +that prefix is used internally by ACE.<p> You can spawn a new task to run <code>ace_main</code>, using either -VxWorks <code>sp</code>, or ACE'S <a name="spa"><code>spa</code></a>. +VxWorks <code>sp</code>, or ACE'S <A NAME="spa"><code>spa</code></A>. <code>spa</code> can be used from the VxWorks shell to pass arguments to <code>ace_main</code>. Its usage is: -</p><pre><code> +<pre><code> spa ace_main, "arg1" [, ...] </code></pre> All arguments must be quoted, even numbers.<p> -The ACE <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/tests/">tests</a> write their output files in a +The ACE <a href="tests/">tests</a> write their output files in a directory named <code>log/</code>, below the current (<code>tests</code>) directory. If you don't have NFS included in your VxWorks kernel, you can use these steps, provided by <a href="mailto:clarence_m_weaver@md.northgrum.com">Clarence M. Weaver</a>, -to run the tests and capture their output:</p><p> -</p><ol> +to run the tests and capture their output:<p> +<ol> <li>What I did was create a log directory on the boot NT host of my vxworks target.<p> - </p></li><li>I copied all the test applications and the run_tests.vxworks script to + <li>I copied all the test applications and the run_tests.vxworks script to the parent of the log directory.<p> - </p></li><li>Using the target shell not the host shell, I "cd" to the directory + <li>Using the target shell not the host shell, I "cd" to the directory containing the script and test programs.<p> - </p></li><li>Invoked the script < run_tests.vxworks from this target shell.<p> -</p></li></ol> + <li>Invoked the script < run_tests.vxworks from this target shell.<p> +</ol> <a href="mailto:Kirk.Davies@pobox.com">Kirk Davies</a> provided this approach for running the ACE tests on Tornado II: @@ -1894,10 +1975,11 @@ approach for running the ACE tests on Tornado II: <ul> <li>Under Tornado II, I set up the Target Server File System (TSFS), and the test logs get written to the log subdirectory under that.<p> - </p></li><li>You have to set an environment variable before running the tests: -<pre>putenv("ACE_TEST_DIR=/tgtsvr") + <li>You have to set an environment variable before running the tests: +<pre> +putenv("ACE_TEST_DIR=/tgtsvr") </pre><p> -</p></li></ul> +</ul> <h5><a name="VxWorks/SharedLibs">Building Shared Libraries for VxWorks</a>.</h5> @@ -1913,12 +1995,12 @@ A shared library for VxWorks uses the same code as for a static (non-shared) library. However, calls to static constructors/ destructors are added. The code in the shared library <strong>must</strong> be reentrant if you shared it between programs (tasks). The -ACE library meets this requirement.</p><p> +ACE library meets this requirement.<p> Shared libraries reduce build time, executable size, and load time of the executable. But, you must manually load the shared library before loading your executable(s) with a command such as: -</p><pre><code> +<pre><code> -> ld < libACE.so </code></pre> Shared libraries can be unloaded the same way an executable @@ -1930,14 +2012,15 @@ no support for creating copies of writeable global (static) data in the shared library. This includes the singleton ACE_Object_Manager instance pointer. If you share global data between separate programs, they may not work properly. See the discussion of shared code and -reentrancy in the VxWorks' <em>Programmers Guide</em>.</p><p> +reentrancy in the VxWorks' <em>Programmers Guide</em>.<p> Instead of trying to run separate programs onto a VxWorks target, we recommend creating just one program, and spawning a thread for each -task. The TAO IDL_Cubit test <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/TAO/performance-tests/Cubit/TAO/IDL_Cubit/collocation_test.cpp">collocation -test</a> is a good example.</p><p> +task. The TAO IDL_Cubit test <a +href="TAO/performance-tests/Cubit/TAO/IDL_Cubit/collocation_test.cpp">collocation +test</a> is a good example.<p> -</p><h5><a name="VxWorks/LinkToKernel">Linking ACE and/or TAO Libraries into the VxWorks Kernel</a>.</h5> +<h5><a name="VxWorks/LinkToKernel">Linking ACE and/or TAO Libraries into the VxWorks Kernel</a>.</h5> It's easy to link your ACE and/or TAO libraries into the VxWorks kernel. Just build <a href="#VxWorks/SharedLibs">shared versions</a>, but @@ -1945,14 +2028,15 @@ disable the munch step. The easiest way to do that is to set the <code>LD</code> make variable to the name of your linker. For example, to build a libACE.so for PowerPC that can be linked into the kernel: -<pre>% cd $ACE_ROOT/ace +<pre> +% cd $ACE_ROOT/ace % make LD=ldppc shared_libs=1 </pre> After building the shared lib, link it into the kernel by setting the <code>MACH_EXTRA</code> make variable in the kernel configuration Makefile. Then, build the kernel using <code>make exe</code>.<p> -</p><h5><a name="VxWorks/NT">Building ACE on Tornado/NT hosts for VxWorks targets</a>.</h5> +<h5><a name="VxWorks/NT">Building ACE on Tornado/NT hosts for VxWorks targets</a>.</h5> The following, very useful information was contributed by <a href="http://people.qualcomm.com/cryan">Chris Ryan</a> and <a href="mailto:Paul_von_Behren@stortek.com">Paul von Behren</a>. @@ -1961,69 +2045,71 @@ the <a href="mailto:ace-users@cs.wustl.edu">ACE mailing list</a>.<p> <strong>NOTE:</strong>The make (version 3.74) that is provided with Tornado II cannot be used to build ACE. Use Cygnus' make (version 3.75) -instead.)</p><p> +instead.)<p> <strong>NOTE:</strong>Optimization is enabled be default in -<a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/include/makeinclude/platform_vxworks5.x_g++.GNU">platform_vxworks5.x_g++.GNU</a>. However, the compiler that is shipped with Tornado II has +<a href=include/makeinclude/platform_vxworks5.x_g++.GNU>platform_vxworks5.x_g++.GNU</a>. However, the compiler that is shipped with Tornado II has trouble compiling some files with -O2. To disable optimization for an individual file, just add <code>optimize=0</code> to your -make invocation when compiling that file.</p><p> +make invocation when compiling that file.<p> Using the Cygnus tools, this approach works: -</p><ul> +<ul> <li>You'll build both your NT and VxWorks executables in the same workspace (directory hierarchy). This works because the NT compiler and ACE's Makefiles put their output in different directories.<p> - </p></li><li>Set up your + <li>Set up your <code>ACE_wrappers/include/makeinclude/platform_macros.GNU</code> as usual for VxWorks. See - <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/include/makeinclude/platform_vxworks5.x_g++.GNU">the + <a href="include/makeinclude/platform_vxworks5.x_g++.GNU">the g++/VxWorks platform file</a> for more information.<p> - </p></li><li>Create an <code>ACE_wrappers/ace/config.h</code> file that looks + <li>Create an <code>ACE_wrappers/ace/config.h</code> file that looks something like the following. tao_idl should be built to not support native exception handling, because that's not available on VxWorks. -<pre>#if defined (_MSC_VER) || defined (__BORLANDC__) +<pre> +#if defined (_MSC_VER) || defined (__BORLANDC__) # include "ace/config-win32.h" # undef ACE_HAS_EXCEPTIONS #else # include "ace/config-vxworks.h" #endif </pre><p> - </p></li><li>Set your <code>ACE_ROOT</code>, <code>CPP_LOCATION</code>, + <li>Set your <code>ACE_ROOT</code>, <code>CPP_LOCATION</code>, <code>WIND_BASE</code>, and <code>WIND_HOST_TYPE</code> environment variables.<p> - </p></li><li>Build for NT, then build for VxWorks.<p> -</p></li></ul> + <li>Build for NT, then build for VxWorks.<p> +</ul> A few additional Windows Notes, from Paul von Behren:<p> -</p><ul> +<ul> <li>Cygnus has created a Win32 API which is compatible with a - "generic" Unix environment. Using this library, they have ported a + "generic" Unix environment. Using this library, they have ported a large collection of GNU tools to WinNT/95 - including a port of - gcc/g++. See <a href="http://www.cygnus.com/misc/gnu-win32/">http://www.cygnus.com/misc/gnu-win32/</a> + gcc/g++. See <A href="http://www.cygnus.com/misc/gnu-win32/">http://www.cygnus.com/misc/gnu-win32/</A> A related link is <a href="ftp://ftp.cygnus.com/pub/gnu-win32/latest/">ftp://ftp.cygnus.com/pub/gnu-win32/latest/</a><p> - </p></li><li>To set up the command-prompt build environemnt, run + <li>To set up the command-prompt build environemnt, run <code>Tornado\host\x86-win32\bin\TorVars.bat</code>. This is done implicitly within the Tornado IDE.<p> - </p></li><li>To run <code>ace_ld</code>, you still need perl installed - - see <a href="http://www.activestate.com/software/default.htm">http://www.activestate.com/software/default.htm</a> + <li>To run <code>ace_ld</code>, you still need perl installed - + see <A href="http://www.activestate.com/software/default.htm">http://www.activestate.com/software/default.htm</A> for Windows perl.<p> - </p></li><li>The Tornado IDE will use a standard Makefile for project + <li>The Tornado IDE will use a standard Makefile for project builds, but does not have a GUI interface for managing the Makefile. By default, it will use rules from Makefile in the current directory and you can configure it to add certain Makefile targets to the project. If you have <code>ACE_ROOT</code> defined before starting Tornado, you can specify an ACE Makefile as a Tornado target and Tornado will then call make from the menu.<p> -</p></li></ul> +</ul> And Chris Ryan's instructions for building for VxWorks targets on Windows NT hosts: <ol> <li>Path setting that seems to be working is:<p> - </p><pre> /tornado/host/x86-win32/bin: + <pre> + /tornado/host/x86-win32/bin: /tornado/host/x86-win32/lib/gcc-lib/i386-wrs-vxworks/cygnus-2.7.2-960126: /tornado/host/x86-win32/i386-wrs-vxworks/bin: /ace/ace_wrappers/bin: @@ -2036,7 +2122,8 @@ on Windows NT hosts: </pre> Other environment variables:<p> - </p><pre> WIND_BASE=/tornado + <pre> + WIND_BASE=/tornado SHELL=/bin/sh.exe TERM=pcbios TAO_ROOT=/ace/ACE_wrappers.vxworks/TAO @@ -2046,13 +2133,14 @@ on Windows NT hosts: ACE_ROOT=/ace/ACE_wrappers.vxworks </pre> - </li><li><code>/tornado</code> is the root of the Tornado install + <li><code>/tornado</code> is the root of the Tornado install (<code>$WIND_BASE</code>). - </li><li><code>/gnuwin32</code> is the root of a Cygnus GNU download and install. + <li><code>/gnuwin32</code> is the root of a Cygnus GNU download and install. - </li><li><code>/bin</code> content is:<p> - </p><pre> aced.dll + <li><code>/bin</code> content is:<p> + <pre> + aced.dll cygwin.dll perl.exe rm.exe @@ -2065,27 +2153,30 @@ on Windows NT hosts: <code>cygwin.dll</code> is from the Cygnus GNU software download and install. - </li><li>Basically, follow documented procedure for ACE build/install on UNIX + <li>Basically, follow documented procedure for ACE build/install on UNIX platform. Create a <code>$ACE_ROOT/ace/config.h</code> that looks like:<p> - </p><pre> #include "config-vxworks5.x.h" + <pre> + #include "config-vxworks5.x.h" </pre> And create a <code>$ACE_ROOT/include/makeinclude/platform_macros.GNU</code> that looks like:<p> - </p><pre> WIND_BASE = /tornado + <pre> + WIND_BASE = /tornado WIND_HOST_TYPE = x86-win32 CPU = I80486 include $(ACE_ROOT)/include/makeinclude/platform_vxworks5.x_g++.GNU </pre> - </li><li>When using cygnus windows GNUTools on WinNT you have to start + <LI>When using cygnus windows GNUTools on WinNT you have to start make with "--unix" option, otherwise WinNT shell cmd.exe is responded and not sh.exe, i.e., - <pre> make --unix static_libs=1 - </pre> -</li></ol> + <PRE> + make --unix static_libs=1 + </PRE> +</ol> <h5>TAO on NT Tornado host, VxWorks target.</h5> @@ -2095,212 +2186,221 @@ on Windows NT hosts: Be sure to build ACE's gperf on NT, in <code>ACE_wrappers/apps/gperf/src</code>.<p> - </p></li><li>Build $TAO_ROOT/tao - <pre> CPP_LOCATION=/Program Files/DevStudio/VC/bin/CL.exe + <li>Build $TAO_ROOT/tao + <pre> + CPP_LOCATION=/Program Files/DevStudio/VC/bin/CL.exe cd $TAO_ROOT/tao /gnuwin32/b18/H-i386-cygwin32/bin/make </pre> - </li><li>Build orbsvcs. - <pre> CPP_LOCATION=/Program Files/DevStudio/VC/bin/CL.exe + <li>Build orbsvcs. + <pre> + CPP_LOCATION=/Program Files/DevStudio/VC/bin/CL.exe cd $TAO_ROOT/orbsvcs/orbsvcs /gnuwin32/b18/H-i386-cygwin32/bin/make </pre> - </li><li>Build $TAO_ROOT/tests<p> -</p></li></ol> + <li>Build $TAO_ROOT/tests<p> +</ol> -<h4><a name="vxworks"> </a> +<H4><A NAME="vxworks"> </a> <a href="mailto:Jaffar_Shaikh@Mitel.COM">Jaffar Shaikh's</a> -Notes for Building ACE and TAO for VxWorks on NT host</h4> -<b></b><p><b>Scenario:</b> I was building the ACE and TAO for VxWorks +Notes for Building ACE and TAO for VxWorks on NT host</H4> +<B><P>Scenario:</B> I was building the ACE and TAO for VxWorks on NT. The target system was a PPC860 based chassis and another a NT -host based card.</p> -<b><p>Host System:</p> -</b><p>NT 4.0 workstation with 128 M RAM, 266MHz Pentium.</p> +host based card.</P> +<B><P>Host System:</P> +</B><P>NT 4.0 workstation with 128 M RAM, 266MHz Pentium.</P> -<b><p>Software Needed For Building TAO</p> -</b><p>1) PERL: Active State's ActivePerl 5.6.0.618 for NT available as +<B><P>Software Needed For Building TAO</P> +</B><P>1) PERL: Active State's ActivePerl 5.6.0.618 for NT available as freeware from http://www.ActiveState.com/download/contrib/Microsoft/NT/InstMsi.exe -</p> - -<p>2) Tornado II .Release V 9904 from Windriver.</p> - -<p>3) Cygwin GNU to build TAO. It is available for NT as a freeware -from </p> -<p>http://www.cygwin.com/</p> -<p>The Cygwin Make (version 3.75) can only build the TAO not the -Tornado II make (version 3.74)</p> - -<b><p>Environment Variables:</p> -</b><p>On NT the environment Variables are set as follows, (from -Control Panel-> System -> Environment)</p> -<p>I added following Environment variable entries to PATH </p> - -<p>C:\Perl\bin\;</p> -<p>C:\tornado\host\x86-win32\bin;</p> -<p>C:\tornado\host\x86-win32\powerpc-wrs-vxworks\bin;</p> -<p>C:\tornado\host\x86-win32\lib\gcc-lib\powerpc-wrs-vxworks\cygnus-2.7.2-960126;</p> -<p>C:\Corba\Ace_wrappers\bin;</p> -<p>C:\Cygwin\bin;</p> -<p>C:\Cygwin\usr\bin;</p> -<p>C:\bin</p> - -<p>Additional Environmental variables and the values,</p> -<p>CPU=PPC860</p> -<p>LD_LIBRARY_PATH=</p> -<p>SHELL=/bin/sh.exe</p> - -<p>ACE_ROOT=/Corba/ACE_wrappers</p> -<p>WIND_BASE=/tornado</p> -<p>SHELL=/bin/sh.exe</p> -<p>TERM=pcbios</p> -<p>TAO_ROOT=/Corba/ACE_wrapper/Tao</p> -<p>CPP_LOCATION=/Program Files/Microsoft Visual Studio/VC98/Bin/CL.exe</p> -<p>GCC_EXEC_PREFIX=/tornado/host/x86-win32/lib/gcc-lib/</p> -<p>WIND_HOST_TYPE=x86-win32</p> -<p>PERL_PATH=/perl/bin/perl.exe</p> - -<b><p>Directories of importance</p> -</b><p>C:\Corba <-- Ace_wrappers (uzipped)</p> -<p>C:\tornado <-- Tornado installed</p> -<p>C:\Perl <-- Perl installed</p> -<p>C:\Cygwin <-- Cygwin installed</p> -<p>C:\bin <-- Copy these files,</p> -<p> Ace.dll, <-- After you build Ace</p> -<p> gperf.exe <-- After you build gperf</p> -<p> Cygwin1.dll, <-- After you install Cygwin</p> -<p> perl.exe, <-- After you install Perl</p> -<p> rm.exe <-- After you install Cygwin</p> -<p> sh.exe <-- After you install Cygwin</p> -<p> true <-- After you install Cygwin</p> -<b><p>Create Files</p> -</b><p>1) C:\Corba\ACE_Wrappers\ace\config.h</p> -<p>with entry</p> -<p>#if defined (_MSC_VER) || (__BORLANDC__)</p> -<p> #include "ace/config-win32.h"</p> -<p> #undef ACE_HAS_EXCEPTIONS</p> -<p>#else</p> -<p> #include "ace/config-vxworks5.x.h"</p> -<p> #define ACE_HAS_IP_MULTICAST </p> -<p>#endif</p> - -<p>2) C:\Corba\ACE_wrappers\include\makeinclude\platform_macros.GNU</p> -<p>WIND_BASE = /tornado</p> -<p>WIND_HOST_TYPE = x86-win32</p> -<p>include -$(ACE_ROOT)/include/makeinclude/platform_vxworks5.x_g++.GNU</p> -<p>ACE_COMPONENTS=FOR_TAO (you may choose this option to build ACE -library that supports TAO)</p> - -<p> </p> -<b><p>Steps to Build</p> -</b><p>1) Build Ace.dll under NT</p> -<p>In MS Visual C++ open C:\Corba\ACE_wrappers\ace.dsw And build Ace -DLL</p> -<p>Copy Ace.dll in C:\bin</p> - -<p>2) Build gperf utility under NT</p> -<p>In MS Visual C++ open -C:\Corba\ACE_wrappers\apps\gperf\src\gperf.dsw. Build gperf.exe</p> -<p>Copy gperf.exe to C:\bin</p> - -<p>3) Mount Directries in Cygwin</p> -<p>Click on Cygnus Solutions -> Cygwin Bash Shell</p> -<p>Mount following directories by using mount command.</p> -<p>create respective directories first then use mount command </p> - -<p>e.g. Create /Corba directory then use $mount -s "C:\Corba" -/Corba</p> - -<p>C:\Corba mount to /Corba</p> -<p>C:\tornado mount to /tornado</p> -<p>C:\Perl mount to /perl</p> -<p>C:\Cygwin mount to /cygwin</p> -<p>C:\bin mount to /bin</p> -<p>C:\Program Files mount to /Program Files </p> - -<p>4) Build ACE in Cygwin</p> -<p>$cd /Corba/ACE_wrappers/ace </p> -<p>$make static_libs=1</p> -<p>This will build your ace library libACE.a for VxWorks. If you use +</P> + +<P>2) Tornado II .Release V 9904 from Windriver.</P> + +<P>3) Cygwin GNU to build TAO. It is available for NT as a freeware +from </P> +<P>http://www.cygwin.com/</P> +<P>The Cygwin Make (version 3.75) can only build the TAO not the +Tornado II make (version 3.74)</P> + +<B><P>Environment Variables:</P> +</B><P>On NT the environment Variables are set as follows, (from +Control Panel-> System -> Environment)</P> +<P>I added following Environment variable entries to PATH </P> + +<P>C:\Perl\bin\;</P> +<P>C:\tornado\host\x86-win32\bin;</P> +<P>C:\tornado\host\x86-win32\powerpc-wrs-vxworks\bin;</P> +<P>C:\tornado\host\x86-win32\lib\gcc-lib\powerpc-wrs-vxworks\cygnus-2.7.2-960126;</P> +<P>C:\Corba\Ace_wrappers\bin;</P> +<P>C:\Cygwin\bin;</P> +<P>C:\Cygwin\usr\bin;</P> +<P>C:\bin</P> + +<P>Additional Environmental variables and the values,</P> +<P>CPU=PPC860</P> +<P>LD_LIBRARY_PATH=</P> +<P>SHELL=/bin/sh.exe</P> + +<P>ACE_ROOT=/Corba/ACE_wrappers</P> +<P>WIND_BASE=/tornado</P> +<P>SHELL=/bin/sh.exe</P> +<P>TERM=pcbios</P> +<P>TAO_ROOT=/Corba/ACE_wrapper/Tao</P> +<P>CPP_LOCATION=/Program Files/Microsoft Visual Studio/VC98/Bin/CL.exe</P> +<P>GCC_EXEC_PREFIX=/tornado/host/x86-win32/lib/gcc-lib/</P> +<P>WIND_HOST_TYPE=x86-win32</P> +<P>PERL_PATH=/perl/bin/perl.exe</P> + +<B><P>Directories of importance</P> +</B><P>C:\Corba 	<-- Ace_wrappers (uzipped)</P> +<P>C:\tornado 	<-- Tornado installed</P> +<P>C:\Perl 	<-- Perl installed</P> +<P>C:\Cygwin 	<-- Cygwin installed</P> +<P>C:\bin <-- Copy these files,</P> +<P>		 Ace.dll, 	<-- After you build Ace</P> +<P>		gperf.exe 	<-- After you build gperf</P> +<P>		Cygwin1.dll, 	<-- After you install Cygwin</P> +<P>		perl.exe, 	<-- After you install Perl</P> +<P>		rm.exe		<-- After you install Cygwin</P> +<P>		sh.exe		<-- After you install Cygwin</P> +<P>		true		<-- After you install Cygwin</P> +<B><P>Create Files</P> +</B><P>1) C:\Corba\ACE_Wrappers\ace\config.h</P> +<P>with entry</P> +<P>#if defined (_MSC_VER) || (__BORLANDC__)</P> +<P>	#include "ace/config-win32.h"</P> +<P>	#undef ACE_HAS_EXCEPTIONS</P> +<P>#else</P> +<P>	#include "ace/config-vxworks5.x.h"</P> +<P>	#define ACE_HAS_IP_MULTICAST </P> +<P>#endif</P> + +<P>2) C:\Corba\ACE_wrappers\include\makeinclude\platform_macros.GNU</P> +<P>WIND_BASE = /tornado</P> +<P>WIND_HOST_TYPE = x86-win32</P> +<P>include +$(ACE_ROOT)/include/makeinclude/platform_vxworks5.x_g++.GNU</P> +<P>ACE_COMPONENTS=FOR_TAO (you may choose this option to build ACE +library that supports TAO)</P> + +<P> </P> +<B><P>Steps to Build</P> +</B><P>1) Build Ace.dll under NT</P> +<P>In MS Visual C++ open C:\Corba\ACE_wrappers\ace.dsw And build Ace +DLL</P> +<P>Copy Ace.dll in C:\bin</P> + +<P>2) Build gperf utility under NT</P> +<P>In MS Visual C++ open +C:\Corba\ACE_wrappers\apps\gperf\src\gperf.dsw. Build gperf.exe</P> +<P>Copy gperf.exe to C:\bin</P> + +<P>3) Mount Directries in Cygwin</P> +<P>Click on Cygnus Solutions -> Cygwin Bash Shell</P> +<P>Mount following directories by using mount command.</P> +<P>create respective directories first then use mount command </P> + +<P>e.g. Create /Corba directory then use $mount -s "C:\Corba" +/Corba</P> + +<P>C:\Corba mount to /Corba</P> +<P>C:\tornado mount to /tornado</P> +<P>C:\Perl mount to /perl</P> +<P>C:\Cygwin mount to /cygwin</P> +<P>C:\bin mount to /bin</P> +<P>C:\Program Files mount to /Program Files </P> + +<P>4) Build ACE in Cygwin</P> +<P>$cd /Corba/ACE_wrappers/ace </P> +<P>$make static_libs=1</P> +<P>This will build your ace library libACE.a for VxWorks. If you use option shared_libs=1 then the build will be libACE.so. The other -options are same as follows.</p> - -<p>5) Build TAO in Cygwin</p> -<p>$cd $TAO_ROOT/tao</p> -<p>$make debug=0 optimize=1 static_libs_only=1 minimum_orb=1 -</p> -<p>for shared libs use shared_libs=1</p> - -<p>The minimum Tao does not have following components,</p> -<p>Dynamic Skeleton Interface</p> -<p>Dynamic Invocation Interface</p> -<p>Dynamic Any</p> -<p>Interceptors</p> -<p>Interface Repository</p> -<p>Advanced POA features</p> -<p>CORBA/COM interworking</p> - -<p>You may play around with above options to find suitable build for +options are same as follows.</P> + +<P>5) Build TAO in Cygwin</P> +<P>$cd $TAO_ROOT/tao</P> +<P>$make debug=0 optimize=1 static_libs_only=1 minimum_orb=1 +</P> +<P>for shared libs use shared_libs=1</P> + +<P>The minimum Tao does not have following components,</P> +<P>Dynamic Skeleton Interface</P> +<P>Dynamic Invocation Interface</P> +<P>Dynamic Any</P> +<P>Interceptors</P> +<P>Interface Repository</P> +<P>Advanced POA features</P> +<P>CORBA/COM interworking</P> + +<P>You may play around with above options to find suitable build for your needs. For example when you give option debug=1 all the debug symbols will be created and the build will huge in size. The debug -symbols are necessary when you want to debug your code.</p> +symbols are necessary when you want to debug your code.</P> -<hr> -<h3><a name="svcsinstall">Building and Installing ACE Network Services</a></h3> +<HR> +<H3><A NAME="svcsinstall">Building and Installing ACE Network Services</A></H3> -The following explains how to build the ACE <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE-netsvcs.html">network services</a> on <a href="#unixsvcs">UNIX</a> and <a href="#win32svcs">Win32</a>. +The following explains how to build the ACE <A +HREF="http://www.cs.wustl.edu/~schmidt/ACE-netsvcs.html">network services</A> on <A +HREF="#unixsvcs">UNIX</A> and <A HREF="#win32svcs">Win32</A>. -<p></p><hr align="left" width="50%"><p> -</p><h4><a name="unixsvcs">Building and Installing ACE Network Services on UNIX</a></h4> +<P><hr align=left width="50%"><P> +<H4><A NAME="unixsvcs">Building and Installing ACE Network Services on UNIX</A></H4> Building and installing ACE Network Services on UNIX is relatively -simple (the <a href="#win32svcs">process</a> for Win32 is different). -Here's what you need to do:<p> +simple (the <A HREF="#win32svcs">process</A> for Win32 is different). +Here's what you need to do:<P> -</p><ol> +<OL> - <li>Build and install ACE on UNIX as described <a href="#unix">earlier</a>. If ACE is built at the root of the ACE + <LI>Build and install ACE on UNIX as described <A + HREF="#unix">earlier</A>. If ACE is built at the root of the ACE source tree (and ACE has been ported to your platform, of course) the netsvcs static and shared object libraries should be built automatically. In addition, the server driver program - (<code>main</code>) contained in <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/netsvcs/servers/main.cpp">$ACE_ROOT/netsvcs/servers/main.cpp</a> - should also be compiled and ready to run.<p> + (<CODE>main</CODE>) contained in <A + HREF="netsvcs/servers/main.cpp">$ACE_ROOT/netsvcs/servers/main.cpp</A> + should also be compiled and ready to run.<P> - </p></li><li>Set your <code>LD_LIBRARY_PATH</code> environment variable to + <LI>Set your <CODE>LD_LIBRARY_PATH</CODE> environment variable to where the binary version of the ACE netsvcs library. For - example, you probably want to do something like the following<p> + example, you probably want to do something like the following<P> - </p><pre><code> + <pre><code> % setenv LD_LIBRARY_PATH $ACE_ROOT/ace:$ACE_ROOT/lib:$LD_LIBRARY_PATH - </code></pre><p> + </code></pre><P> - </p></li><li>By default, if the shared object library is built, the services - are linked into the <code>main</code> driver program dynamically. + <LI>By default, if the shared object library is built, the services + are linked into the <CODE>main</CODE> driver program dynamically. To specify which services should be linked in and executed, edit the - <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/netsvcs/servers/svc.conf">$ACE_ROOT/netsvcs/servers/svc.conf</a> + <A + HREF="netsvcs/servers/svc.conf">$ACE_ROOT/netsvcs/servers/svc.conf</A> file. During your editing, you should update information (such as the default service port numbers) that affects the initialization of services in this file. Refer to the - <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/ACE-papers.html#config">Service Configurator</a> + <A HREF="ACE-papers.html#config">Service Configurator</A> documentation to learn how the configuration file is parsed and how the services are dynamically linked and executed. In - addition, refer to the <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE-netsvcs.html">Network - Services</a> documentation to learn more about how to configure - each network service.<p> + addition, refer to the <A + HREF="http://www.cs.wustl.edu/~schmidt/ACE-netsvcs.html">Network + Services</A> documentation to learn more about how to configure + each network service.<P> - </p></li><li>If you only want to link the services statically, simply remove - or rename the svc.conf file.<p> -</p></li></ol> + <LI>If you only want to link the services statically, simply remove + or rename the svc.conf file.<P> +</OL> -<p></p><hr align="left" width="50%"><p> -</p><h4><a name="rtems">Building and Installing ACE on RTEMS</a></h4> +<P><hr align=left width="50%"><P> +<H4><A NAME="rtems">Building and Installing ACE on RTEMS</A></H4> -<pre>export RTEMS_MAKEFILE_PATH=/opt/rtems/CPU-rtems/BSP +<PRE> +export RTEMS_MAKEFILE_PATH=/opt/rtems/CPU-rtems/BSP # setup the build structure cd ACE_wrappers @@ -2347,85 +2447,92 @@ make -f ../include/makeinclude/Makefile.rtems rtems_init.o make cd ../TAO make -</pre> +</PRE> -<p></p><hr align="left" width="50%"><p> -</p><h4><a name="win32svcs">Building and Installing ACE Network Services on Win32</a></h4> +<P><hr align=left width="50%"><P> +<H4><A NAME="win32svcs">Building and Installing ACE Network Services on Win32</A></H4> Once again, there are supplied project for MSVC 6.0 or later for -the Network Services.<p> +the Network Services.<P> -</p><hr> -<h3><a name="sslinstall">Building and Installing The ACE_SSL Library</a></h3> +<HR> +<H3><A NAME="sslinstall">Building and Installing The ACE_SSL Library</A></H3> <p>The first step for all platforms is to build and install the -<a href="http://www.openssl.org/">OpenSSL</a> distribution. The -ACE_SSL library must then be built according to the instructions +<A HREF="http://www.openssl.org/">OpenSSL</A> distribution. Then the +ACE_SSL library must be built according to the instructions below.</p> <h3>Unix</h3> -<ol> - <li>Make sure the OpenSSL header file directory is in your compiler's +<OL> + <LI>Make sure the OpenSSL header file directory is in your compiler's include path, and that OpenSSL libraries are in your library link/load path (e.g. <font face="Courier New, Courier, mono">LD_LIBRARY_PATH</font>). If you installed OpenSSL into a set of directories unknown by the compiler, - set the <code>SSL_ROOT</code> environment variable to point to the - top level directory of your OpenSSL distribution, i.e. the one - containing OpenSSL's <code>include</code> and <code>lib</code> - directories.</li> - <li>Add <code>ssl=1</code> to your MPC - <code>$ACE_ROOT/bin/MakeProjectCreator/config/default.features</code> - or <code>$ACE_ROOT/local.features</code> file, and re-run MPC to add - support for building the ACE_SSL library to your GNUmakefiles. - <li>Build ACE as described above. When building ACE, add - "<font face="Courier New, Courier, mono">ssl=1</font>" + then set the following variables in your + <font face="Courier New, Courier, mono">platform_macros.GNU</font> + file: + <P><table width="75%" border="0" align="center"> + <tr> + <td><font face="Courier New, Courier, mono">PLATFORM_SSL_CPPFLAGS</font></td> + <td>Platform preprocessor options for OpenSSL (e.g. -I...)</td> + </tr> + <tr> + <td><font face="Courier New, Courier, mono">PLATFORM_SSL_LDFLAGS</font></td> + <td>Platform linker options for OpenSSL (e.g. -L...)</td> + </tr> + <tr> + <td><font face="Courier New, Courier, mono">PLATFORM_SSL_LIBS</font></td> + <td>Platform libraries required with OpenSSL (e.g. -lssl -lcrypto)</td> + </tr> + </table> + <br> + </LI> + <LI>Build ACE as described above. When building ACE, add + "<font face="Courier New, Courier, mono">ssl=1</font>" to your <font face="Courier New, Courier, mono">make</font> command line invocation, or add it to your <font face="Courier New, Courier, mono">platform_macros.GNU</font> - file.</li> - <li>Build the ACE_SSL library in the <tt>$ACE_ROOT/ace/SSL</tt> - directory. The <tt>ACE_ROOT</tt> environment variable should be set + file.</LI> + <li>Build the ACE_SSL library in the <TT>$ACE_ROOT/ace/SSL</TT> + directory. The <TT>ACE_ROOT</TT> environment variable should be set prior to this point.</li> -</ol> +</OL> <h3>Microsoft Visual Studio</h3> <ol> - <li>Set the <code>SSL_ROOT</code> environment variable to the location - of the directory containing the OpenSSL <code>inc32</code> and - <code>out32dll</code> directories. - <li>Add <code>ssl=1</code> to your MPC - <code>$ACE_ROOT/bin/MakeProjectCreator/config/default.features</code> - or <code>$ACE_ROOT/local.features</code> file, and re-run MPC to add - support for building the ACE_SSL library to your MSVC++ - workspaces and projects. + <li>Set the OpenSSL include/header directory path under the + <b><i>Directories</i></b> tab - <i><b>Include Files</b></i> setting in + the <i><b>Tools->Options</b></i> dialog. A typical value would be + something like: <code>openssl-0.9.6\inc32</code></li> + <li>Set the OpenSSL library directory path under the + <b><i>Directories</i></b> tab - <i><b>Library Files</b></i> setting in + the <i><b>Tools->Options</b></i> dialog. A typical value would be + something like: <code>openssl-0.9.6\out32dll</code></li> <li>Open the <code>ACE.dsw</code> workspace, and refer to the ACE build and installation instructions above for details on creating a <code>config.h</code> configuration header for this platform. Once - the <code>config.h</code> file has been created, build the + the <CODE>config.h</CODE> file has been created, build the <code>ACE_SSL</code> project.</li> </ol> <h3>Borland C++</h3> -<p>Support for building ACE's ACE_SSL library and TAO's SSLIOP - pluggable protocol with Borland C++ does exist. -<ol> - <li>Set the <code>SSL_ROOT</code> environment variable to the location - of the directory containing the OpenSSL <code>inc32</code> and - <code>out32</code> directories. - <li>Add <code>ssl=1</code> to your MPC - <code>$ACE_ROOT/bin/MakeProjectCreator/config/default.features</code> - or <code>$ACE_ROOT/local.features</code> file, and re-run MPC to add - support for building the ACE_SSL library to your Borland C++ makefiles. - <li>Build ACE and TAO. -</ol> +<p>Support for building TAO's SSLIOP pluggable protocol with Borland C++ + does exist. First get a patch for the Open SSL makefile from <A + HREF="http://www.tenermerx.com/tao_bcb/index.html"> + http://www.tenermerx.com/tao_bcb/index.html</A>. Then build the OpenSSL + library. When you use the DLL version of ACE+TAO you have to build a DLL + version of OpenSSL. Then you must set the environment variable SSL_ROOT + to the location of your OpenSSL and then build ACE and TAO as normally. </p> -<hr><p> -</p><h3><a name="minimum_build">What Do I Need to Build for TAO?</a></h3> +<HR><P> +<H3><A NAME="minimum_build">What Do I Need to Build for TAO?</A></H3> Toshio Hori <toshi@etl.go.jp> provided these suggestions on building just what's needed for (a subset of) TAO:<p> I usually make: -</p><pre> $ACE_ROOT/ace, +<pre> + $ACE_ROOT/ace, $ACE_ROOT/apps/gperf, $TAO_ROOT/tao, $TAO_ROOT/TAO_IDL, and @@ -2436,72 +2543,75 @@ Pentium-III/550MHz, 256MB memory, 512MB swap machine. (Top secret: I renice the 'make' process to the highest priority, -20... ;-) To save time and space, I set -<pre> TAO_ORBSVCS = Naming Time Trader ImplRepo +<pre> + TAO_ORBSVCS = Naming Time Trader ImplRepo </pre> -in <code>$ACE_ROOT/include/makeinclude/platform_macros.GNU</code> also. See -<a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/TAO/docs/configurations.html#orbsvcs">TAO's orbsvcs +in $ACE_ROOT/include/makeinclude/platform_macros.GNU also. See +<a href="TAO/docs/configurations.html#orbsvcs">TAO's orbsvcs library customization instructions</a> for more information.<p> -</p><hr><p> </p><h3><a name="resource_requirements">System Resource -Requirements</a></h3> The amount of system resources required to build +<HR><P> <H3><A NAME="resource_requirements">System Resource +Requirements</A></H3> The amount of system resources required to build ACE and TAO varies greatly. The required system resources are influenced by OS and compiler platform, build options, and component configurations. As a rough guide, the typical peak memory requirement -can be well over 512 MB (notably, for TAO's orbsvcs). Depending on +can be well over 256 MB (notably, for TAO's orbsvcs). Depending on your OS and compiler configuration, an <strong>entire</strong> build -of ACE and TAO can use well over 4 GB of disk space. It's usually not +of ACE and TAO can use well over 2 MB of disk space. It's usually not necessary to build <strong>all</strong> of ACE and TAO, though.<p> Much less disk space is required for just the libraries. For example, -see the <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/docs/ACE-subsets.html#ACE%20Library%20Size%20Breakdown">ACE -library subset sizes</a>.</p><p> +see the <a href="docs/ACE-subsets.html#ACE Library Size Breakdown">ACE +library subset sizes</a>.<p> If you run out of memory when building, you might consider trying -some or all of these suggestions:</p><p> -</p><ul> - <li>Enable or increase virtual memory. If you're on a <a href="#Linux">Linux</a> or <a href="#LynxOS">LynxOS</a> platform, +some or all of these suggestions:<p> +<ul> + <li>Enable or increase virtual memory. If you're on a <a + href="#Linux">Linux</a> or <a href="#LynxOS">LynxOS</a> platform, please see the appropriate sections above.<p> - </p></li><li>Disable/enable optimization and/or debugging. See the + <li>Disable/enable optimization and/or debugging. See the <a href="#flags">Makefile Flags</a> discussion for information on how to do that via ACE's Makefiles.<p> - </p></li><li>If you're using g++, try removing <code>-pipe</code> from + <li>If you're using g++, try removing <code>-pipe</code> from <code>CFLAGS</code> in your <code>include/makeinclude/platform_macros.GNU</code> file.<p> - </p></li><li>Restrict the components that you build. For ACE and TAO, see the + <li>Restrict the components that you build. For ACE and TAO, see the discussion of <code>ACE_COMPONENTS</code> in the - <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/docs/ACE-subsets.html">ACE subsets</a> page. For TAO's + <a href="docs/ACE-subsets.html">ACE subsets</a> page. For TAO's orbsvcs, see the discussion of <code>TAO_ORBSVCS</code> in - <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/TAO/docs/configurations.html#orbsvcs">orbsvcs Library configuration information</a>.<p> + <a href="TAO/docs/configurations.html#orbsvcs">orbsvcs Library configuration information</a>.<p> If disk space is a problem, disabling debugging should greatly reduce object code, and therefore, library size. This is especially -true with g++.</p><p> +true with g++.<p> Toshio Hori <toshi@etl.go.jp> provided these tips for reducing -disk space usage:</p><p> +disk space usage:<p> To save space on a Unix machine, I usually run 'find . -name \*.dsw -o -name \*.dsp -o -name \*.bor | xargs rm -f' in $ACE_ROOT at first after I untar the distribution. They are meaningless in my environment (Files named '*.dsw' and '*.dsp' are used for MSVC++ and files named '*.bor' are for Borland C++ -Builder.)</p><p> +Builder.)<p> Finally, to save space, may want to run 'make clean' after 'make'. It removes generated object files and leaves libraries/executables intact. If you want to remove any of the libraries/executables, as -well, try 'make realclean'.</p><p> +well, try 'make realclean'.<p> -</p></li></ul> +</ul> -<p></p><hr><p> -</p><h3><a name="MPC">General MPC information</a></h3> +<P><HR><P> +<H3><A NAME="MPC">General MPC information</A></H3> If you are attempting to generate project files using MPC, and you get the following error message:<br> -<pre>ERROR: Unable to find the MPC modules in /builds/ACE_wrappers/MPC. +<pre> +ERROR: Unable to find the MPC modules in /builds/ACE_wrappers/MPC. You can set the MPC_ROOT environment variable to the location of MPC. </pre> @@ -2518,7 +2628,8 @@ anonymous CVS server and set your MPC_ROOT environment variable.</li> If you do not have access to the DOC Group CVS repository, you can check out MPC from the OCI anonymous CVS server using the following command. -<pre>cvs -d :pserver:anonymous@anoncvs.ociweb.com:/cvs co MPC +<pre> +cvs -d :pserver:anonymous@anoncvs.ociweb.com:/cvs co MPC </pre> The README and USAGE files in the MPC directory are an up-to-date source @@ -2532,89 +2643,50 @@ http://downloads.ociweb.com/MPC/</a>, however much of MPC has changed since it's writing. It will be updated as newer versions of the TAO Developer's Guide is released. -</p> -<p> -</p><h3><a name="eclipse">Working with ACE in Eclipse</a></h3> - - -<p> -The Eclipse CDT C++ development environment can be used to develop ACE applications. You can configure a new CDT project to build ACE using either a local source distribution or checking out ACE from CVS in Eclipse. These are the steps to create the CDT project to build ACE. -</p> - -<p> -<h4>To create an Eclipse project for ACE starting from CVS:</h4> -<ol> -<li>In the "CVS Repository Exploring" perspective, navigate to the module containing ACE.</li> -<li>Checkout the module using "Check Out As" and select the "project configured using the New Project Wizard" option.</li> -<li>Select "Standard Make C++ Project" for the project type.</li> -<li>Follow the steps outlined above, up to the point of running make, for building ACE on your platform. Use "path_to_your_eclipse_workspace"/"project_name" as your $ACE_ROOT. -<li>If you had to regenerate the makefiles using MPC, select the root folder for your poject and use the import wizard to add them to your project.</li> -<li>Select the root folder for the project and use the "Create Make Target" wizard to setup the appropriate make command and options.</li> -<li>Select the root folder and run "Build Make Target." This will build ACE.</li> -</ol> -</p> - - - -<p> -<h4>To create an Eclipse project for ACE from a local source distribution:</h4> -<ol> -<li>Launch the "New Project Wizard" in Eclipse.</li> -<li>Select "Standard Make C++ Project" for the project type.</li> -<li>On the project name page, uncheck the "use default" location option and replace the default path with the path to your source distribution.</li> -<li>Follow the steps, up to the point of running make, for building ACE on your platform. -<li>If you had to regenerate the makefiles using MPC, select the root folder for your poject and use the import wizard to add them to your project.</li> -<li>Select the root folder for the project and use the "Create Make Target" wizard to setup the appropriate make command and options.</li> -<li>Select the root folder and run "Build Make Target." This will build ACE.</li> - - -</ol> -</p> - -</p> - -<hr><p> -</p><h3><a name="advanced">Advanced Topics</a></h3> - -<ul> - <li><a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/docs/ACE-porting.html">Porting ACE and TAO to a New OS Platform</a> - </li><li><a href="#Non-static%20Object%20Manager">Non-static ACE_Object_Manager</a> - </li><li><a href="#cloning">Cloning the Source Tree</a> - </li><li><a href="#mvs">Additional Build Tips for MVS</a> - </li><li><a href="#flags">Makefile Flags</a> - </li><li><a href="http://www.cs.wustl.edu/%7Elevine/CVS.html">Version Control</a> - </li><li><a href="http://www.cs.wustl.edu/%7Ecleeland/ace/makefile-hints.html">ACE Makefile hints</a> - </li><li><a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/docs/ACE-SSL.html">ACE SSL effort</a> -</li></ul> - -<p></p><hr align="left" width="50%"><p> -</p><h4><a name="Non-static Object Manager">Non-static -ACE_Object_Manager</a></h4> The ACE_Object_Manager can be instantiated +<HR><P> +<H3><A NAME="advanced">Advanced Topics</A></H3> + +<UL> + <LI><A + HREF="docs/ACE-porting.html">Porting ACE and TAO to a New OS Platform</A> + <LI><A HREF="#Non-static Object Manager">Non-static ACE_Object_Manager</A> + <LI><A HREF="#cloning">Cloning the Source Tree</A> + <LI><A HREF="#mvs">Additional Build Tips for MVS</A> + <LI><A HREF="#flags">Makefile Flags</A> + <LI><A HREF="http://www.cs.wustl.edu/~levine/CVS.html">Version Control</A> + <LI><A HREF="http://www.cs.wustl.edu/~cleeland/ace/makefile-hints.html">ACE Makefile hints</a> + <LI><A HREF="docs/ACE-SSL.html">ACE SSL effort</a> +</UL> + +<P><hr align=left width="50%"><P> +<H4><A NAME="Non-static Object Manager">Non-static +ACE_Object_Manager</A></H4> The ACE_Object_Manager can be instantiated as a static object, can be instantiated on the stack of the main program thread, or can be explicitly instantiated and destroyed by the application with <code>ACE::init ()</code> and <code>ACE::fini -()</code>. The comments in the <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/ace/Object_Manager.h">header +()</code>. The comments in the <a href="ace/Object_Manager.h">header file, <code>ace/Object_Manager.h</code></a>, as well as Section 1.6.3 in <a href="http://www.riverace.com/docs">The ACE Programmer's Guide</a> -provide more detail.<p> +provide more detail.<P> <strong><blink><font color="#ff0000">NOTE:</font></blink></strong> Special requirements are imposed on applications if the ACE_Object_Manager is instantiated, by ACE, on the stack of the main thread. This behavior is selected by defining <code>ACE_HAS_NONSTATIC_OBJECT_MANAGER</code> in -<code>ace/config.h</code>. Again, see the ACE Object_Manager <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/ace/Object_Manager.h">header file, +<code>ace/config.h</code>. Again, see the ACE Object_Manager <a +href="ace/Object_Manager.h">header file, <code>ace/Object_Manager.h</code></a> for more information. One of these requirements is discussed here, because it is so important. Please note that <code>ACE_HAS_NONSTATIC_OBJECT_MANAGER</code> is defined in the distributed ACE <code>config.h</code> headers for -VxWorks and Win32.</p><p> +VxWorks and Win32.<p> The important requirement is that the program <strong>must</strong> declare its <code>main</code> function with two arguments, even if they're not used, and with <code>int</code> return type: -</p><pre><code> +<pre><code> int main (int, char *[]) </code></pre> @@ -2629,7 +2701,7 @@ Alternatively, this feature can be disabled by commenting out the difficult on VxWorks. And, you'd either have to call static constructors and destructors manually or unload/load the program between runs. On Win32, disabling the feature can possibly lead to -shutdown difficulties.</p><p> +shutdown difficulties.<p> <strong><blink><font color="#ff0000">WARNING:</font></blink></strong> <code>ACE_HAS_NONSTATIC_OBJECT_MANAGER</code> assumes that your @@ -2639,11 +2711,11 @@ entry point something other than <code>main</code>, you'll need to construct and destroy the ACE_Object_Manager. The best way to do that is to call <code>ACE::init ()</code> and <code>ACE::fini ()</code>. Or, see the <code>#define</code> of <code>main (int, char *[])</code> -in <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/ace/OS.h"><code>ace/OS.h</code></a> to see how ACE does +in <a href="ace/OS.h"><code>ace/OS.h</code></a> to see how ACE does that for entry points named <code>main</code>. -</p><p></p><hr align="left" width="50%"><p> -</p><h4><a name="cloning">Cloning the Source Tree</a></h4> +<P><hr align=left width="50%"><P> +<H4><A NAME="cloning">Cloning the Source Tree</A></H4> On UNIX platforms, we typically like to support multiple platform builds using the same ACE source tree. This idiom is supported by ACE @@ -2651,43 +2723,45 @@ using the $ACE_ROOT/bin/create_ace_build script or $ACE_ROOT/bin/clone.cpp program. To use build and use the clone program, first make sure there's a file -called <code>platform_macros.GNU</code> that contains the correct platform-specific -Makefile configurations in the <code>$ACE_ROOT/include/makeinclude/</code> +called platform_macros.GNU that contains the correct platform-specific +Makefile configurations in the $ACE_ROOT/include/makeinclude/ directory, as well as making sure there's a $ACE_ROOT/ace/config.h file that includes the desired platform/compiler specific -configuration header. Then perform the following steps:<p> +configuration header. Then perform the following steps:<P> -</p><pre>% cd $ACE_ROOT/bin +<pre> +% cd $ACE_ROOT/bin % make % mv clone ~/bin % rehash -</pre><p> +</pre><P> Then create a ./build subdirectory someplace, e.g., under $ACE_ROOT. Once this is done, then invoke the top-level Makefile with the -"clone" target, e.g.:</p><p> +"clone" target, e.g.:<P> -</p><pre>% cd $ACE_ROOT +<pre> +% cd $ACE_ROOT % mkdir build-SunOS5 % cd build-SunOS5 % make -f ../Makefile clone % setenv ACE_ROOT $cwd % make -</pre><p> +</pre><P> This will establish a complete tree of links. In addition, make sure -you set your <code>LD_LIBRARY_PATH</code> to -<code>$ACE_ROOT/ace:$ACE_ROOT/lib:$LD_LIBRARY_PATH</code> on SVR4 UNIX -platforms.</p><p> +you set your <CODE>LD_LIBRARY_PATH</CODE> to +<CODE>$ACE_ROOT/ace:$ACE_ROOT/lib:$LD_LIBRARY_PATH</CODE> on SVR4 UNIX +platforms.<P> When you do a make in the $ACE_ROOT directory you will be producing object code that is not stored in the same place as the original source tree. This way, you can easily build another platform in a -parallel tree structure.</p><p> +parallel tree structure.<P> -<b> VERY IMPORTANT! </b></p><p> +<B> VERY IMPORTANT! </B><P> -If you use the "clone trick" discussed above, make sure that the +If you use the "clone trick" discussed above, make sure that the symbolic links are correctly in place before starting the build. In particular, if you plan to clone the tree, it is preferable to do so before you start a build procedure on the original tree. This is @@ -2697,7 +2771,7 @@ You would end up with links pointing to object files of another platform. If you clone the tree after you've done a build on the original tree, make sure to remove all ".obj", ".shobj" and (any other files or directories) in all subdirectories before starting the build -on your cloned tree.</p><p> +on your cloned tree.<P> Alternatively, the perl script <code>ACE_wrappers/bin/create_ace_build</code> can be used to create @@ -2706,24 +2780,24 @@ It filters out all but the necessary files, so the warning above does not apply. See the comments at the top of the script itself for usage information. -</p><p></p><hr align="left" width="50%"><p> -</p><h4><a name="mvs">Additional Build Tips for MVS</a></h4> +<P><hr align=left width="50%"><P> +<H4><A NAME="mvs">Additional Build Tips for MVS</A></H4> For all intents and purpose, MVS OpenEdition (OE) is another flavor of -UNIX, therefore, the instructions under <a href="#aceinstall">Building -and Installing ACE on Unix</a> can be used along with the following -additional tips:<p> +UNIX, therefore, the instructions under <A HREF="#aceinstall">Building +and Installing ACE on Unix</A> can be used along with the following +additional tips:<P> You can get a copy of GNU make that has been ported to MVS OpenEdition from -the <a href="http://www.s390.ibm.com/products/oe/index.html">IBM OpenEdition web site</a>. +the <A HREF="http://www.s390.ibm.com/products/oe/index.html">IBM OpenEdition web site</A>. ACE's make scheme generates compile commands that have options and operands interspersed. By default, the c89/cc/c++ compiler expects all options to precede all operands. To get around this, you must set a special compiler environment variable (_CXX_CCMODE) to 1 which tells the compiler -to allow options and operands to be interspersed.</p><p> +to allow options and operands to be interspersed.<P> -Note that the environment variable <code>LD_LIBRARY_PATH</code> is -called <code>LIBPATH</code> on MVS.</p><p> +Note that the environment variable <CODE>LD_LIBRARY_PATH</CODE> is +called <CODE>LIBPATH</CODE> on MVS.<P> Shared objects are built a little different on MVS than on other UNIX implementations. This has been accounted for in the makefiles @@ -2733,7 +2807,7 @@ side-deck file and it must be included in subsequent link edits with application code. For more information on this see the C/C++ MVS Programming Guide. If you want to build your application statically, i.e., using libACE.a instead of libACE.so, you can set ACELIB to -ACELIB_STATIC in platform_mvs.GNU.</p><p> +ACELIB_STATIC in platform_mvs.GNU.<P> When the libACE.so file is built (via the MVS pre-linker and binder), you will get a rc=4 from the pre-linker. This is ok. This is due to some @@ -2742,43 +2816,43 @@ link step. Note, however, there shouldn't be any unresolved references from the binder (linkage editor). You can get pre-link and link maps by uncommenting the PMAP and LMAP lines in the platform_mvs.GNU file. -</p><p></p><hr align="left" width="50%"><p> -</p><h4><a name="flags">Makefile Flags</a></h4> +<P><hr align=left width="50%"><P> +<H4><A NAME="flags">Makefile Flags</A></H4> GNU make provides many options to customize its operation. See its documentation for more information. One example is that for multi-cpu -UNIX machines you will be able to build faster if you use:<p> +UNIX machines you will be able to build faster if you use:<P> -</p><pre><code> +<pre><code> % make -j <em>n</em> </code></pre><p> which allows parallel compilation. The number <i>n</i> should typically be the number of CPUs. It is likely that builds will be faster even on single-CPU UNIX machines with <code>make -j -2</code>.</p><p> +2</code>.<P> ACE further supports the following flags. They can be enabled either on the command line, e.g., "make purify=1", or added to your -<code>platform_macros.GNU</code>. To disable the option, -set the flag to null, +platform_macros.GNU. To disable the option, set the flag to null, e.g., "make debug=". Some flags support setting to 0 disable, e.g., "make debug=0". debug=1 is enabled in the platform files that are -released with ACE.</p><p> +released with ACE.<P> Please note that the effects of a flag may be platform specific. Also, combinations of certain flags may or may not be allowed on specific platforms, e.g., debug=1 opt=1 is supported by g++ but -not all other C++ compilers.</p><p> +not all other C++ compilers.<P> If you use Purify or Quantify: purify or quantify <strong>must</strong> be on your <code>PATH</code>. By default, ACE puts the Purify/Quantify caches below <code>/tmp</code>. To override that, set the <code>PURE_CACHE_BASE_DIR</code> variable, either in your environment or on the <code>make</code> make command line, to the destination -directory for your instrumented libraries.</p><p> +directory for your instrumented libraries.<p> -</p><pre>Flag Description +<PRE> +Flag Description ---- ----------- debug Enable debugging; see DCFLAGS and DCCFLAGS. exceptions Enable exception handling (not supported by all platforms). @@ -2830,7 +2904,7 @@ split Build the library by first splitting up the ACE source to 1 overrides debug to 0. Usually, users do not need to be concerned with make targets. -Just enter "make" on the command line to build. A few notable +Just enter "make" on the command line to build. A few notable targets are listed below. Target Description @@ -2840,60 +2914,51 @@ show_statics Lists all static objects in object files built for show_uninit Lists all uninitialized in object files built for current directory. Only supported for g++. -</pre> -<hr><p> +</PRE> +<HR><P> -</p><hr><p> -</p><h3><a name="power">Building from anonymous CVS</a></h3> -If users are building from our <a href="http://cvs.doc.wustl.edu/anoncvs.html"> anon cvs </a> the +<HR><P> +<H3><A NAME="power">Building from anonymous CVS</A></H3> +If users are building from our <a +href="http://cvs.doc.wustl.edu/anoncvs.html"> anon cvs </a> the GNUmakefiles, and project files for building on various platforms will not be available. Users from anon cvs are expected to generate them -using <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/MPC/README">MPC </a> before building ACE, TAO or +using <a href="MPC/README">MPC </a> before building ACE, TAO or CIAO. We point out some suggestions below to get bootstrapped -quickly. +quickly. -<ul> - <li> Please see <a href="#MPC"> instructions </a> above to download - MPC from anon cvs repository <p> - </p></li><li>Please make sure that you have <a href="http://www.perl.org/"> - perl</a> installed, preferably perl +<UL> + <LI> Please see <a href="#MPC"> instructions </a> above to download + MPC from anon cvs repository <p> + <LI>Please make sure that you have <a href="http://www.perl.org"> + perl</a> installed, preferably perl 5.8 or higher. Users on Win32 based platforms are recommended to use <a href="http://www.activestate.com/Products/ActivePerl/"> Active State Perl </a>. We use active state perl without problems. We have ran into problems trying to use the cygwin version of perl on Win32 based platforms. <p> - </p></li><li>If you just want to build ACE and associated tests, examples, + <LI>If you just want to build ACE and associated tests, examples, and associated utility libraries, we recommend that you do <p> - <code> $ACE_ROOT/bin/mwc.pl ACE.mwc </code> </p><p> + <CODE> $ACE_ROOT/bin/mwc.pl ACE.mwc </CODE> <p> + + from <CODE> $ACE_ROOT </CODE> to generate GNUmakefiles. Please use - from <code> $ACE_ROOT </code> to generate GNUmakefiles. Please use + <CODE> $ACE_ROOT/bin/mwc.pl -type vc6 ACE.mwc </CODE> <p> - <code> $ACE_ROOT/bin/mwc.pl -type vc6 ACE.mwc </code> </p><p> + to generate VC6 project and workspace files. Please use <CODE>-type + vc71</CODE> to generate VC71 project and solution files. - to generate VC6 project and workspace files. Please use <code>-type - vc71</code> to generate VC71 project and solution files. + <LI>If you want to build TAO+CIAO and its associated libraries + please see <a href="TAO/TAO-INSTALL.html"> TAO-INSTALL <a> and <a + href="TAO/CIAO/CIAO-INSTALL.html"> CIAO-INSTALL </a> for details. +</UL> - </p></li><li>If you want to build TAO+CIAO and its associated libraries - please see <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/TAO/TAO-INSTALL.html"> TAO-INSTALL </a><a> and </a><a href="http://www.cs.wustl.edu/%7Eschmidt/ACE_wrappers/TAO/CIAO/CIAO-INSTALL.html"> CIAO-INSTALL </a> for details. -</li></ul> +<HR><P> -<hr><p> - -Back to the <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE.html">ACE</a> +Back to the <A HREF="http://www.cs.wustl.edu/~schmidt/ACE.html">ACE</A> home page. - - -</p><p> -<!--<EM> -Visitor # -from -<EM><br> --> - -<!-- hhmts start --> -Last modified: Wed Aug 25 11:18:59 PDT 2004 -<!-- hhmts end --> - - -</p></body></html> +<!--#include virtual="/~schmidt/cgi-sig.html" --> +</BODY> +</HTML> |