[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pykde
Subject:    Re: [PyKDE] SIP with debug Qt
From:       Phil Thompson <phil () riverbankcomputing ! co ! uk>
Date:       2005-04-02 9:18:03
Message-ID: 200504021018.03342.phil () riverbankcomputing ! co ! uk
[Download RAW message or body]

On Friday 01 April 2005 11:49 pm, James Emerton wrote:
> In the interest of not having two different Qt source trees, I
> perpetrate small hack that creates qt-mtNNNd.dll as the debug version.
> (I do this by building normally to get a release build, then rerunning
> configure with -debug -lean -no-qmake and manually tweaking TARGET in
> the generated Makefile.)  This approach has worked wonderfully for me.
>
> Problem is, sipconfig is not aware of my creative renaming.  All my
> generated wrappers were linking to the non-debug qt.  (This causes an
> app compiled with -MDd to have a different heap, and bad things
> happen!)
>
> So I've hacked sipconfig to link to the correct library, but I can't
> really share this because currently it would break anywhere someone
> hasn't built Qt this way.  The strange thing is, I didn't have to do
> this to PyQt itself.  qt_d.pyd correctly links to qt-mt334d.dll!  I
> couldn't find this magic in the PyQt sources -- but I don't know where
> to look and I haven't been able to spend a lot of time on it yet.
>
> Is it possible to add this capability to sipconfig?

Not for something as non-standard as this. I don't see the problem in having 
separate Qt (and Python) debug/release source trees.

Phil

_______________________________________________
PyKDE mailing list    PyKDE@mats.imk.fraunhofer.de
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
[prev in list] [next in list] [prev in thread] [next in thread]