[Qt-qml] How plugin paths should work
Matthias Ettrich
matthias.ettrich at nokia.com
Mon Aug 9 15:14:57 CEST 2010
On Monday 09 August 2010 10:09:34 ext Jyrki Hämäläinen wrote:
>
> Thanks Matthias,
Your welcome.
[...]
>
> The problem (as I understand it and the actual technical background may be
> somewhat different) was that we tried to use pluginpath to tell where
> plugins are located and then force QT to load the plugins by declaring the
> existence of them in the qmldir-files in the modules that use the plugin.
> This led QT to believe that the plugin should be initialized under wrong
> modules "namespace" and moreover under multiple modules "namespaces". This
> again confused parser for some reason.
> Funny thing in here is that the parser does not seem to get confused, if
> each module actually contains a separate copy of the plugin file. Not that
> it really matters, as it is obviously a very wrong way to use such a
> plugin.
Did you use a release build? in qdeclearativeimport.cpp, line 894 I find a
Q_ASSERT_X for exactly that case with
"Internal error: Plugin imported previously with different uri".
This is not good. If we ignore the 2nd import, we need to give a warning a
least. Or shall we simply accept the 2nd import?
Matthias
More information about the Qt-qml
mailing list