<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2657.42">
<TITLE>RE: [PyKDE] Building PyQt as 1 shared library</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>I'm curious why you see static in the python library as an advantage?</FONT>
</P>
<BR>
<P><FONT SIZE=2>> -----Original Message-----</FONT>
<BR><FONT SIZE=2>> From: Phil Thompson [<A HREF="mailto:phil@riverbankcomputing.co.uk">mailto:phil@riverbankcomputing.co.uk</A>] </FONT>
<BR><FONT SIZE=2>> Sent: Thursday, November 06, 2003 9:19 AM</FONT>
<BR><FONT SIZE=2>> To: Peter Kropf; 'phil@riverbankcomputing.co.uk'; </FONT>
<BR><FONT SIZE=2>> pykde@mats.imk.fraunhofer.de</FONT>
<BR><FONT SIZE=2>> Subject: Re: [PyKDE] Building PyQt as 1 shared library</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> On Thursday 06 November 2003 4:58 pm, Peter Kropf wrote:</FONT>
<BR><FONT SIZE=2>> > To start, merging qttable into qt was fairly easy. I modified </FONT>
<BR><FONT SIZE=2>> > qtmod.sip, adding %Include qtable.sip. Then rebuilding PyQt </FONT>
<BR><FONT SIZE=2>> resulted </FONT>
<BR><FONT SIZE=2>> > in the qtable code being included and accessable from </FONT>
<BR><FONT SIZE=2>> python. Instead </FONT>
<BR><FONT SIZE=2>> > of:</FONT>
<BR><FONT SIZE=2>> ></FONT>
<BR><FONT SIZE=2>> > from qttable import QTable</FONT>
<BR><FONT SIZE=2>> ></FONT>
<BR><FONT SIZE=2>> > the python code now reads:</FONT>
<BR><FONT SIZE=2>> ></FONT>
<BR><FONT SIZE=2>> > from qt import QTable</FONT>
<BR><FONT SIZE=2>> ></FONT>
<BR><FONT SIZE=2>> > As to why I want to do this, it has to do with deployment issues on </FONT>
<BR><FONT SIZE=2>> > Solaris. (See my posting from yesterday titled "qttable and </FONT>
<BR><FONT SIZE=2>> installer </FONT>
<BR><FONT SIZE=2>> > confusion on windows and solaris" for details.) We're using Gordon </FONT>
<BR><FONT SIZE=2>> > McMillan's Installer (which is a great tool) to create </FONT>
<BR><FONT SIZE=2>> executables for </FONT>
<BR><FONT SIZE=2>> > distribution. All is well when running in the development </FONT>
<BR><FONT SIZE=2>> environment </FONT>
<BR><FONT SIZE=2>> > (Windows and Solaris) and in the Windows distribution. But </FONT>
<BR><FONT SIZE=2>> on Solaris </FONT>
<BR><FONT SIZE=2>> > we have runtime issues. I've been able to trace the problem back to </FONT>
<BR><FONT SIZE=2>> > the fact that qt and qtable are two seperate shared libraries. Why </FONT>
<BR><FONT SIZE=2>> > that matters, I don't know yet and it's very frustrating. </FONT>
<BR><FONT SIZE=2>> However by </FONT>
<BR><FONT SIZE=2>> > building qtable into the qt shared library, I'm able to create a </FONT>
<BR><FONT SIZE=2>> > distribution package on Solaris that works.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> I would have thought a better solution would be to statically </FONT>
<BR><FONT SIZE=2>> link them into </FONT>
<BR><FONT SIZE=2>> the interpreter so that they become builtin modules.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Phil</FONT>
<BR><FONT SIZE=2>> </FONT>
</P>
</BODY>
</HTML>