On 22.02.06 20:35:40, Dave Williams wrote: > On Wed, 22 Feb 2006 20:41:19 +0100 > Andreas Pakulat <[EMAIL PROTECTED]> wrote: > > > BTW: You don't need those 'old' snapshots, PyQt was fixed 1 or 2 days > > after I sent you those files. > > > OK but it was good to get something working at least rather than chase more > moving targets!
I don't find chasing PyQt too hard. I normally check the Snapshots dir every 2 or 3 days and look into the Changelog. If the changes are substantial or interesting or I need them I download and build. This takes less than 30 minutes. If you need longer I'd suggest to use the "-c" Option together with "-j 4" or something like that. It'll speed up Compilation _a lot_. Though I found out that PyQt3 at least on my machine needs debugging symbols enabled to not make the System unusable due to heavy memory usage. It's not that extreme with PyQt4. Also using to few "parts" can increase memory usage to an amount where your kernel kills all running apps (including the gcc). > > > b) The need to explicitly use the -g option because > > > /usr/include/qt3/qconfig.h contains > > Huh??? Probably this is related to the above. Here QTDIR for qt3 is > > /usr/share/qt3, you can find "include", "share", "bin", "lib" and so on > > there. At least here on Debian. > > Doesnt appear to be related. My QTDIR points to /usr/lib/qt3 (which is > Mandriva decided to put it) Yeah heard of that. Debian puts it into /usr/share and provides include and lib and doc via symlinks. The bin-dir is a real dir, but with a couple of symlinks to the real files in /usr/bin in it. Also Debian renames the tools to <tool>-qt3 and provides a system to easily choose between qt4 or qt3 as "default". > and, as you would expect, there are the dir's you mention (alhough not > share). I still get the same problem. Would be interesting to know > what your include/qconfig.h has in it. No MULTIARCH_HEADER here, I can only guess that this is something mandriva changed (to the worse maybe). However I have no idea what this could do and whether it's in Qt3's source, as I don't have a copy of that lying around. > > Does Mandriva not deliver QScintilla? You can tell PyQt3's configure.py > > where QScintilla headers and libs are installed, so you don't need to > > install it into /usr/local, /usr or anywhere you might not have > > sufficient rights to write to. > > Yes they do albeit they are always some time behind the cutting edge. Ideally > I would have done a 100% source code install for all components so I knew > where everything came from and could update if/when required. QT was the > exception because it was installed already and was going to break rather too > many RPM dependencies to remove it and reinstall from source. Overwriting an > RPM install is asking for trouble. Yeah overwriting is not good. But installing into $HOME is not good either, at least the style-problem I had (PyQt3 built against $HOME/qt3 had no styles available) came from that... Anyway installing Qt4 into $HOME and Python+PyQt(3|4) into $HOME still works perfectly. > Yes Same problem and yes -q fixes it! Mandriva leaves QTDIR defined but I > agree you dont need it. I'd really be surprised if you wouldn't agree, as that is what TT themselves say: Qt4 doesn't consider the QTDIR environment variable anymore. All paths are put into the Makefiles by qmake. > Sorry if I almost gave you heart failure!! Not really :-) Andreas -- You like to form new friendships and make new acquaintances. _______________________________________________ PyKDE mailing list [email protected] http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
