<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7653.14">
<TITLE>Can't run OmniPy out of the box? (_omniidl module problem)</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<P><FONT SIZE=2 FACE="Arial">Hi, </FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">I am running on Windows 2000, 32 bit, and have installed omniORB-4.1.1-x86-win32-vc7.zip (since that's the version of VC we use) and omniORBpy-3.1-x86-win32-python2.5.zip.</FONT></P>
<P><FONT SIZE=2 FACE="Arial">Having extracted the contents of these zips alongside each other under C:\projects [see footnote] and added C:\projects\omniORBpy-3.1\lib\python and C:\projects\omniORBpy-3.1\lib\x86_win32 to my PYTHONPATH, and C:\projects\omniORB-4.1.1\bin\x86_win32 to my PATH (I found that having C:\projects\omniORBpy-3.1\bin\x86_win32 in my PATH seemed to cause problems?) I now get the following error when trying to compile my first IDL file with "<SPAN LANG="en-gb"></SPAN></FONT><SPAN LANG="en-gb"><FONT SIZE=2 FACE="Courier New">omniidl -bpython example_echo.idl</FONT><FONT FACE="Times New Roman"> ": </FONT></SPAN></P>
<P><SPAN LANG="en-gb"><FONT FACE="Courier New">omniidl: Could not import back-end 'python'</FONT></SPAN>
<BR><SPAN LANG="en-gb"><FONT FACE="Courier New">omniidl: Maybe you need to use the -p option?</FONT></SPAN>
<BR><SPAN LANG="en-gb"><FONT FACE="Courier New">omniidl: (The error was 'No module named python')</FONT></SPAN>
<BR><SPAN LANG="en-gb"><FONT SIZE=2 FACE="Courier New">From the documentation of omniidl, I can see that it will be trying to load the python module omniidl_be.python here. Running "import omniidl_be.python" from the Python interpreter gives me slightly more information - the problem is "import _omniidl" at line 97 of lib\python\omniidl\main.py. I can find nothing in either zip matching this name, i.e. containing "_omniidl". What am I doing wrong? Do I need to build something after all?</FONT></SPAN></P>
<P><SPAN LANG="en-gb"><FONT SIZE=2 FACE="Courier New">Ben Keeping</FONT></SPAN>
<BR><SPAN LANG="en-gb"><FONT SIZE=2 FACE="Courier New">-----------------</FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">Footnote: I did see the following instruction in the README:</FONT></SPAN>
</P>
<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">"If you do not have Autoconf support on your platform (e.g. on</FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">Windows), you must install the omniORBpy source in the $TOP/src/lib</FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">directory of a working omniORB 4.1 tree. Make sure the directory is</FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">called omniORBpy -- if you downloaded a release archive you must</FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">rename the directory to remove the version from the directory name.</FONT></SPAN>
</P>
<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">Once you have the source in the right place, simply do a make export</FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">in the $TOP/src/lib/omniORBpy directory."</FONT></SPAN>
</P>
<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">But assumed this didn't apply as I am not building anything from source.</FONT></SPAN>
</P>
<pre>______________________________________________________________________
This email is intended only for the use of the individual(s) to whom it is addressed and may be privileged and confidential.
Unauthorised use or disclosure is prohibited.If you receive This e-mail in error, please advise immediately and delete the original message.
This message may have been altered without your or our knowledge and the sender does not accept any liability for any errors or omissions in the message.
</pre></BODY>
</HTML>