Hugo Parente Lima wrote:
On Monday 29 March 2010 14:09:56 Josh wrote:
Hi all,
I'm trying to build a binding for my Qt C++ widget using shiboken.
Here's my shiboken command:
shiboken ../data/global.h \
--include-paths=../../VideoPlayerWidget:-I/home/josh/videoWidget/targetfs-
base/include/QtCore:-I/home/josh/videoWidget/targetfs-base/include:/usr/inc
lude
--typesystem-paths=../data:/home/josh/videoWidget/targetfs-base/bindings
--output-directory=.. ../data/typesystem_VideoPlayerWidget.xml
Make fails with the error:
make: *** No rule to make target
`VideoPlayerWidget_globals_wrapper.cpp', needed by `compile'. Stop.
Indeed, there is no "VideoPlayerWidget_globals_wrapper.cpp". Is shiboken
supposed to generate one?
Then, I noticed that it did generate
"videoplayerwidget_module_wrapper.cpp" and "videoplayerwidget_python.h".
However, these names are formatted incorrectly. In the Makefile the
values are camel-capped, ie. they should be:
"VideoPlayerWidget_globals_wrapper.cpp"
"VideoPlayerWidget_module_wrapper.cpp"
"VideoPlayerWidget_wrapper.cpp"
So, is shiboken doing something wrong or have I screwed something up?
The full shiboken output ends with:
...
... ( hundreds of similar warnings snipped out for brevity)
WARNING :: type 'QFrame' is specified in typesystem, but not defined.
This could potentially lead to compilation errors.
WARNING :: type 'QCDEStyle' is specified in typesystem, but not defined.
This could potentially lead to compilation errors.
WARNING :: type 'QGraphicsColorizeEffect' is specified in typesystem,
but not defined. This could potentially lead to compilation errors.
WARNING :: type 'QIconEngine' is specified in typesystem, but not
defined. This could potentially lead to compilation errors.
WARNING :: type 'QGraphicsScene' is specified in typesystem, but not
defined. This could potentially lead to compilation errors.
WARNING :: type 'QItemEditorFactory' is specified in typesystem, but not
defined. This could potentially lead to compilation errors.
WARNING :: type 'QAbstractPageSetupDialog' is specified in typesystem,
but not defined. This could potentially lead to compilation errors.
WARNING :: type 'QLCDNumber' is specified in typesystem, but not
defined. This could potentially lead to compilation errors.
WARNING :: type 'QXmlStreamEntityDeclaration' is specified in
typesystem, but not defined. This could potentially lead to compilation
errors.
WARNING :: type 'QActionGroup' is specified in typesystem, but not
defined. This could potentially lead to compilation errors.
WARNING :: type 'QTextCodec::ConverterState' is specified in typesystem,
but not defined. This could potentially lead to compilation errors.
[-] (1094/1094) Detecting inconsistencies in typesystem for
QTextCodec::ConverterState
Done, 485 warnings (1 known issues)
make: *** No rule to make target
`AwareVideoPlayerWidget_module_wrapper.cpp', needed by `compile'. Stop.
Are you including QtCore and QtGui typesystem in your typesystem file?
Yes. Here's my typesystem file:
<?xml version="1.0"?>
<typesystem package="VideoPlayerWidget">
<load-typesystem name="typesystem_core.xml" generate="no"/>
<load-typesystem name="typesystem_opengl.xml" generate="no"/>
<load-typesystem name="typesystem_gui_common.xml" generate="no"/>
<load-typesystem name="typesystem_gui.xml" generate="no"/>
<object-type name="VideoPlayerWidget"/>
</typesystem>
See the log files generated by ApiExtractor, they can give some clue on what's
wrong.
The only thing out of the ordinary was in mjb_rejected_classes.log
************************************************************************
Type redefined to not be a class
- VideoPlayerWidget
************************************************************************
Is there something wrong with my type system file?
Josh
_______________________________________________
PySide mailing list
[email protected]
http://lists.openbossa.org/listinfo/pyside
