[omniORB] BuildDebugBinary (Win32 MSVC) for omniORB4?

[Frédéric Bouvier]

I have the same problem here and I found that (in mk/win32.mk) shared debug
DLL are
built unconditionally with MSVC_DLL_CXXLINKNODEBUGOPTIONS options.
I changed temporarily line 311 of win32.mk to

$(CXXLINK) -out:$$dllname -DLL $(MSVC_DLL_CXXLINKDEBUGOPTIONS) \

rebuild the shared library (obj files are ok) and I now have debug symbols
in
omniORB400_rtd.dll.

Of course, a rule that depends on the 'debug' variable would be better but I
am not
enough acquainted with GNU make to make the change.

Hope that helps,

-Fred

----- Original Message -----
From: "Ken Feuerman" <kfeuerma@adobe.com>
To: "Lars Immisch" <lars@ibp.de>
Cc: <omniorb-list@uk.research.att.com>
Sent: Monday, August 20, 2001 6:54 PM
Subject: Re: [omniORB] BuildDebugBinary (Win32 MSVC) for omniORB4?


> Tracing into the omniORB code is indeed what I want to do, but it seems
> that the DLL's don't actually contain debug information, even though the
> various object files do.  I think the problem is that the DLL's are linked
> without the /debug option set (see the log below for an example of how
> omnithread30_rtd.dll was built).  I've been playing around with the
> win32.mk file, but I can't seem to get the options right so that
> omnithread30_rtd.dll is built with /debug flags, and omnithread30_rt.dll
is
> built without /debug flags.  Any suggestions there?
>
> --Ken Feuerman.
> Adobe Systems, Inc.