summaryrefslogtreecommitdiff
path: root/ACE/ACE-INSTALL.html
diff options
context:
space:
mode:
Diffstat (limited to 'ACE/ACE-INSTALL.html')
-rw-r--r--ACE/ACE-INSTALL.html140
1 files changed, 2 insertions, 138 deletions
diff --git a/ACE/ACE-INSTALL.html b/ACE/ACE-INSTALL.html
index adfa45e30d2..3edb65ad76c 100644
--- a/ACE/ACE-INSTALL.html
+++ b/ACE/ACE-INSTALL.html
@@ -281,150 +281,14 @@ The following sections explain how to build ACE on:
<hr align="left" width="50%">
<h2><a name="unix">Building and Installing ACE on UNIX</a></h2>
-As of ACE 5.4, you can choose between two methods of building ACE on
-UNIX:
+As of ACE 6.1, you can building ACE on
+UNIX with:
<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 for Windows</a> is different from both of
the UNIX methods.
-<h3><a name="unix_autoconf">Building ACE with GNU Autoconf</a></h3>
-<p>
-GNU Autoconf support is available in the ACE and ACE+TAO distributions
-in the DOC group website. Support for Autoconf is not included in
-distributions that contain CIAO.
-</p>
-<p>
-GNU Autoconf support has been partially present in a number of ACE
-versions. However, ACE 5.4 was the first version that supported it in
-earnest. The range of platforms on which GNU autoconf support is regularly
-tested is not as broad as for the traditional configuration method, so you
-should be careful to test the resulting ACE library before using it in
-your applications. You can review the
-<a href="http://www.dre.vanderbilt.edu/scoreboard/" target="_blank">
-build scoreboard</a> to check the currently tested set of autoconfigured
-platforms (look for autoconf in the platform name).
-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@cse.wustl.edu">ACE users</a> mailing list
-using the standard <a href="PROBLEM-REPORT-FORM">PROBLEM-REPORT-FORM</a>.
-</p>
-<p>
-The kit has been bootstrapped so you do not need to install the GNU
-Autotools (autoconf, automake, libtool) unless you want to participate
-in <a href="#autoconf_development">testing and developing</a> this
-process further or if you are working directly off of sources in the
-ACE subversion repository. 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
- ACE version, and then change to the new directory:
- <pre> mkdir build
- cd build</pre>
- Note that you do not run the <code>create_ace_build.pl</code> utility
- 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]</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++.</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-fl-reactor</code> (no): Enable support for the
- <code>ACE_FlReactor</code> class.</li>
- <li><code>--enable-qt-reactor</code> (no): Enable support for the
- <code>ACE_QtReactor</code> class.</li>
- <li><code>--enable-tk-reactor</code> (no): Enable support for the
- <code>ACE_TkReactor</code> class.</li>
- <li><code>--enable-xt-reactor</code> (no): Enable support for the
- <code>ACE_XtReactor</code> class.</li>
- <li><code>--enable-gperf</code> (yes): Build the implementation of
- gperf that comes with ACE.</li>
- <li><code>--enable-qos</code> (no): Include the ACE_QoS library when
- building ACE.</li>
- <li><code>--enable-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-openssl</code>: Specifies the root directory of the
- OpenSSL installation; expects the specified directory to have
- <code>include</code> and <code>lib</code> subdirectories. To
- specify other locations for the header and libraries, use one or
- both of the following.</li>
- <li><code>--with-openssl-include</code>: Specify the directory
- containing the OpenSSL header files.</li>
- <li><code>--with-openssl-libdir</code>: Specify the directory
- containing the OpenSSL libraries.</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>
-
-<h4><a name="autoconf_development">Testing and Developing GNU Autotool
-Support in ACE</a></h4>
-<p>
-In order to test and develop the GNU Autotool support in ACE or
-bootstrap autotool support into ACE when working directly off of ACE
-sources in the subversion repository, you must have recent versions of GNU
-Autoconf, Automake and Libtool installed on your host. Once
-installed, autotool support may be bootstrapped into your workspace by
-doing the following:
- <blockquote>
- <code>
- cd ACE_wrappers<br>
- ./bin/bootstrap<br>
- </code>
- </blockquote>
-After doing so, you will be able to run the <code>configure</code>
-script.
-
<h3><a name="unix_traditional">Using the Traditional ACE/GNU Configuration</a></h3>
<p>
Here's what you need to do to build ACE using GNU Make and ACE's traditional