Use loadFromModule, instead of load, as it's the simpler and newer API.
That requires renaming main.qml to Main.qml, and some changes to the
CMakeLists.txt file. That gets rid of a runtime warning about using
relative URLs.
Moreover, avoid adding an import path we don't need, and remove the
error handling for the case where loading fails – we know it can't fail.
Pick-to: 6.10
Fixes: QTBUG-138177
Change-Id: I01a3eac70147bf5aef6456be0b634af933daae20
Reviewed-by: Olivier De Cannière <olivier.decanniere@qt.io>
We can avoid confusion in qmllint by explicitly specifying that the
content module depends on RobotArm (using the target based dependency
API).
At runtime this happens to work because the application rearranges the
modules in the import path, but that's a runtime setting.
Pick-to: 6.10
Task-number: QTBUG-138176
Change-Id: I91e1a4142a691d70784380ef0de42fc198eaa3f7
Reviewed-by: Olivier De Cannière <olivier.decanniere@qt.io>
Projects need install instructions to be usable on embedded platforms.
Fix existing instructions to put files into correct places.
Fixes: QTBUG-112024
Pick-to: 6.7
Change-Id: I6a3d84edc1c67281d5497e99144c159faf0f783c
Reviewed-by: Alexey Edelev <alexey.edelev@qt.io>
Reviewed-by: Kimmo Ollila <kimmo.ollila@qt.io>
Both robotarm, and todolist examples were creating `content` target
which was breaking the build if both examples were activated.
Pick-to: 6.6
Change-Id: I0922765526f2fca861c16b1ced4f1c040c104adc
Reviewed-by: Jonas Karlsson <jonas.karlsson@qt.io>
Fabian Kosmale
Samuli Piippo
Amir Masoud Abdol
Kimmo Leppälä