Hi,
I'm running the script below with all Qt headers copied to C:/includes.
I already tried to set the --include-paths to point to
C:/Qt/4.7.2/include but I've got the same result. I'm running it on
Windows 7 with PySide 1.0.1 and Python2.7. I also tried to change the
--include-paths to --include-path. Any ideas? Thanks/Bruno.
generatorrunner.exe \
--generator-set=shiboken \
--debug-level=full \
--no-supress-warnings \
--include-paths=C:/includes \
--typesystem-paths=C:/Users/Tezine/typesystems \
--output-directory=. \
../data/global.h \
../data/typesystem.xml
but now I get the errors:
DEBUG :: Parsed: 'typesystem_templates.xml', 0 new entries
DEBUG :: Parsed: 'typesystem_core.xml', 374 new entries
DEBUG :: Parsed: 'typesystem_gui.xml', 3 new entries
DEBUG :: Parsed: '../data/typesystem.xml', 379 new entries
Detecting inconsistencies in typesystem... [WARNING]
type 'QUrl' is specified in typesystem, but not defined. This could
potentially lead to compilation errors.
type 'QPoint' is specified in typesystem, but not defined. This could
potentially lead to compilation errors.
type 'QXmlStreamEntityDeclaration' is specified in typesystem, but not
defined. This could potentially lead to compilation errors.
type 'QAbstractItemModel' is specified in typesystem, but not defined.
This could potentially lead to compilation errors.
type 'QXmlStreamAttributes' is specified in typesystem, but not defined.
This could potentially lead to compilation errors.
type 'QRectF' is specified in typesystem, but not defined. This could
potentially lead to compilation errors.
type 'QBuffer' is specified in typesystem, but not defined. This could
potentially lead to compilation errors.
type 'QMetaProperty' is specified in typesystem, but not defined. This
could potentially lead to compilation errors.
type 'QFileInfo' is specified in typesystem, but not defined. This could
potentially lead to compilation errors.
type 'QModelIndex' is specified in typesystem, but not defined. This
could potentially lead to compilation errors.
type 'QLine' is specified in typesystem, but not defined. This could
potentially lead to compilation errors.
type 'QAbstractFileEngineHandler' is specified in typesystem, but not
defined. This could potentially lead to compilation errors.
type 'QTextBoundaryFinder' is specified in typesystem, but not defined.
This could potentially lead to compilation errors.
type 'QWaitCondition' is specified in typesystem, but not defined. This
could potentially lead to compilation errors.
type 'QXmlStreamEntityResolver' is specified in typesystem, but not
defined. This could potentially lead to compilation errors.
type 'QTextCodec::ConverterState' is specified in typesystem, but not
defined. This could potentially lead to compilation errors.
type 'QFileSystemWatcher' is specified in typesystem, but not defined.
This could potentially lead to compilation errors.
type 'QMetaObject' is specified in typesystem, but not defined. This
could potentially lead to compilation errors.
type 'QResource' is specified in typesystem, but not defined. This could
potentially lead to compilation errors.
type 'QChildEvent' is specified in typesystem, but not defined. This
could potentially lead to compilation errors.
type 'QLibraryInfo' is specified in typesystem, but not defined. This
could potentially lead to compilation errors.
type 'QSignalMapper' is specified in typesystem, but not defined. This
could potentially lead to compilation errors.
type 'QXmlStreamNamespaceDeclaration' is specified in typesystem, but
not defined. This could potentially lead to compilation errors.
type 'QIODevice' is specified in typesystem, but not defined. This could
potentially lead to compilation errors.
type 'QPluginLoader' is specified in typesystem, but not defined. This
could potentially lead to compilation errors.
type 'QParallelAnimationGroup' is specified in typesystem, but not
defined. This could potentially lead to compilation errors.
type 'QTemporaryFile' is specified in typesystem, but not defined. This
could potentially lead to compilation errors.
type 'QTextEncoder' is specified in typesystem, but not defined. This
could potentially lead to compilation errors.
Em 14/04/2011 06:45PM, Renato Araujo Oliveira Filho escreveu:
This can be problems with you typesystem path, check if you are using
the correct: --typesystem-paths='<path1>;<path2>' in the
generatorrunner command.
You need specify the path where PySide typesystem can be found.
BR
On Thu, Apr 14, 2011 at 6:10 PM, Bruno Tezine<[email protected]> wrote:
Well,
Now I've copied all typesystem xml files from pyside1.0.1 to a folder called
typesystems, than I set the QTTYPESYSTEM to point to it. Now the problem
changed to:
$ ./build.sh
Fatal error: line=3, column=62, message=Failed to parse:
'typesystem_core.xml'
DEBUG :: Parsed: '../data/typesystem.xml', 1 new entries
Cannot parse file: ../data/typesystem.xmlWARNING: Failure to find:
pyhybrid/pyhybrid_module_wrapper.cpp
WARNING: Failure to find: pyhybrid/mainwindow_wrapper.cpp
Makefile:121: *** multiple target patterns. Stop.
Any ideas? I'm using Visual Studio 2010. ApiExtractor, Shiboken,
GeneratorRunner are all compiled with it.
Thanks/Bruno.
Em 13/04/2011 11:41AM, Bruno Tezine escreveu:
Hi, I tried to run the build.sh from the tutorial you said, but it fails
with the message below: How can I create the Qt typesystem? Is this why I’m
getting these errors?
I already compiled the generatorrunner, apiextractor and shiboken.
Thanks again./Bruno.
$ ./build.sh
Fatal error: line=3, column=62, message=Failed to parse:
‘typesystem_core.xml’
Cannot parse file: ../data/typesystem.xmlWARNING: Failure to find:
pyhybrid/pyhybrid_module_wrapper.cpp
WARNING: Failure to find: pyhybrid/mainwindow_wrapper.cpp
Makefile:121: *** multiple target patterns. Stop.
Em 08/04/2011 10:52PM, Renato Araujo Oliveira Filho escreveu:
Check this tutorial, I think this can be helpful to you:
http://lynxline.com/superhybrids-part-2-now-qt-pyside/
BR
On Fri, Apr 8, 2011 at 7:21 PM, Bruno Tezine<[email protected]> wrote:
Hi,
I'm a newbie in Python. Does anybody know if it's possible to load a
PySide
script from a C++ Qt application(not lib) and use a C++ widget as
"parent
widget" for the PySide script? That's because I'd like allow users to
create
PySide scripts as "plugins" for my application.
I know I can access C++ from Python using Shiboken, but I didn't see the
opposite.
Any ideas?
Thanks/Bruno.
_______________________________________________
PySide mailing list
[email protected]
http://lists.pyside.org/listinfo/pyside
_______________________________________________
PySide mailing list
[email protected]
http://lists.pyside.org/listinfo/pyside
