[omniORB] omniidl and pydev

[OKeeffe, Michael K]

>-----Original Message-----
>
>Hi,
>
>I'd like to try to write a backend for omniidl.
>
>Not considering myself a Real Programmer
>(http://catb.org/~esr/jargon/html/R/Real-Programmer.html)
>and just starting in Python (coming from 10 ys of
>Java), I would like to use the great pydev Eclipse
>plugin to debug and single-step the backend code.
>
>Has anybody tried this already?
>
>Pydev not being able to run the omniidl.exe I tried to
>run the Unix omniidlrun.py within the debugger.
>
>It fails with the message given below. It seems to
>miss the .so but there is no corresponding .dll for
>Windows.
>
>Have you some tips for me how I could get to debug
>omniidlrun.py or even omniidl.exe?
>

Glad to see you are checking out omniORB.

I think the first thing would be to get omniORB and omniORBpy running outside your dev environment to familiarize yourself with how it works.  The omniidl is used to compile the classes for the interface, based on the IDL file, and the stubs and skeletons required, so unless there are issues in building those files, you shouldn't have to run those through a debugger.  For example, in WSAD/Eclipse, I use Ant (http://ant.apache.org) to run the Java IDL compiler, and there are tools for Visual Studio to do the same thing on the C++ side.

It seems from the error message your configuration is incorrect, see http://omniorb.sourceforge.net/omnipy2/omniORBpy/omniORBpy001.html#toc2 for how to set your PYTHONPATH.  You should be running against the .dlls since you are running on Windows, not the .so files for Unix.  Once you get that working, see the readme.win32 for useful tips on running your project in Visual C++.  While I haven't used pydev, I imagine the setup is similar.

>Thanks,
>Jürgen
>
>pydev debugger
>
>
>omniidl: ERROR!
>
>omniidl: Could not open IDL compiler module
>_omniidlmodule.so
>omniidl: Please make sure it is in directory
>E:\omniORB-4.0.6\lib\python
>omniidl: (or set the PYTHONPATH environment variable)
>
>omniidl: (The error was 'No module named _omniidl')
>
>
>	
>