From 36dff72987c4412ba47b9d23f37e637005448d4b Mon Sep 17 00:00:00 2001 From: Steve Huston Date: Sat, 10 Jun 2006 22:37:05 +0000 Subject: ChangeLogTag:Sat Jun 10 22:32:03 UTC 2006 Steve Huston --- ACE-INSTALL.html | 559 ++++++++++++++++++++++++++++++------------------------- ChangeLog | 8 + bin/make_release | 1 - 3 files changed, 313 insertions(+), 255 deletions(-) diff --git a/ACE-INSTALL.html b/ACE-INSTALL.html index 71e18ad4441..3b6bc5d4aeb 100644 --- a/ACE-INSTALL.html +++ b/ACE-INSTALL.html @@ -7,9 +7,9 @@
-

Building and Installing ACE and Its Auxiliary Libraries and Services

+

Building and Installing ACE and Its Auxiliary Libraries and Services

-

Synopsis

+

Synopsis

The file explains how to build and install ACE, its Network Services, test suite and examples on the various OS platforms and compilers that @@ -33,7 +33,7 @@ tracking system to submit a report in accordance with our bug report process.

-

Document Index

+

Document Index

-

Building ACE on Tornado/NT hosts for VxWorks targets.
+

Building ACE on Tornado/NT hosts for VxWorks targets.

The following, very useful information was contributed by Chris Ryan and Paul von Behren. @@ -1523,7 +1573,7 @@ on Windows NT hosts: -
TAO on NT Tornado host, VxWorks target.
+

TAO on NT Tornado host, VxWorks target.

  1. Build ACE and TAO_IDL in the NT tree as already documented. @@ -1546,9 +1596,8 @@ on Windows NT hosts:

-

-Jaffar Shaikh's -Notes for Building ACE and TAO for VxWorks on NT host

+

Jaffar Shaikh's +Notes for Building ACE and TAO for VxWorks on NT host

Scenario: 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.

@@ -1682,56 +1731,8 @@ 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.

- -
-

Building and Installing ACE Network Services

- -The following explains how to build the ACE network services on UNIX and Win32. -

-

Building and Installing ACE Network Services on UNIX

- -Building and installing ACE Network Services on UNIX is relatively -simple (the process for Win32 is different). -Here's what you need to do:

- -

    - -
  1. Build and install ACE on UNIX as described earlier. 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 - (main) contained in $ACE_ROOT/netsvcs/servers/main.cpp - should also be compiled and ready to run.

    - -

  2. Set your LD_LIBRARY_PATH environment variable to - where the binary version of the ACE netsvcs library. For - example, you probably want to do something like the following

    - - 

    
-      % setenv LD_LIBRARY_PATH $ACE_ROOT/ace:$ACE_ROOT/lib:$LD_LIBRARY_PATH
-

    - -

  3. By default, if the shared object library is built, the services - are linked into the main driver program dynamically. - To specify which services should be linked in and executed, edit the - $ACE_ROOT/netsvcs/servers/svc.conf - 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 - Service Configurator - documentation to learn how the configuration file is parsed and - how the services are dynamically linked and executed. In - addition, refer to the Network - Services documentation to learn more about how to configure - each network service.

    - -

  4. If you only want to link the services statically, simply remove - or rename the svc.conf file.

    -

- -

-

Building and Installing ACE on RTEMS

+

Building and Installing ACE on RTEMS

export RTEMS_MAKEFILE_PATH=/opt/rtems/CPU-rtems/BSP
 # setup the build structure
@@ -1782,20 +1783,68 @@ cd ../TAO
 make
+ +
+

Building and Installing ACE Network Services

+ +The following explains how to build the ACE network services on UNIX and Win32. +

-

Building and Installing ACE Network Services on Win32

+

Building and Installing ACE Network Services on UNIX

+ +Building and installing ACE Network Services on UNIX is relatively +simple (the process for Win32 is different). +Here's what you need to do:

+ +

    + +
  1. Build and install ACE on UNIX as described earlier. 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 + (main) contained in $ACE_ROOT/netsvcs/servers/main.cpp + should also be compiled and ready to run.

    + +

  2. Set your LD_LIBRARY_PATH environment variable to + where the binary version of the ACE netsvcs library. For + example, you probably want to do something like the following

    + + 

    
