...
Update IExternal/omniOrb's requirements file
Regenerating files using omniidl
IDL stubs can be compiled like this:http://omniorb.sourceforge.net/omni41/omniORB/omniORB005.html
In our HepRepCorba package, we save two *.idl files: HepRep.idl and HepEventServer.idl. We use these as input to the omniidl binary that is created when we compile omniOrb.
omniidl -bcxx echo-Wba HepRep.idl
producing
HepRep.hh HepRepSK.cc, and HepRepDynSK.cc
and
omniidl -bcxx HepEventServer.idl
The product is the files: echoHepEventServer.hh and echoSKHepEventServerSK.cc
Rebuild HepRepCorba
In the HepRepCorba cmt requirements file there is a line
- Set some OmniOrb env variables
- This is useful for debugging
set ORBtraceLevel 0Documentation pertaining to this env variable is available here: http://omniorb.sourceforge.net/omni41/omniORB/omniORB004.html#toc20 In particular:
The following options control debugging trace output.
traceLevel default = 1
omniORB can output tracing and diagnostic messages to the standard error stream. The following levels are defined:
| |
level 0 | critical errors only |
level 1 | informational messages only |
level 2 | configuration information and warnings |
level 5 | notifications when server threads are created and communication endpoints are shutdown |
level 10 | execution and exception traces |
level 25 | trace each send or receive of a giop message |
level 30 | dump up to 128 bytes of each giop message |
level 40 | dump complete contents of each giop message |
The trace level is cumulative, so at level 40, all trace messages are output.