Next: Adding a thread library
Up: Using PaCO++ with your
Previous: Using PaCO++ with your
Contents
Adding an ORB
For each ORB, PaCO++ needs to have a config file to generate the PaCO++ layers.
In the repertory ORB, you have to add a repertory for the new ORB. The name of the repertory is the name
that you want to give to PaCOIdlTool. For example, omniORB3 for omniORB3.x ORBs.
In this repertory you have to create a config file that's name is config
Now let see what to write into this configuration file :
- COMMAND_LINE
- : This is the command line that PaCO++ has to use to generate the CORBA stubs.
The files names have to be in this form : interface.idl
interface.h,cc. Example for
omniORB : ${PACOORB}/bin/omniidl -bcxx -Wbh=.h -Wbs=.cc
- CLASS_NAME_CLIENT
- This is the class where, in the CORBA stubs, PaCO++ has to find the abstracts methods of the interface
for the client. The macro NAME will be replace by the interface name. Example for omniORB : _impl_NAME
- CLASS_NAME_SERVANT
- This is the class where, in the CORBA stubs, PaCO++ has to find the abstracts methods of the interface
for the servant. The macro NAME will be replace by the interface name. Example for mico : POA_NAME
- CLASS_DEL
- Since PaCO++ doesn't use a C++ parser, PaCO++ has to find the beginning of the class it wants to find.
Example for mico : :.
- CLASS_END
- Since PaCO++ doesn't use a C++ parser, PaCO++ has to
find the end of the class it wants to find. Example for mico : };.
- MODULE_DEF
- Finally, PaCO++ needs to find modules declaration. Examples :
mico
namespace, omniORB
_CORBA_MODULE
Next: Adding a thread library
Up: Using PaCO++ with your
Previous: Using PaCO++ with your
Contents
2013-04-10