<div dir="ltr">Ian,<div><br></div><div>This setting of QML2_IMPORT_PATH is needed only when installing qml stuff into a different place than qt itself. So yes it's likely to be a similar issue to the QStandardPaths issue unfortunately.</div><div><br></div><div>BR,</div><div>Jeremy</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Dec 30, 2014 at 6:51 PM, Ian Wadham <span dir="ltr"><<a href="mailto:iandw.au@gmail.com" target="_blank">iandw.au@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Jeremy,<br>
<span class=""><br>
On 30/12/2014, at 1:40 AM, Jeremy Whiting wrote:<br>
> It's likely that you haven't set QML2_IMPORT_PATH=/usr/local/lib/qml in your<br>
> environment, Without this set it will only look next to the qt installation itself<br>
> for qml data.<br>
<br>
</span>Could this become a problem again when porting QML-based apps to MacPorts<br>
and Apple OS X?  Environment variables are not so welcome there when starting<br>
apps from the OS X GUI.<br>
<br>
Cheers, Ian W.<br>
<div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
kde-games-devel mailing list<br>
<a href="mailto:kde-games-devel@kde.org">kde-games-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kde-games-devel" target="_blank">https://mail.kde.org/mailman/listinfo/kde-games-devel</a><br>
</div></div></blockquote></div><br></div>