TAO/TAO-INSTALL.html

   1 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
   2 <!--  -->
   3
   4 <HTML>
   5 <HEAD>
   6   <meta content="text/html; charset=ISO-8859-1" http-equiv="content-type">
   7   <TITLE>Building and Installing TAO</TITLE>
   8   <link rev=made href="mailto:schmidt@dre.vanderbilt.edu">
   9 </HEAD>
  10
  11 <BODY text    = "#000000"
  12       link    = "#000fff"
  13       vlink   = "#ff0f0f"
  14       bgcolor = "#ffffff">
  15
  16 <H5>Document Index</H4>
  17 <UL>
  18   <LI><A HREF="#build">Building and Installing TAO from a distribution</A>
  19   <LI><A HREF="#svn">Building and Installing TAO from git</A>
  20 </UL>
  21
  22 <HR>
  23 <H4><A NAME="build">Building and Installing TAO from a distribution</H4>
  24
  25
  26 <p>The following table summarizes platforms on which TAO runs, see the
  27 <a href="../ACE-INSTALL.html#platforms">ACE installation notes</A> for an
  28 overview of all the platforms ACE runs on, these are all candidates
  29 to run TAO on:<P>
  30
  31 <table width="100%" border=1>
  32   <tr valign=top>
  33     <td><b>Fully supported, i.e., continually tested and used daily</b></td>
  34     <td>Windows (Microsoft Visual C++ 7.1, 9.0, 10.0, 11.0, 12, 14.0, 14.1, and 14.2),
  35         Linux/Intel (Redhat, Debian, and SuSe), Android
  36     </td>
  37   </tr>
  38   <tr valign=top bgcolor="#AFAFAF">
  39    <td><b>Nearly fully supported, i.e., sometimes tested</b></td>
  40    <td>HP/UX 11.x, LynxOS
  41    </td>
  42   </tr>
  43   <tr valign=top>
  44     <td><b>Partially supported, i.e., infrequently tested</b></td>
  45     <td>Solaris 9, FreeBSD, NetBSD, Windows CE, MacOSX, Linux/Alpha (RedHat, SuSE, and Debian), and AIX 5.x
  46     </td>
  47   </tr>
  48   <tr valign=top bgcolor="#AFAFAF">
  49     <td><b>Planned support, i.e., pending</b></td>
  50     <td></td>
  51   </tr>
  52   <tr valign=top>
  53     <td><b>Formerly Supported Platforms</b></td>
  54     <td> Embarcadero C++ Builder, Sun/C++ 5.1 through 5.4, g++
  55          prior to 2.95.x, HP/UX 10.x, pSoS, Chorus, DEC UNIX, SCO, UnixWare, MVS,
  56          Windows 9x/ME, Chorus, Tandem NS, OpenVMS 8.3 IA64
  57     </td>
  58   </tr>
  59 </table>
  60
  61 <P>Any UNIX/POSIX/Win32 variation is a potential target platform for
  62 TAO.  If you have <A
  63 HREF="../docs/ACE-porting.html">porting
  64 questions</A> or have a problem compiling the TAO along with ACE
  65 wrappers on the platforms shown above please send email to the <A
  66 HREF="http://www.dre.vanderbilt.edu/~schmidt/TAO-mail.html">TAO mailing list</A> and we'll
  67 try to help you fix the problems.  You can also submit issues and
  68 enhancement requests through
  69 <a href="https://github.com/DOCGroup/ACE_TAO">github</a>.<P>
  70
  71 TAO can be obtained <A
  72 HREF="https://download.dre.vanderbilt.edu">electronically</A>
  73 via the WWW and ftp.  <A
  74 HREF="https://www.dre.vanderbilt.edu/TAO">TAO</A> is bundled
  75 with the <A
  76 HREF="https://www.dre.vanderbilt.edu/ACE"> ACE </A> release.  You'll
  77 always need the most recent version of ACE because TAO tracks and
  78 influences changes to ACE.  Always use the ACE+TAO release
  79 bundle as a single piece instead of trying to mix and match things up.<P>
  80
  81 <HR><P>
  82 <H3>On UNIX platforms</H3>
  83
  84
  85 <OL>
  86   <LI>Set <CODE>ACE_ROOT</CODE> environment variable as outlined in
  87       the <a href="../ACE/ACE-INSTALL.html">ACE
  88       installation notes</A>.<P>
  89
  90   <LI>Build and install ACE under <CODE>$ACE_ROOT</CODE>.<P>
  91
  92       <UL>
  93         <LI>Change directory to <CODE>$ACE_ROOT/ace</CODE> and execute
  94             <CODE><A HREF="#makenotes">make</A></CODE>.<P>
  95         <LI>Also build GPERF under <CODE>$ACE_ROOT/apps/gperf/src</CODE><P>
  96       </UL>
  97
  98   <LI>Set <CODE>TAO_ROOT</CODE> environment variable to
  99       <CODE>$ACE_ROOT/TAO</CODE>.<P>
 100
 101   <LI>Build and install the TAO release under <CODE>$TAO_ROOT</CODE>.
 102         <P> TAO also uses GNUmakefiles and project files generated
 103         from MPC to compile. The full distribution will
 104         come with stock GNUmakefiles, project files (for VC9 and VC
 105         10) awhich were all generated by
 106         MPC. </P>
 107
 108         <P>The easiest and recommended way to compile the
 109           <B>complete</B> TAO distribution by simply simply executing
 110           <code><a href="#makenotes">make</a></code>
 111           in the <CODE>$TAO_ROOT</CODE> directory.
 112         </P>
 113
 114         <P>A smaller subset, that may be of interest to test basic TAO
 115           functionality, is:
 116           <CODE>$TAO_ROOT/tao</CODE>,
 117           <CODE>$TAO_ROOT/TAO_IDL</CODE>,
 118           <CODE>$TAO_ROOT/tests/Param_Test</CODE>.
 119           Then you can execute the <CODE>run_test.pl</CODE> script in
 120           <CODE>$TAO_ROOT/tests/Param_Test</CODE> and/or
 121           follow the instructions contained in the <CODE>README</CODE>
 122           file in the same directory.
 123         </P>
 124
 125         <P>If you wish to compile the ORB services distributed with TAO,
 126           including the <CODE>Naming Service</CODE> you
 127           must include <CODE>$TAO_ROOT/orbsvcs</CODE> to the list
 128           above.  Please see the
 129           <A HREF="docs/configurations.html#orbsvcs">TAO configuration documentation</a>
 130           for a discussion on how to create a subset configuration of specific
 131           TAO ORB servcies.
 132         </P>
 133         <P> If you wish to compile all the core tao and orbsvcs,
 134           including its dependencies in ACE and ACEXML, you can do the
 135           following <OL>
 136           <LI>
 137           Unpack the distribution from DOC group's
 138           website.</LI>
 139           <LI>
 140           Set the environment variables $ACE_ROOT and
 141           $TAO_ROOT.</LI>
 142           <LI>Create config.h and platform_macros.GNU at
 143           the right places</LI>
 144           <LI>Delete all the GNUmakefiles (or sln and
 145           vproj file as the case may be) from the TAO distribution using
 146           the 'find' command.</LI>
 147           <LI>Change directory to $TAO_ROOT.</LI>
 148           <LI>Run MPC like this, $ACE_ROOT/bin/mwc.pl TAO_ACE.mwc -type gnuace </LI>
 149           <LI>Run
 150           'make'.</LI> </OL></P><P> This will create all the required libraries for TAO
 151           and TAO orbsvcs. In step 6, use -type vc71 if you want to
 152           generate VC71 project and workspace files for Win32. Please
 153           see <A href="../MPC/docs/USAGE"> MPC USAGE </A> document for
 154           details on how to generate build files for other compilers
 155           and tools.</P>
 156
 157    <LI>To test that the TAO release is properly configured,
 158         follow instructions on executing the various examples under
 159       <CODE>$TAO_ROOT/tests</CODE>.<P>
 160
 161 </OL>
 162
 163 <h3><strong><a name="sun_g++_notes">Note About g++ On
 164 Solaris for x86 Target</a></strong></h3>
 165
 166 If you install g++/gcc from <a href="http://www.blastwave.org"> blastwave
 167 </a> then this note is applicable for you. If you are in the habit of
 168 building g++/gcc from sources directly, please feel free to skip this
 169 section. <p>
 170
 171 The distribution from <a href="http://www.blastwave.org">blastwave</a> has,
 172 as we believe, a bug in it. This bug manifests as compilation errors
 173 when you try to build the orbsvcs when debugging is enabled. Please
 174 remember that debugging is enabled in your platform_macros.GNU if you
 175 haven't specifically disabled it. The easiest way to address this
 176 issue is to set debug=0 in platform_macros.GNu file or build a g++
 177 compiler for your target platform. A bug has been registered with
 178 blastwave. If you have more questions please feel to contact <a
 179 mailto="bala at dre.vanderbilt.edu"> Bala Natarajan </a>.
 180
 181 <h2><strong><a name="makenotes">A Note On Make</a></strong></h2>
 182
 183 Since TAO is built atop ACE, TAO re-uses ACE's Makefile structure as
 184 well.  Thus, just like ACE requires GNU Make, so too does TAO.  More
 185 exactly, versions of <code>make</code> which are known to <em>not</em>
 186 work include those from Solaris 4.x and 5.x, HP-UX, the latest BSD,
 187 etc.<p>
 188
 189 GNU Make can be obtained from various places in source and binary
 190 form. Please see <a href="../ACE/ACE-INSTALL.html">ACE-INSTALL.html</a>
 191 for details from where they can be obtained.<P>
 192
 193 <HR><P>
 194 <h3>Using cross compilation</h3>
 195
 196 With cross compilation you build on the so called host system for a certain
 197 target system. The host system can for example be linux and the target
 198 can for example be VxWorks, LynxOS, or Linux.
 199
 200 If you are building TAO for a VxWorks target, please see the detailed
 201 instructions for building and installing ACE and TAO in <a
 202 href="../ACE/ACE-INSTALL.html#vxworks">$ACE_ROOT/ACE-INSTALL.html</a>.</p>
 203 <p>If you are building TAO for an Android target, please see the notes
 204 for building and installing ACE and TAO in <a
 205 href="../ACE-INSTALL.html#android">$ACE_ROOT/ACE-INSTALL.html</a>.</p>
 206
 207     <P>Cross-compiling TAO is not much different than building it for a
 208       self-host.  The one major difference is that TAO's IDL compiler
 209       must be built and run on the host; it's not necessary to run it
 210       on the target.
 211       There are several ways to do this, below we document the two
 212       most common approaches:
 213       </P>
 214
 215     <H4>Modifying the default location for the IDL compiler</H4>
 216
 217     <P>By default TAO assumes that the IDL compiler is located in:
 218       <CODE>$ACE_ROOT/bin/tao_idl</CODE> and that the GPERF tool
 219       is located in <CODE>$ACE_ROOT/bin/gperf</CODE>, this is fine for
 220       hosted builds, but not for cross-compilation.
 221       Unfortunately there is no good default for cross-compilation
 222       builds because different sites choose a different location for
 223       their tools.
 224     </P>
 225     <P>
 226       The location of the IDL compiler is set when the makefiles (whether
 227       GNU, Visual Studio projects, or any other type) are generated using
 228       MPC. If you are using GNU make for the target build, you can follow the
 229       procedure below with no further steps. If, however, you are using
 230       Visual Studio for the target build, you must generate the Visual Studio
 231       projects with a specification of where the hosted IDL compiler is. One
 232       common way to do this is to use the MPC <code>-value_template</code>
 233       option to specify the path to the IDL compiler, either using a
 234       fully specified path or an environment variable. For example, to specify
 235       the location with the <code>HOST_TAO_IDL</code> environment variable,
 236       generate your projects with the MPC command line option
 237       <code>-value_template tao_idl=$(HOST_TAO_IDL)</code>. Then before
 238       running Visual Studio to cross-build for the target, be sure that the
 239       <code>HOST_TAO_IDL</code> environment variable is set to the location
 240       of the host-built IDL compiler. Note that if the host-built IDL compiler
 241       requires a PATH setting different from what's set in the Visual Studio
 242       environment, you must set the PATH environment variable and specify the
 243       <code>/USEENV</code> option to devenv.
 244     </P>
 245     <P>If your builds are using GNU make, you can override the default values
 246       by adding several lines to your <code>platform_macros.GNU</code> file.
 247       Assuming $(HOST_ROOT) is set to the location of your host build where
 248       you previously built gperf and tao_idl, you can change the target
 249       build by adding the following lines:
 250 <PRE>
 251 TAO_IDL := $(HOST_ROOT)/bin/tao_idl
 252 TAO_IDLFLAGS += -g $(HOST_ROOT)/bin/gperf
 253 TAO_IDL_DEP := $(HOST_ROOT)/bin/tao_idl$(EXEEXT)
 254 </PRE>
 255
 256     <P>Obviously you must first build the tools for the host platform,
 257       typically you would do this as follows:
 258 <PRE>
 259 # (1) Create a clone directory for the host:
 260
 261 $ cd ACE_wrappers
 262 $ mkdir -p build/HOST
 263 $ ./bin/create_ace_build build/HOST
 264
 265 # (2) Configure the host build:
 266
 267 $ echo '#include "ace/config-HOST.h"' > build/HOST/ace/config.h
 268 $ echo 'include $(ACE_ROOT)/include/makeinclude/platform_HOST.GNU' \
 269      > build/HOST/include/makeinclude/platform_macros.GNU
 270
 271 # Often host builds are static:
 272 $ echo 'static_libs_only=1' \
 273      >> build/HOST/include/makeinclude/platform_macros.GNU
 274
 275 # (3) Build the host tools
 276
 277 $ cd build/HOST
 278 $ export ACE_ROOT=$PWD
 279 $ make -C ace
 280 $ make -C apps/gperf/src
 281 $ make -C TAO/TAO_IDL
 282 </PRE>
 283
 284     <P>Then configuring the location of the tools for the target
 285       could be done as shown here:
 286 <PRE>
 287 # (4) Create a clone directory for the target:
 288
 289 $ cd ACE_wrappers
 290 $ mkdir -p build/TARGET
 291 $ ./bin/create_ace_build build/TARGET
 292
 293 # (5) Configure the target build:
 294
 295 $ echo '#include "ace/config-TARGET.h"' > build/HOST/ace/config.h
 296 $ echo 'include $(ACE_ROOT)/include/makeinclude/platform_TARGET.GNU' \
 297      > build/TARGET/include/makeinclude/platform_macros.GNU
 298
 299 # (6) Configure the TARGET build to use the HOST IDL compiler and
 300 #     gperf tools, as described above.
 301 </PRE>
 302
 303     <H4>Alternative configuration, using links</H4>
 304
 305     <P>Some developers prefer to set up the host tools using symbolic
 306       links (Unix) or copy of <code>tao_idl</code> (NT).
 307       By way of example, here is how you could setup a
 308       croos-compilation environment for Unix,
 309       the host is <CODE>SunOS5/g++</CODE>,
 310       the target is <CODE>VxWorks</CODE>.
 311       It assumes that the ACE+TAO distribution has been
 312       unpacked, with TAO below ACE_wrappers.  It uses the
 313       ACE_wrappers/bin/create_ace_build script to create a shadow
 314       build
 315       tree:
 316 <ol>
 317   <li><code>cd ACE_wrappers</code>
 318   <li><code>bin/create_ace_build SunOS5_g++</code>
 319   <li><code>bin/create_ace_build vxworks</code>
 320   <li><code>cd build/vxworks/bin</code>
 321   <li><code>/bin/rm -r tao_idl</code>
 322   <li><code>ln -s ../../SunOS5_g++/bin/tao_idl</code>
 323 </ol>
 324
 325       <P>To build on the host:
 326 <ol>
 327   <li><code>cd build/SunOS5_g++</code>
 328   <li><code>export ACE_ROOT=`pwd`;
 329     export LD_LIBRARY_PATH=`pwd`/ace:`pwd`/lib:$LD_LIBRARY_PATH</code>
 330   <li><code>(cd ace; make && cd ../tests; make && cd ../TAO; make) &gt;
 331     make.log</code>
 332   <li><code>cd ../vxworks</code>
 333   <li><code>export ACE_ROOT=`pwd`</code>
 334   <li><code>(cd ace; make && cd ../tests; make && cd ../TAO; make) &gt;
 335     make.log</code>
 336 </ol>
 337
 338     <P>For Win32 hosts, please see the detailed instructions for building
 339       and installing ACE and TAO in
 340       <a href="../ACE/ACE-INSTALL.html#vxworks">ACE_ROOT/ACE-INSTALL.html</a>,
 341       and
 342       <a href="../ACE/ACE-INSTALL.html#VxWorks/NT">Building ACE on
 343         Tornado/NT hosts for VxWorks targets</a>
 344     </P>
 345
 346     <P>Please note that dynamic loading of libraries is not supported
 347       by TAO for any cross-compiled target.  Therefore, dynamic
 348       service configuration of the TAO ORB is not supported.
 349     </p>
 350
 351     <P>If using perfect hashing, TAO_IDL needs gperf to be built on
 352       the host. That's the default on many platforms.  First, build
 353       <code>gperf</code> in the
 354       <code>ACE_wrappers/apps/gperf/src/</code> directory.
 355     </P>
 356
 357     <H4>Which one is right for me?</H4>
 358
 359     <P>Using links to cross-compile TAO may appear simpler at first
 360       glance.  However, storing the location in the
 361       <CODE>platform_macros.GNU</CODE> is more amenable for
 362       sites where many developers share the same configuration files,
 363       or where ACE+TAO are compiled once and used by a medium or large
 364       size group.
 365     </P>
 366
 367 <HR><P>
 368 <H3>On Windows NT and Windows 2000 and Windows XP</H3>
 369
 370 <P><CODE>TAO_IDL</CODE> does not contain its own preprocessor, so it
 371 needs to use an external preprocessor.  Depending on which compiler was
 372 used to build <CODE>TAO_IDL</CODE>, the default preprocessor will change.
 373 For example, if compiled with MSVC, <CODE>TAO_IDL</CODE> will look for
 374 CL.EXE in the path. There are cases where this will not work, such as in cross-compiling
 375 or if the preprocessor is not in the path.  These situations require that
 376 environment variables are set on the machine to override the
 377 built-in settings.  More information about these environment variables can
 378 be found in the <a href="docs/compiler.html#idl_env">TAO_IDL documentation.</a></P>
 379
 380 <P>It is also mandatory to set the <CODE>ACE_ROOT</CODE> environment
 381 variable as outlined in the
 382 <a href="../ACE/ACE-INSTALL.html">ACE
 383 installation notes</A> and the <code>TAO_ROOT</code> environment variable.
 384   </P>
 385
 386 Remember to <a href="../ACE/ACE-INSTALL.html">set
 387 up ACE</A> before building TAO.
 388
 389 Make sure that you first build <code>$TAO_ROOT\TAO_IDL</code> and then <code>
 390 $TAO_ROOT\tao</code> because in order to compile the core TAO libraries
 391 you need to have <code>TAO_IDL</code> compiled.
 392
 393 <H4>Visual C++ 7.1 and newer</H4>
 394
 395 <P>It works best if TAO is placed in ACE_wrappers so TAO ends up in
 396 <CODE>ACE_wrappers\TAO</CODE> because the Visual Studio Project files
 397 are setup up to work in this configuration. If you move it, then make
 398 sure you regenerate the project files to look for the include and
 399 library files in the correct place. The default place for placing the
 400 library files are $ACE_ROOT/lib. You can change this setting in <a
 401 href="../bin/MakeProjectCreator/config/acedefaults.mpb"> this base
 402 project </a> file.</P>
 403
 404 <OL>
 405   <LI>Make sure ACE is built (For Visual C++ 7.1, use ACE.sln). <P>
 406
 407   <LI>First make sure <CODE>ACE_wrappers\bin</CODE> is listed in the Executable
 408       Directories in Tools|Options.  This is needed if using the TAO_IDL
 409       compiler under MSVC.  If you intend to also use the release
 410       version of the libraries in the same workspace you have to be
 411       careful, since the executable name for TAO_IDL is same in debug
 412       and release builds. You can use only or the other in the same
 413       workspace. This shouldn't be an issue since the projects for
 414       tests and examples are set up to transparently use one or the
 415       other.
 416  <P>
 417   <LI>Load the solution <CODE>$TAO_ROOT\TAO.sln</CODE> and build first
 418       the TAO_IDL compiler. After that build the TAO
 419       library. This solution has almost all the projects under TAO
 420       which can be built. Therefore please pick and choose projects
 421       that you want to build.<P>
 422
 423   <LI>To build the Param_Test, load the solution
 424       <CODE>tests\tests.sln</CODE>
 425       and build both client and server. <P>
 426 </OL>
 427
 428 <H4>Upgrading From Older Releases</H4>
 429
 430 <P>When a newer version of ACE/TAO is installed, rebuild all should be
 431 used to make sure everything is built correctly.</P>
 432
 433 <H4>Changing Include Paths</H4>
 434
 435 <P>If you prefer <code>#include &lt;corba.h&gt;</code> over <code> #include
 436 &lt;tao/corba.h&gt;</code> then you will need to change your Project Settings
 437 to also contain the <code>TAO/tao</code> directory.  You'll find this in the
 438 C/C++ settings under Input.</P>
 439
 440 <H4>Creating Static Libraries (*.lib)</H4>
 441
 442 <P> Instructions for dynamic libraries apply to static libraries as
 443 well. Users will have to use the _Static.sln files for
 444 creating static libraries and linking with them.
 445
 446 <H4>MinGW and Cygwin</H4> <P>
 447
 448 <P>First, follow the build instructions in the
 449 <A HREF="../ACE/ACE-INSTALL.html#mingw">ACE installation notes.</A>
 450 When building with MinGW and Cygwin you are using the GNU make under Windows.
 451 When you use make from the commandline, make sure that <code>TAO_ROOT</code> is
 452 set to a full path or to <code>%ACE_ROOT%/TAO</code>, which will also result
 453 in setting a full path. Setting it with the Unix style to <code>$ACE_ROOT/TAO</code>
 454 will not work, setting it using the make style to <code>$(ACE_ROOT)/TAO</code> looks
 455 to work but will cause problems when building the TAO services, so don't do that.
 456 The correct way is:
 457 <BLOCKQUOTE><code>set TAO_ROOT=%ACE_ROOT%/TAO</code></BLOCKQUOTE>
 458
 459 <HR>
 460 <H3>Perl Scripts</H3>
 461
 462 <P>Several of TAO's tests and examples contain perl scripts that automate the
 463 execution of these tests. The scripts are found as "run_test.pl" in the
 464 directory of the test.</p>
 465
 466 <HR>
 467 <P>
 468
 469 <H3>Minimum CORBA</H3>
 470
 471 <P>By default, all components in TAO will be compiled.  If you only
 472 want support for <A HREF="docs/minimumTAO.html">minimumTAO</A>, define
 473 TAO_HAS_MINIMUM_CORBA. This can be accomplished by the following:
 474 create <code>ACE_wrappers/bin/MakeProjectCreator/config/default.features</code>
 475 with the contents:</p>
 476 <code>minimum_corba=1</code><p>
 477 Then regenerate the project files with MPC using <code>perl bin/mwc.pl</code>,
 478 see also <A HREF="../ACE/ACE-INSTALL.html#MPC">ACE-INSTALL.html</A> for more info
 479 about the MPC generation. This <code>miminum_corba=1</code> will add compiler
 480 flags to the C++ compiler and the IDL compiler to indicate that minimum corba
 481 is enabled.
 482 For your own project code you can define TAO_HAS_MINIMUM_CORBA in the ace/config.h file or
 483 by using <CODE>make minimum_corba=1</CODE> when you compile TAO after that.</P>
 484
 485 <strong><blink><font color="#ff0000">WARNING:</font></blink></strong>
 486 Make sure that if you build the orbsvcs with minimum_corba=1 you also
 487 build the core libraries with minimum_corba=1!<P>
 488
 489 <HR>
 490 <P>
 491
 492 <H3>CORBA/e compact and micro</H3>
 493
 494 <P>By default, all components in TAO will be compiled.  If you only
 495 want support for CORBA/e compact or micro you must regenerate the
 496 makefiles shipped with the distribution.
 497 This can be accomplished by the following:
 498 create <code>ACE_wrappers/bin/MakeProjectCreator/config/default.features</code>
 499 with the contents:</p>
 500 <code>corba_e_compact=1</code><p>
 501 or</p>
 502 <code>corba_e_micro=1</code><p>
 503 Then regenerate the project files with MPC using <code>perl bin/mwc.pl</code>,
 504 see also <A HREF="../ACE/ACE-INSTALL.html#MPC">ACE-INSTALL.html</A> for more info
 505 about the MPC generation. This <code>corba_e_x=1</code> will add compiler
 506 flags to the C++ compiler and the IDL compiler to indicate that CORBA/e
 507 is enabled.
 508 For your own project code you can define <code>CORBA_E_COMPACT</code> or
 509 <code>CORBA_E_MICRO</code>
 510 in the ace/config.h file.</P>
 511 <P>
 512
 513 <HR><P>
 514 <H3><A NAME="resource_requirements">System Resource Requirements</A></H3>
 515 Please see the
 516 <a href="../ACE/ACE-INSTALL.html#resource_requirements">ACE-INSTALL.html</a> System
 517 Resource Requirements discussion for information on system resources
 518 required to build ACE and TAO.<p>
 519
 520 <HR>
 521 <H4><A NAME="svn">Building and Installing TAO from git</H4>
 522
 523 If users are building from our <a
 524 href="https://github.com/DOCGroup/ACE_TAO">git archive</a> the
 525 GNUmakefiles, and project files for building on various platforms will
 526 not be available. Users from git are expected to generate them
 527 using <a href="../MPC/docs/README">MPC</a> before building ACE or TAO.
 528 We point out some suggestions below to get bootstrapped
 529 quickly.
 530
 531 <UL>
 532   <LI> Please see <a href="#MPC"> instructions </a> above to download
 533   MPC from our git repository</LI><p/>
 534   <LI>Please make sure that you have <a href="http://www.perl.org">
 535   perl</a> installed, preferably perl
 536    5.8 or higher. Users on Win32 based platforms are recommended to use
 537   <a href="https://www.activestate.com/products/perl"> Active
 538   State Perl </a>. We use active state perl without problems. We have
 539   ran into problems trying to use the cygwin version of perl on Win32
 540   based platforms.</LI><p/>
 541   <LI>When building from git, the ACE_ROOT and TAO_ROOT environment
 542   variable settings differ from their settings in the ACE_wrappers
 543   prepackaged source distribution:
 544     <UL>
 545       <LI>ACE_ROOT should point to the ACE subdirectory of the top level
 546       ACE_TAO directory</LI>
 547       <LI>TAO_ROOT should point to the TAO subdirectory of the top level
 548       ACE_TAO directory</LI>
 549     </UL>
 550   </LI><p/>
 551   <LI>If you just want to build TAO and associated tests, examples,
 552   and associated utility libraries, we recommend the following
 553   alternatives:
 554     <UL>
 555     <LI> Build ACE and TAO separately. ACE needs to be built first and
 556   instructions for building ACE are available at <a
 557   href="../ACE/ACE-INSTALL.html#MPC">ACE-INSTALL</a>. GNUmakefiles and
 558   project files for TAO can be generated by using the following
 559   commands:<p>
 560     <CODE> $ACE_ROOT/bin/mwc.pl TAO.mwc -type gnuace </CODE> <p>
 561    from <CODE> $TAO_ROOT </CODE> to generate GNUmakefiles. Use <CODE>
 562   -type vc71 </CODE>  to generate VC71 project and solution files,
 563   or <CODE>-type vc8</CODE> for VC8 project and solution files, or
 564    <CODE>-type bmake</CODE> for Borland C++ make files.</LI><p/>
 565    <LI> Build ACE+TAO together in one shot. To do that please issue
 566   the following commands: <p>
 567   <CODE> $ACE_ROOT/bin/mwc.pl TAO_ACE.mwc </CODE> <p>
 568    from <CODE>$TAO_ROOT</CODE>. This will generate GNUmakefiles for
 569   ACE, gperf, and core ACE+TAO libraries. Issuing a
 570   <CODE>'make'</CODE> from <CODE>$TAO_ROOT </CODE> will build all of
 571   the above in one shot. You can use <CODE> -type vc71 </CODE> to
 572   generate VC71 project and workspace files. <CODE>TAO_ACE.sln</CODE>
 573   can be used by users to build ACE+TAO from a single workspace
 574   file. Users can use <CODE> -type vc8 </CODE> to generate the VC8
 575   solutions files.
 576     </LI>
 577     </UL>
 578   </LI><p/>
 579 </UL>
 580
 581
 582 <HR><P>
 583 Back to the <A HREF="https://www.dre.vanderbilt.edu/~schmidt/TAO.html">TAO</A> home page.
 584
 585 <!--#include virtual="/~schmidt/cgi-sig.html" -->
 586 </BODY>
 587 </HTML>