[omniORB] BuildDebugBinary (Win32 MSVC) for omniORB4?

[Lars Immisch]

Duncan Grisby:
> On Wednesday 15 August, Ken Feuerman wrote:
>
> > Has anybody tried building omniORB4 on a Win2K platform (MSVC 6.0) with
> > BuildDebugBinary = 1?
>
> Probably not, no.
>
> BuildDebugBinary only applies to .exe files -- i.e. things like
> omniNames and catior. I'm pretty certain that the debug versions of
> the DLLs do have full debugging symbols in them. They're certainly big
> enough. If they don't, it can be fixed by changing
> MSVC_DLL_CXXDEBUGFLAGS and friends in mk/win32.mk.

Yes, they do contain debug information.

> The reason omniidl fails with BuildDebugBinary is that omniidl.exe is
> linked against a non-debug python15.dll. I think the full Python
> installation includes a debug version of the Python dll, so modifying
> the omniidl make rules to use that (when BuildDebugBinary is on)
> should fix it.

Ahhh. Thanks.

But as Duncan said above, it's not necessary if you want to trace into omniORB  
code linked to your application (which seems the most common use).

- Lars