[prev in list] [next in list] [prev in thread] [next in thread]
List: pykde
Subject: [PyKDE] python/qt "slots" clash
From: "Patrick Stinson" <patrickkidd.lists () gmail ! com>
Date: 2007-01-10 22:37:00
Message-ID: 664bf2b80701101436o72726c65jb56b06e053ea53d () mail ! gmail ! com
[Download RAW message or body]
There is a clash with the "slots" definition in (at least) python2.3
and the qt definition of "slots." Apparently this bug has been fixed
in a later version of python, but I would like to avoid an upgrade at
this point.
The problem is solvable if you
#undef slots
before including any qt headers in your C++ code. I have embedded the
python interpreter into my application, and included a bunch of sip
files to access my data structures from within my C++ executable.
My problem is that I am using precompiled headers and I include sip.h
then QtCore and QtGui, like this:
#include <sip.h>
#undef slots
#include <QtGui>
#include <QtCore>
...so slots gets redefined by the qt headers. when my sip*.cpp files
are compiled they include sip.h *then* my ModuleHeaderCode, and I get
the clash again. I am confused because sip.h should not be included
twice, so how is the clash comin back if the order is fixed in the
pch?
Here is the related python bug report:
http://www.google.com/url?sa=t&ct=res&cd=1&url=http%3A%2F%2Fmail.python.org%2Fpipermai \
l%2Fpython-bugs-list%2F2005-September%2F030473.html&ei=gmqlRYvGHaaygwPmk_j3CQ&usg=__hJynaNrnzniof4fKXQdZHJxA5N4=&sig2=9B34igyhUw06q8BU6HjrNw
--
Patrick Kidd Stinson
http://www.patrickkidd.com/
http://pkaudio.sourceforge.net/
http://pksampler.sourceforge.net/
_______________________________________________
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]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic