<!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>To start, merging qttable into qt was fairly easy. I modified qtmod.sip, adding %Include qtable.sip. Then rebuilding PyQt resulted in the qtable code being included and accessable from python. Instead of:</FONT></P>
<P><FONT SIZE=2> from qttable import QTable </FONT>
</P>
<P><FONT SIZE=2>the python code now reads:</FONT>
</P>
<P><FONT SIZE=2> from qt import QTable</FONT>
</P>
<P><FONT SIZE=2>As to why I want to do this, it has to do with deployment issues on Solaris. (See my posting from yesterday titled "qttable and installer confusion on windows and solaris" for details.) We're using Gordon McMillan's Installer (which is a great tool) to create executables for distribution. All is well when running in the development environment (Windows and Solaris) and in the Windows distribution. But on Solaris we have runtime issues. I've been able to trace the problem back to the fact that qt and qtable are two seperate shared libraries. Why that matters, I don't know yet and it's very frustrating. However by building qtable into the qt shared library, I'm able to create a distribution package on Solaris that works.</FONT></P>
<P><FONT SIZE=2>- Peter</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 12:52 AM</FONT>
<BR><FONT SIZE=2>> To: Peter Kropf; 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 Wednesday 05 November 2003 10:57 pm, Peter Kropf wrote:</FONT>
<BR><FONT SIZE=2>> > Does anyone know if it's possible to build PyQt so that </FONT>
<BR><FONT SIZE=2>> there is one </FONT>
<BR><FONT SIZE=2>> > shared library that contains all the code instead of the 8 </FONT>
<BR><FONT SIZE=2>> > (libqtcanvascmodule.so, libqtcmodule.so, libqtextcmodule.so, </FONT>
<BR><FONT SIZE=2>> > libqtnetworkcmodule.so, libqtsqlcmodule.so, libqttablecmodule.so, </FONT>
<BR><FONT SIZE=2>> > libqtuicmodule.so,</FONT>
<BR><FONT SIZE=2>> > libqtxmlcmodule.so) as there are today?</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Building it as a single shared library shouldn't be too </FONT>
<BR><FONT SIZE=2>> difficult. The problem </FONT>
<BR><FONT SIZE=2>> is that I'm not sure Python can deal with several modules </FONT>
<BR><FONT SIZE=2>> being defined in a </FONT>
<BR><FONT SIZE=2>> single library as it uses the module name to load the </FONT>
<BR><FONT SIZE=2>> extension and to call </FONT>
<BR><FONT SIZE=2>> the initialisation function.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Why would you want to do this?</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Phil</FONT>
<BR><FONT SIZE=2>> </FONT>
</P>
</BODY>
</HTML>