> -----Original Message----- > From: qt-qml-bounces+kai.koehne=nokia....@qt.nokia.com [mailto:qt- > qml-bounces+kai.koehne=nokia....@qt.nokia.com] On Behalf Of ext André > de Castilho > Sent: Sunday, January 22, 2012 3:00 PM > To: qt-qml@qt.nokia.com > Subject: Re: [Qt-qml] QtCreator error (QML Module not Found) when > including QtDesktop 0.1 > > Thank you guys for the answers!
Hi Andre, Seems you managed to run into a lot of bugs at once :) > As I was using the QtSDK, had Qt 4.7.4 and it doesn't come with the > qmlplugindump binary, so I had to compile it. To do that, I needed the private > libraries, so I uninstalled the SDK, got Qt 4.8.0 source, built it, downloaded > the QtCreator 2.4.0, installed it, and finally ran the plugin. > > For starters, if I open a single .qml file, it stil didn't recognize the > module, but > when I created a qmlproject, it recognized it (and I didn't have to add any > special config to the project). This is to be expected. Qt Creator needs the notion of a 'project' to guess which Qt version and environment you'd like to use. A .qmlproject is the most lightweight way to get one ... > I was happy, but not for long: > > When I import the QtDesktop module and open the Design window, > QtCreator crashes with a segmentation fault. If I take away the "import > QtDesktop 0.1" line, it opens correctly. The Qt Quick Designer in Qt Creator is kind of a beast. It comes down to that both the component set and the Quick Designer have to have explicit support : The component set might be used in ways not expected in normal use (like setting some bindings multiple times, unsetting them ...), while Qt Quick Designer has to know how to graphically manipulate items. So your mileage may vary, but the Qt Desktop components are not officially supported right now. Anyhow, Qt Creator shouldn't crash, since the loading of the component set is now done in a separate process. Feel therefore free to file a bug at bugreports.qt.nokia.com. > I ran the qtcreator.sh plugin on a terminal to catch the log. > > When I open the design, it doesn't matter if I have the import QtDesktop line > or not, I get this: > > > > > /usr/share/mime/application/x-executable.xml:1: parser error : > Document is empty > ^ > /usr/share/mime/application/xml.xml:1: parser error : Document is > empty > ^ > /usr/share/mime/application/x-executable.xml:1: parser error : > Document is empty > ^ > /usr/share/mime/application/x-executable.xml:1: parser error : > Document is empty > ^ > /usr/share/mime/application/x-shellscript.xml:1: parser error : > Document is empty > ^ > /usr/share/mime/application/x-shellscript.xml:1: parser error : > Document is empty > ^ > /usr/share/mime/application/x-desktop.xml:1: parser error : > Document is empty > ^ > /usr/share/mime/application/x-executable.xml:1: parser error : > Document is empty > ^ > /usr/share/mime/application/x-executable.xml:1: parser error : > Document is empty > ^ > /usr/share/mime/application/x-executable.xml:1: parser error : > Document is empty > ^ > /usr/share/mime/application/x-executable.xml:1: parser error : > Document is empty > ^ > /home/andre/.local/share/mime/application/vnd.nokia.qt.qmakepr > ofile.xml:1: parser error : Document is empty I don't know where the parser errors come from, sorry. But I guess they're independent from Qt / Qt SDK / Qt Creator. > ^ > QmlDesigner: Log file is: "/tmp/qmldesigner-logger-2012-01-22T11- > 51-50-ZT2866.txt" > > > > When I insert the import QtDesktop 0.1 line, after the xml parser errors, the > program crashes with segmentation fault. > > I don't know how to trace the bug, or turn the debug messages on, and > would appreciate any help pointing me in the right direction or telling me > what I am doing wrong. The only additional hint I can give you is that the qt-creator@ is probably a better place to ask for the Qt Creator / Designer specific problems. Regards Kai > Thank you one more time, > > > André de Castilho > > > 2012/1/20 Sven Anderson <sven.ander...@snom.com>: > > > > > > On 20.01.2012 03:41, Alan Alpert wrote: > >> It can work with it, but does not by default. When using your own QML > >> plugins with creator theres an extra step you have to perform to make > >> it known to creator. I forget exactly what this step is, but it > >> involves running the qmlplugindump utility and placing the output > somewhere creator can find it. > >> For Qt Creator to recognize a module, it needs this metadata, which > >> is why modules can be unknown to creator but loaded properly in > qmlviewer. > > > > Here are the details: > > > > http://doc.qt.nokia.com/qtcreator-2.4/creator-qml-modules-with-plugins > > .html > > > > > > Best regards, > > > > Sven > > _______________________________________________ > > Qt-qml mailing list > > Qt-qml@qt.nokia.com > > http://lists.qt.nokia.com/mailman/listinfo/qt-qml > _______________________________________________ Qt-qml mailing list Qt-qml@qt.nokia.com http://lists.qt.nokia.com/mailman/listinfo/qt-qml
