[omniORB] omniORBpy and visual studio 7
Luke Deller
ldeller at xplantechnology.com
Sun Aug 1 23:04:49 BST 2004
Jan Olderdissen wrote:
> We decided to build a new C++/CORBA project in vs7. I had to compile
> omniORB-4.0.3 against vs7 because the runtime DLL has incompatible memory
> allocators. While it was somewhat tricky to figure out the build process,
> the result seems to work fine.
>
> The system will be used from a Python client. Running the binary
> distribution of _omnipy.pyd against the omniORB403_rt.dll compiled for vs7
> failed, so I decided to compile omniORBpy-2.3 against vs7 as well. Sadly,
> the result is flaky. Every once in a while the most basic invocations crash
> with "The instruction at '0x77fcda2f' referenced memory at '0x0000002c'. The
> memory could not be 'read'."
>
> The debugger points to a problem when freeing memory in msvcr71.dll.
>
> I checked that both the servant and the python client use the same
> omniORB403_rt.dll and omnithread30_rt.dll.
>
> The only potential problem that comes to mind is that python23.dll is _not_
> compiled against vs7.
Yes, you will need to rebuild Python 2.3.x using the newer version of
visual c++. I got this to work using Visual Studio .NET 2003 (vc7.1).
I installed the regular Python binary package into C:\Python23, then
built Python from source using vc7.1, then copied all the binaries
(*.dll *.pyd *.lib) from the source build into the relevant subfolder of
C:\Python23
Happily, I believe that the upcoming binary releases of Python 2.4 will
be compiled with vc7.x so you should be able to use these without
recompiling Python.
Regards,
Luke.
More information about the omniORB-list
mailing list