diff options
| author | schmidt <douglascraigschmidt@users.noreply.github.com> | 1998-08-17 19:50:26 +0000 |
|---|---|---|
| committer | schmidt <douglascraigschmidt@users.noreply.github.com> | 1998-08-17 19:50:26 +0000 |
| commit | 962d094081662fd384cd584c26778f87a7e140ac (patch) | |
| tree | 894280495bba67edaed4526ae1aa82be0677610e /etc | |
| parent | 5fa7d60aaabba24c31fb4fa4a34bb9f8baaf2fd3 (diff) | |
| download | ATCD-962d094081662fd384cd584c26778f87a7e140ac.tar.gz | |
*** empty log message ***
Diffstat (limited to 'etc')
| -rw-r--r-- | etc/ACE-porting.html | 78 |
1 files changed, 78 insertions, 0 deletions
diff --git a/etc/ACE-porting.html b/etc/ACE-porting.html new file mode 100644 index 00000000000..6c4ba40ccaa --- /dev/null +++ b/etc/ACE-porting.html @@ -0,0 +1,78 @@ +<HTML> +<HEAD> + <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> + <META NAME="Generator" CONTENT="Microsoft Word 97"> + <META NAME="Template" CONTENT="C:\PROGRAM FILES\MICROSOFT OFFICE\OFFICE\html +.dot"> + <META NAME="GENERATOR" CONTENT="Mozilla/4.05 [en] (Win95; I) [Netscape]"> + <TITLE>ACE-Porting</TITLE> +</HEAD> +<BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#0000FF" VLINK="#FF0000"> + +<HR> +<H3> +Porting ACE to a new Platform</H3> +Following is a suggestion of a logical step-by-step process that can be +used when porting the ADAPTIVE Communication Environment to a new platform. +<UL> +<LI> +<B>Make a config header file for the target platform</B></LI> +</UL> + +<DIR> +<DIR>There exists a different config header file in ACE_Wrappers/ace for +each platform to which ACE has been ported (like config-sunos5.5.h, config-sco- +4.2-nothread.h, +config-win32-borland.h and so on). It is in that file that the portability +macros for each particular configuration of ACE is set. A complete description +of the existent macros can be found in the ACE_Wrappers/ace/Readme file. +It would possibly be a good idea to look at the config-files for platforms +with similar characteristics as examples.</DIR> +</DIR> + +<UL> +<LI> +<B>Porting the ACE_OS class</B></LI> +</UL> + +<DIR> +<DIR>The ACE_OS encapsulates most of the differences between all different +implementations for Unix and Win32. It is the base class of the ACE OS +abstraction layer. Most of the work implied in porting of ACE to a new +environment resides in this class.</DIR> +</DIR> + +<UL> +<LI> +<B>Porting the different components of the OS abstraction layer</B></LI> +</UL> + +<DIR> +<DIR>The next logical step after porting the ACE_OS class, would be to +port all of the lower level components of the ACE OS abstraction layer +(System V IPC, Unix FIFO, Sockets classes and so on). A full list of the +categories and classes can be found in the ACE_Wrappers/ace/ACE_Categories +file. It is recommended to concentrate the work on one category at the +time, instead of going for the big-bang-port-all-at-once approach. The +ACE distribution comes with several test programs, which resides in the +ACE_Wrappers/ace/tests folder. They can be used to test the different component +s +as they are ported.</DIR> +</DIR> + +<UL> +<LI> +<B>Porting the higher level components of ACE</B></LI> +</UL> + +<DIR> +<DIR>Having ported (and tested) all the components of the ACE OS abstraction +layer, one can proceed to port the higher components of ACE (Reactor, Service +Configurator, Acceptor and so on). In fact, having reached this far in +the porting, it should be relatively easy to port the rest of ACE, as most +of the platform code tweaking should be localized in the OS abstraction +layer.</DIR> +</DIR> + +</BODY> +</HTML> |