[omniORB] RE: omnipy debug builds on windows

Tue Dec 3 18:57:01 2002

This is a multi-part message in MIME format.

------_=_NextPart_001_01C29AFD.A368EFE8
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Oops, I forgot that the _DEBUG symbol also needs to be defined for debug
builds.

		-----Original Message-----
		From: Kevin Wooten=20
		Sent: Tuesday, December 03, 2002 11:53 AM
		To: omniorb-list@omniorb-support.com
		Subject: omnipy debug builds on windows

		Duncan,
		Could you possibly add a change to the make files for
windows that builds a debug version of "_omnipy" named "_omnipy_d" and
links with "python$(ver)_d.lib", when BuildDebugBinary is defined. When
running a debug version of Python on windows it needs to be linked this
way and all the module names must end in "_d", as the import statement
maps them that way (i.e. "import _omnipy" will only import "_omnipy_d"
in debug builds). I do it manually now but it would be nice to have both
versions built automatically when BuildDebugBinary is turned on.

		Thanks,
		Kevin

------_=_NextPart_001_01C29AFD.A368EFE8
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.6249.1">
<TITLE>RE: omnipy debug builds on windows</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial">Oops, I forgot that the _DEBUG symbol also needs to be =
defined for debug builds.</FONT></SPAN></P>
<BR>
<UL><UL>
<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma">-----Original Message-----<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">From:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Kevin Wooten<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Sent:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> Tuesday, December 03, =
2002 11:53 AM<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">To:</FONT></B></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Tahoma"> =
omniorb-list@omniorb-support.com<BR>
</FONT></SPAN><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Tahoma">Subject:</FONT></B></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Tahoma"> omnipy debug builds on windows</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Duncan,</FONT></SPAN></P>

Could =
you possibly add a change to the make files for windows that builds a =
debug version of &#8220;_omnipy&#8221; named &#8220;_omnipy_d&#8221; and =
links with &#8220;python$(ver)_d.lib&#8221;, when BuildDebugBinary is =
defined. When running a debug version of Python on windows it needs to =
be linked this way and all the module names must end in =
&#8220;_d&#8221;, as the import statement maps them that way (i.e. =
&#8220;import _omnipy&#8221; will =
only import &#8220;_omnipy_d&#8221; in debug builds). I do it manually now but it would be =
nice to have both versions built automatically when BuildDebugBinary is =
turned on.

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Thanks,</FONT></SPAN></P>

<P ALIGN=3DLEFT><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Kevin</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>
</UL></UL>
</BODY>
</HTML>
------_=_NextPart_001_01C29AFD.A368EFE8--