[omniORB] Implementation Repository

[Duncan Grisby]

On Wednesday 5 March, Thomas Lockhart wrote:

> I'm not sure if there was a decision on whether this is a standalone 
> package or something inside the omniORB tree (and later the omniORBpy 
> tree too).

At least to start with, I don't want to make it part of the omniORB
tree, since it isn't going to be finished for a while. I'm happy for
it to go in the omniORB CVS as a new top-level module. Alternatively,
you might want to create a whole new SourceForge project for it.

>   If it is standalone, I can work on autoconf support, which 
> should be pretty easy with enough borrowing from the omniORB 
> infrastructure. If it is merged, then most of the make system can just 
> be adopted from an existing example.

That will be good, but remember two things:

 1. Autoconf isn't available everywhere, notably on Windows.
 2. The omniORB build environment is nightmarishly complex. Think
    twice before saddling omniImR with it.

Cheers,

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan@grisby.org     --
   -- http://www.grisby.org --