Re: [review] [PyKDE] PyQT module size

2005-03-04 Thread Phil Thompson
I think I'm just going to go with the other users' recommendation of nabbing the latest sip and compiling with some different flags with GCC4 and see if that gets me some quick wins. My mind is too small and fragile to attempt the changes you proposed above without screwing things up or

[PyKDE] Compiling sip 4.1.1, PyQt 3.13, PyKDE 3.11.3 on Solaris 8micro-Howto

2005-03-04 Thread Holger Joukl
As promised, a more detailed description of a successful sip/pyqt/pykde build on Solaris 8, using gcc 2.95.2. As this became rather lengthy I will quick-start with a summary of what worked for me. Find the details afterwards. Thanks to everybody for hints information. SIP/pyqt/pykde are great

Re: [PyKDE] Compiling sip 4.1.1, PyQt 3.13, PyKDE 3.11.3 on Solaris 8micro-Howto

2005-03-04 Thread Jim Bublitz
On Friday 04 March 2005 05:01, Holger Joukl wrote: PyKDE-3.11.3: - 1. Apply a patch to PyKDE I found on the mailing list which adds support for KDE 3.3.2 (by using the 3.3.0 stuff): for i in `find | grep kde330 | grep diff`; do echo $i mv -f $i `echo $i |

[PyKDE] PyKDE Snapshot

2005-03-04 Thread Phil Thompson
Jim's latest PyKDE snapshot has now been uploaded to the snapshots directory. Apologies for the delay. Phil ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde

[PyKDE] Good news/Bad news

2005-03-04 Thread Jim Bublitz
The bad news is I made a dumb mistake when regenerating PyKDE for KDE 3.4.0. In the project file, I set the previous version number equal to the new version number, so no new stuff showed up. It looked like an error in the way enums were versioned, so I set off debugging that, and found the