[omniORB] omniORB 4.0.1 soon

[Corrigan Coleman]

To facilitate the resolution some rather Horrid EBCDIC to ASCII issues for
SNI BS2000.

-----Original Message-----
From: Duncan Grisby [mailto:duncan@grisby.org]
Sent: 20 January 2003 11:33
To: Corrigan Coleman
Cc: omniorb-list@omniorb-support.com
Subject: Re: [omniORB] omniORB 4.0.1 soon 


On Saturday 18 January, Corrigan Coleman wrote:

> 	could you include these few minor changes to omniidl to close files
> created by the cxx backend 

I'll check that in in my next wave of checkins. Out of interest, why
do you need that?  It doesn't do any harm to explicitly close the
files, but it should happen anyway.

> How are you disposed to having the sources in orbcore starting with an
> initial #include "config.h" ?

Why is that necessary?  All of the sources currently end up including
omniconfig.h. If you need to do anything special, it can go there.

> What is the story with build tools for omniORB ? will it be autoconfig for
> the foreseeable future ? 

It will be autoconf (where available) for 4.0.x. I am hoping to throw
away the make stuff altogether for 4.1, and replace it with something
else, probably SCons.

Cheers,

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan@grisby.org     --
   -- http://www.grisby.org --
************************************************************************
This e-mail and any files transmitted with it are confidential and may be
privileged and are intended solely for the individual named/ for the use of
the individual or entity to whom they are addressed.If you are not the
intended addressee, you should not disseminate, distribute or copy this
e-mail.Please notify the sender immediately if you have received this e-mail
by mistake and delete this e-mail from your system.If you are not the
intended recipient, you are notified that reviewing, disclosing, copying,
distributing or taking any action in reliance on the contents of this e-mail
is strictly prohibited.Please note that any views or opinions expressed in
this e-mail are solely those of the author and do not necessarily represent
those of Traventec Limited.E-mail transmission cannot be guaranteed to be
secure or error-free as information could be intercepted, corrupted, lost,
destroyed, or arrive late or incomplete.Traventec Limited therefore does not
accept liability for any errors or omissions in the contents of this
message, which arise as a result of e-mail transmission.The recipient should
check this e-mail and any attachments for the presence of viruses.This
e-mail has been swept for computer viruses however Traventec Limited accepts
no liability for any damage caused by any virus transmitted by this e-mail.