<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<style>
<!--
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:Arial;
color:windowtext;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>It would be really nice if (at least on windows) that the –u
flag of configure.py produced final targets with ‘_d’ appended to
the name. My troubles on win32 were almost exclusively due to this. When Python
is compiled for debugging, it looks as if it tries to load other modules built
for debugging, so it actually tries to import “qt_d” instead of “qt”.
I was only ever able to get it to work when everything was compiled without
debug, and I think this was the main issue.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>This would also make it much easier for me to switch between
the release and debug versions.<o:p></o:p></span></font></p>
</div>
</body>
</html>
<table><tr><td bgcolor=#ffffff><font color=#000000>__________________________________________________________________________________________<br>
This electronic message may contain proprietary and confidential information of Verint Systems Inc., its affiliates and/or subsidiaries.<br>
The information is intended to be for the use of the individual(s) or<br>
entity(ies) named above. If you are not the intended recipient (or authorized to receive this e-mail for the intended recipient), you may not use, copy, disclose or distribute to anyone this message or any information contained in this message. If you have received this electronic message in error, please notify us by replying to this e-mail. (1)<br>
</font></td></tr></table>