+      % setenv LD_LIBRARY_PATH $ACE_ROOT/ace:$ACE_ROOT/lib:$LD_LIBRARY_PATH
+

    + +

  3. By default, if the shared object library is built, the services + are linked into the main driver program dynamically. + To specify which services should be linked in and executed, edit the + $ACE_ROOT/netsvcs/servers/svc.conf + 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 + Service Configurator + documentation to learn how the configuration file is parsed and + how the services are dynamically linked and executed. In + addition, refer to the Network + Services documentation to learn more about how to configure + each network service.

    + +

  4. If you only want to link the services statically, simply remove + or rename the svc.conf file.

    +

+ +

+

Building and Installing ACE Network Services on Win32

Once again, there are supplied project for MSVC 6.0 or later for the Network Services.

-

Building and Installing The ACE_SSL Library

+

Building and Installing the ACE_SSL Library

The first step for all platforms is to build and install the OpenSSL distribution. The ACE_SSL library must then be built according to the instructions below.

-

Unix

+

Unix

  1. Make sure the OpenSSL header file directory is in your compiler's include path, and that OpenSSL libraries are in your library link/load @@ -1820,7 +1869,7 @@ below.

    directory. The ACE_ROOT environment variable should be set prior to this point.
-

Microsoft Visual Studio

+

Microsoft Visual Studio

  1. Set the SSL_ROOT environment variable to the location of the directory containing the OpenSSL inc32 and @@ -1836,7 +1885,7 @@ below.

    the config.h file has been created, build the ACE_SSL project.
-

Borland C++

+

Borland C++

