-----------------------------------------
Compiling CorbaScript on top of omniORB2.
-----------------------------------------

CorbaScript can be compiled and run on top of omniORB2: Always use the
lastest supported omniORB2 release (see doc/index.html).

With CorbaScript, there is no need for stubs/skeletons generation:
the OMG IDL information is obtained at runtime from the Interface Repository.
However, you need to load IDL files into the Interface Repository.

As omniORB2 doesn't currently provide an Interface Repository and its
associated loader (the IDL to IFR compiler), we advise to use the
ORBacus's IFR 3.x and its loader.

On Unix systems:
----------------

To obtain the two needed ORBacus tools, you need to build the ORBacus 3.x
for C++ product:
* download the ORBacus 3.x for C++ product from http://www.ooc.com/,
* uncompress it,
* read carefully all README files, because some platforms need special options,
* start the 'runconfig' script to configurate it,
* select your environment settings (OS, C++ compiler, compilation preferences),
* make it.

After that, you only need to keep:
* the 'irserv' binary which is the Interface Repository server,
* the 'irfeed' and 'idlcpp' binaries which are the IDL to IFR compiler/loader.
* the 'irdel' binary to remove IDL definitions from the Interface Repository.
* the 'libJTC.so' library if you have compiled ORBacus in multithreaded mode.
* the 'libIDL.so' and 'libOB.so' libraries if you have compiled ORBacus
  in shared libraries mode.
By keeping them, we would like to say "copy them into another directory".
So when you compile CorbaScript, you must indicate this directory as extra
binary and library paths.

After that, you could remove the ORBacus product if needed.

On Windows systems:
-------------------

To obtain these two ORBacus tools, you need to build the ORBacus 3.x
for C++ product:
* download the ORBacus 3.x for C++ product from http://www.ooc.com/,
* uncompress it,
* read carefully the INSTALL.WINDOWS file,
* configurate the config/Make.rules.mak file correctly,
* make it.

After that, you only need to keep:
* the 'irserv.exe' binary which is the Interface Repository server,
* the 'irfeed.exe' and 'idlcpp.exe' binaries which are the IDL to IFR compiler/loader.
* the 'irdel.exe' binary to remove IDL definitions from the Interface Repository.
* the 'JTC.dll' library if you have compiled ORBacus in multithreaded mode.
* the 'IDL.dll' and 'OB.dll' libraries if you have compiled ORBacus
  in dynamic shared libraries mode.
By keeping them, we would like to say "copy them into another directory".

After that, you could remove the ORBacus product if needed.

----------------------------------------
Running CorbaScript on omniORB2/Windows.
----------------------------------------

Running the CorbaScript engine and demonstrations need the ORBacus's Interface Repository.
DON'T FORGET to put the directory containing these programs into your PATH environment variable.

CorbaScript can access to the omniORB2 Name Service if it is configured as described
into the omniORB_280/README.win32 file (i.e. its IOR must be recorded into the Windows Registry).
