[omniORB] omniidl and Visual C++ v.6.0

[Da Silva, Pedro]

You need to add the omniidl path to the IDE.
Go to Tools->Options->Directories within that dialog in "Show directories
for" select "Executable files" and add the path in the "Directories" box.

impl_is_ready's second argument is a boolean which determines whether it's
blocking (0) or non blocking (1).

rgds,
Pedro

> Date: Fri, 23 May 2003 12:19:50 +0200 (MEST)
> From: Ren? Fosdal <fosdal at gmx.net>
> Subject: Re: [omniORB] omniidl and Visual C++ v.6.0
> To: omniorb-list at omniorb-support.com
> Message-ID: <32343.1053685190 at www37.gmx.net>
> Content-Type: text/plain; charset="iso-8859-1"
> 
> Hi Silvia,
> 
> I don't know about omniORB with Visual C++ (so far), but it 
> looks to me that
> you have to specify the complete path to omniidl. 
> 
> Regards,
> 
> Rene
> 
> > Hi All,
> > 
> > I'm trying to build a project in VC++ 6.0 (NT 4.0) but I'm having a 
> > problem.
> > I've searched the mailing list's archives but I didn't find anything
> > related.
> > 
> > I've created a configuration build for omniORB 
> (Build->Configurations),
> > and associated the IDL files (Project->Setting) with a few commands,
> > including the idl compilation with omniidl (of course). But 
> when I try 
> > to
> > build the same error always occurs:
> > 
> > The name specified is not recognized as an
> > internal or external command, operable program or batch file.
> > 
> > Has far as I can tell this refers to the command line: 
> omniidl -bcxx 
> > ......
> > If I compile the IDL in the command line everything goes OK,
> > The kind of error that I'm getting from VC++ is the one that
> > occurs when for instance you run a command that is unknown to the 
> > system.
> > So it looks like I'm missing something.
> > 
> > I'm really "clueless", if this has ever happened to anyone 
> please tip 
> > me.
> > 
> > By the way does anyone know if omniORB posses a constant to specify
> > an infinite timeout, I need this to give it  to 
> impl_is_ready so that 
> > the
> > server
> > registers itself and the ORB places it in an infinite "event 
> > processing"
> > loop .
> > I'm migrating from ORBIX and in his case this is in
> > CORBA::ORB.INFINITE_TIMEOUT.
> > 
> > Thanks a lot in advance,
> > Silvia
> > 
> > 
> > _______________________________________________
> > omniORB-list mailing list
> > omniORB-list at omniorb-support.com
> > http://www.omniorb-support.com/mailman/listinfo/omniorb-list
> > 
> 
> -- 
> +++ GMX - Mail, Messaging & more  http://www.gmx.net +++
> Bitte lacheln! Fotogalerie online mit GMX ohne eigene Homepage!
> 
> 
> 
> ------------------------------
> 
> _______________________________________________
> omniORB-list mailing list
> omniORB-list at omniorb-support.com
> http://www.omniorb-support.com/mailman/listinfo/omniorb-list
> 
> 
> End of omniORB-list Digest, Vol 1, Issue 420
> ********************************************
>