[PyKDE] New PyKDE snapshot

[Detlev Offenbach]

Hi,

I tried to download the new PyKDE snapshot from Riverbank, but the link points 
to nowhere (404 error).

Detlev

Am Freitag 14 Oktober 2005 06:31 schrieb Jim Bublitz:
> I'm in the process of sending the latest PyKDE snapshot to Phil for posting
> on at http://www.riverbankcomputing.co.uk/snapshots/PyKDE. It's
> snapshot20051013. It should be available within 24 to 48 hours.
>
> The changes are:
>
> Cleaned up sip files for gcc 3.4.x/4.0.x compatibility
> ================================
>
> This should allow people using gcc 3.4.x or 4.0.x to compile and load PyKDE
> - the unresolved symbol problems should be fixed (except see below)
>
> Replaced sipNewCppToSelf instances with sipBuildResult
> Updated configure.py to use pyqtconfig.py for Qt environment info
> ========================================
>
> These are for sip compatibility - PyKDE should now build with both previous
> and current (snapshot) versions of sip and PyQt.
>
> Dropped kdesu (undefined symbol problem)
> Added -fno-rtti to kdeprint compile
> Dropped driver.sip from kdeprint
> Backed out konsolepart code (undefined symbol problem)
> ===================================
>
> These are problems I ran into on SuSE 10. driver.sip was part of the gcc
> compatibility problem. kdesu and konsolepart have problems with unresolved
> symbols (at least with the SuSE 10 libs, but I suspect other libs as well).
> konsolepart was added by request this past summer, but there are
> fundamental problems resolving symbols. After fixing a few, I still got
> someClass::className() undefined errors for QObject derived classes -
> there's no way to prevent sip from generating this based on inheritance
> (and probably shouldn't be). It appears that KDE compile settings are
> optimizing out some symbols, which sip can't do.
>
> The same holds for kdesu, but I had an additional problem there where the
> kdesu.so lib was picking up a symbol from the h file that wasn't in the
> sip-generated files, and this symbol didn't exist in KDE's libkdesu. That
> might be fixable, but in the little stuff I've tried with kdesu, it didn't
> work very well from PyKDE, and I doubt it's in wide use. If someone really
> has an application for kdesu, let me know and I'll put some work into it.
> Otherwise, I'll probably drop the module entirely.
>
> -------------------------------
>
> I still have a number of bug fixes from the mailing list to incorporate,
> but I'd appreciate some feedback on problems compiling against gcc 3.4.x
> and 4.0.x as soon as possible. This version will compile against KDE 3.4.2,
> but doesn't incorporate changes later than 3.4.1. I'll include 3.4.2 and
> 3.5 changes in the final release.
>
> I'll be out of town all day tomorrow (Friday here), but will be back online
> Saturday AM.
>
> Jim
>
> _______________________________________________
> PyKDE mailing list    PyKDE at mats.imk.fraunhofer.de
> http://mats.imk.fraunhofer.de/mailman/listinfo/pykde

-- 
Detlev Offenbach
detlev at die-offenbachs.de