On quinta-feira, 1 de novembro de 2012 11.39.22, Chris Adams wrote: > You're right. > Ok, all in all, I think having separate import install paths and separate > envvars to define the import path basedir at runtime is the best solution > after all.
Thanks. That makes my life easier because there's no need to patch further. The only variable I've renamed so far was QML_PLUGIN_PATH. I'm still waiting for the final decision on the tooling. The current suggestions are: qml1viewer (from qmlviewer) qml2viewer (from qmlscene) qml1plugindump qml2plugindump (from qmlplugindump) All the rest is unchanged. Please note that we *can* have qmlviewer, provided it's the Qt Quick 1. It works in either scenario of tooling: if it's in $PATH, it's via the toolwrapper, in which case you run the Qt 5 version by adding the -qt5 option. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