Support for building ACE's ACE_SSL library and TAO's SSLIOP pluggable protocol with Borland C++ does exist.

    @@ -1852,10 +1901,10 @@ below.

    -

    Building and Using GUI Reactors Libraries

    +

    Building and Using GUI Reactors Libraries

    There is a general method for building and using ACE_Reactors for various GUI libraries. -

    Building GUI Reactor Library

    +

    Building GUI Reactor Library

    1. Try to generate build files using MPC. Inspect the output of MPC to find out which features are necessary to build given reactor. Add these features to @@ -1905,24 +1954,26 @@ libraries. Windows the results are shared QtReactor.dll and import QtReactor.lib libraries or their variants depending on build options. When compiling TAO also GUI related libraries are created like libTAO_QtResource.so. -

      Using GUI Reactor Library

      +

      Using GUI Reactor Library

      Here one has at least three use cases: -
      Applications with their own build system.
      +
        +
      1. Applications with their own build system. To use ACE support for GUI one has to include specific GUI headers and link with specific ACE_[GUI]Reactor library. When using TAO support for GUI one has - also to link with specific TAO_[GUI]Resource library. -
        Applications with build system using MPC.
        + also to link with specific TAO_[GUI]Resource library.
        2. +
      2. Applications with build system using MPC. In general, it is better to create specific base projects for using ACE GUI support in such application. Base projects provided by ACE ACE_wrappers/bin/MakeProjectCreator/[ace,tao]_[gui][reactor,resource].mpb - may be an examples of how to do this. -
        Internal ACE applications like tests or examples.
        + may be an examples of how to do this.
        3. +
      3. Internal ACE applications like tests or examples. MPC project for internal ACE application using GUI support should be derived from ace_[gui]reactor.mpb base projects. To employ TAO support for GUI one should derive the project from tao_[gui]resource.mpb These base projects ensure that all necessary libraries are linked to the application, specifies features necessary to build a project and moreover impose a build order consistant with ACE. For example, the application project using XtReactor should be - derived from ace_xtreactor.mpb. -

        Notes on specific GUI Reactors

        + derived from ace_xtreactor.mpb.
        4. +
      +

      Notes on specific GUI Reactors

      • QtReactor
        • The build is controlled by ace_qtreactor [1 by default] feature. @@ -1956,7 +2007,7 @@ libraries. x11switch is ignored for this platform.
      -

      Installation Notes

      +

      Installation Notes

      • Windows (Windows NT, 2000, XP, 2003, etc., and Windows '9x/ME)

        @@ -2479,7 +2530,7 @@ libraries.

        -

        Compiling ACE with GNU g++

        +

        Compiling ACE with GNU g++

        If you use the GNU GCC g++ compiler please note the following: @@ -2521,7 +2572,7 @@ If you use the GNU GCC g++ compiler please note the following:

        -

        What Do I Need to Build for TAO?

        +

        What Do I Need to Build for TAO?

        Toshio Hori <toshi@etl.go.jp> provided these suggestions on building just what's needed for (a subset of) TAO:

        @@ -2544,8 +2595,8 @@ in $ACE_ROOT/include/makeinclude/platform_macros.GNU also. See library customization instructions for more information.

        -

        System Resource -Requirements

        The amount of system resources required to build +

        System Resource +Requirements

        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 @@ -2597,7 +2648,7 @@ well, try 'make realclean'.

      -

      General MPC information

      +

      General MPC information

      The Makefile Project Creator (MPC) is a tool that takes platform and building tool generic files (mpc files) as input, which describe basic @@ -2642,7 +2693,7 @@ versions of the TAO Developer's Guide is released.

      -

      Working with ACE in Eclipse

      +

      Working with ACE in Eclipse

      @@ -2650,7 +2701,7 @@ The Eclipse CDT C++ development environment can be used to develop ACE applicati

      -

      To create an Eclipse project for ACE starting from CVS:

      +

      To create an Eclipse project for ACE starting from CVS:

      1. In the "CVS Repository Exploring" perspective, navigate to the module containing ACE.
      2. Checkout the module using "Check Out As" and select the "project configured using the New Project Wizard" option.
        3. @@ -2665,7 +2716,7 @@ The Eclipse CDT C++ development environment can be used to develop ACE applicati

        -

        To create an Eclipse project for ACE from a local source distribution:

        +

        To create an Eclipse project for ACE from a local source distribution:

        1. Launch the "New Project Wizard" in Eclipse.
        2. Select "Standard Make C++ Project" for the project type.
          3. @@ -2682,7 +2733,7 @@ The Eclipse CDT C++ development environment can be used to develop ACE applicati

          -

          Advanced Topics

          +

          Advanced Topics

          -

          Non-static -ACE_Object_Manager

          The ACE_Object_Manager can be instantiated +

          Non-static +ACE_Object_Manager

          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 ACE::init () and ACE::fini @@ -2750,7 +2801,7 @@ in ace/OS_main.h to see how ACE does that for entry points named main.

          -

          Cloning the Source Tree

          +

          Cloning the Source Tree

          On UNIX platforms, we typically like to support multiple platform builds using the same ACE source tree. This idiom is supported by ACE @@ -2784,7 +2835,7 @@ See the comments at the top of the create_ace_build.pl script for further usage information.

          -

          Additional Build Tips for MVS

          +

          Additional Build Tips for MVS

          For all intents and purpose, MVS OpenEdition (OE) is another flavor of UNIX, therefore, the instructions under Building @@ -2820,7 +2871,7 @@ 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.

          -

          Makefile Flags

          +

          Makefile Flags

          GNU make provides many options to customize its operation. See its documentation for more information. One example is that for multi-cpu @@ -2918,7 +2969,7 @@ show_uninit Lists all uninitialized in object files built for

          -

          Building from anonymous CVS

          +

          Building from anonymous CVS

          If users are building from our anon cvs the GNUmakefiles, and project files for building on various platforms will not be available. Users from anon cvs are expected to generate them diff --git a/ChangeLog b/ChangeLog index 45d118616c8..8d8ec4a76dd 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,11 @@ +Sat Jun 10 22:32:03 UTC 2006 Steve Huston + + * ACE-INSTALL.html: Corrected a bunch of platform build things and + hopefully clarified the sections a bit. + + * bin/make_release: Removed the search for, and chmod for, dsp/dsw + files - they're for MSVC6 which is no longer generated. + Sat Jun 10 10:07:32 UTC 2006 Phil Mesnier * ace/Thread_Manager.cpp: diff --git a/bin/make_release b/bin/make_release index a0c73c050c7..5126de53d4f 100755 --- a/bin/make_release +++ b/bin/make_release @@ -819,7 +819,6 @@ sub generate_makefiles () { bin/mwc.pl -type vc71 $mpc_option $exclude_option; \ bin/mwc.pl -type borland $mpc_option $exclude_option; \ bin/mwc.pl -type vc71 $static_option; \ - find ./ -name '*.ds[p,w]' | /usr/bin/xargs chmod 0644;\ find ./ -name '*.bor' | /usr/bin/xargs chmod 0644;\ find ./ -name '*.vcproj' | /usr/bin/xargs chmod 0644;\ find ./ -name '*.sln' | /usr/bin/xargs chmod 0644"); -- cgit v1.2.1