Qt 5.2 beta 1 / iOS / QtQuick 1.1 and 2.0

[timday]

For what it's worth, I just ran into this problem out of the blue (despite having previously had QML stuff working on the iPad simulator) after I nuked a build area. (On MacOS 10.8 using the Qt5.2.1 for ios).

One thing which had changed in the development area's history: I'd moved the qml files into a subdirectory (relative to the .pro file).

I just followed dbrian's advice and created a near identical imports.qml adjacent to the .pro... and ta-da... back in action again.

[dbrian]

Another FWIW: The 'imports.qml' file I mentioned above doesn't seem to be necessary anymore in Qt 5.3. Maybe the build system is now searching deeper in the project hierarchy for import statements.

[KH-219Design]

@dbrian said in Qt 5.2 beta 1 / iOS / QtQuick 1.1 and 2.0:

Create a .qml file in the same directory as your .pro file where you declare any qml imports your application requires

Amazing. It is now 2020 (7 years have passed), and this "imports.qml" trick still solved my iOS/qmake issue today. Thanks, from the future ;)