How to resolve Sailfish.Silica import error after Sailfish SDK update
After the update of the Sailfish SDK I get an error for the Sailfish.Silica import. It says, that the QML module was not foiund. I think I have to adjust the import path. Where and how? I have originally used the SDK's templage for my app project. If I create a new project with the SDK, the import error is not shown.
Adjusting paths should not be needed. Which platform is this on? Does this "mersdk/targets/<name>/usr/lib/qt5/qml/Sailfish/Silica/plugins.qmltypes" file exist under the installation directory?</name>
martyone ( 2019-01-26 19:25:39 +0200 )editI'm developing on macOS 10.14.3 Mojave. Both files exist:
jsommer ( 2019-01-27 12:11:36 +0200 )editI missed your words "If I create a new project ..." before. So it might be some change to the .pro file that causes this. If there is no such change, I would try to remove the .pro.user file (while the project is closed) and configure the project again. And last idea, is the project using one of the SailfishOS-* kit, not the Destkop kit, right?
martyone ( 2019-01-31 10:04:49 +0200 )edit@martyone. Thanks for your response. At the weekend I have updated the SDK. Afterwards the error disappeared. Maybe it was a bug of an intermediate release.
jsommer ( 2019-02-04 10:05:27 +0200 )edit