[omniORB] OmniOrb and Visual Studio 2005 July 2005 CTP
Ketan Shah
ketan_shah at credence.com
Sun Aug 21 09:59:00 BST 2005
Yes. Now, after compiling distro, I have following error while running
omniidl:
omniidl: ERROR!
omniidl: Could not open Python files for IDL compiler
omniidl: Please put them in directory C:\omniORB-4.0.6
\src\tool\omniidl\cxx
omniidl: (or set the PYTHONPATH environment variable)
omniidl: (The error was 'No module named omniidl.main')
I am not sure, about my setting of PYTHONPATH which is pointing to
minimum version of python1.5.x copied under top of omniORB
installation directory.
Any other settings missing?
Thanks,
Ketan
----- Original Message -----
From: Slawomir Lisznianski <slisznianski at asyncnet.com>
Date: Saturday, August 20, 2005 6:58 am
Subject: Re: [omniORB] OmniOrb and Visual Studio 2005 July 2005 CTP
> Have you tried compiling the omniORB distro for your environment,
> ratherthan using downloaded binaries?
>
> Regards,
> Slawomir
>
>
> On Fri, 19 Aug 2005 20:03:30 -0700, "Ketan Shah"
> <ketan_shah at credence.com> said:
> >
> >
> > Using Visual Studio 2005 and July 2005 CTP release. While invoking
> > omniidl,
> > gives error on symbol "point_invoke_watson" not found in
MSVCR80.DLL
> >
> > Any ideas?
> >
> >
> > _______________________________________________
> > omniORB-list mailing list
> > omniORB-list at omniorb-support.com
> > http://www.omniorb-support.com/mailman/listinfo/omniorb-list
> >
> >
> > _______________________________________________
> > omniORB-list mailing list
> > omniORB-list at omniorb-support.com
> > http://www.omniorb-support.com/mailman/listinfo/omniorb-list
>
>
More information about the omniORB-list
mailing list