Summary: | simple Qt5 qml app does not start | ||
---|---|---|---|
Product: | [Applications] marble | Reporter: | Dibala Vasiliy <dibalavs> |
Component: | general | Assignee: | marble-bugs |
Status: | REPORTED --- | ||
Severity: | normal | CC: | alessandro.pezzato, nienhueser |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | attachment-6832-0.html |
Description
Dibala Vasiliy
2014-06-22 11:04:55 UTC
I have exactly the same problem, Qt 5.5 on gentoo x86_64 For Qt Quick 1.1 it was necessary to set QML_IMPORT_PATH. Otherwise you get that import error. Setting QML_IMPORT_TRACE=1 is useful to debug such problems. Just recently we moved to Qt Quick 2 in the master branch and upgraded org.kde.edu.marble from 0.11 to 0.20. I changed the declarative plugin to a library-style plugin which means that at the moment qmlviewer will not be able to import org.kde.edu.marble 0.20. This was easier to get it running on Android, but I might change that until the next release to enable direct .qml loading again. When that is done, QML2_IMPORT_PATH must be set. Created attachment 94075 [details]
attachment-6832-0.html
Thank you Dennis. I've found the example in src/examples/cpp/marbleQuick2
which is working with QtQuick 2. I can reproduce it in my app only manually
copying src/lib/marble/declarative/*.h files in the install path. These
headers are not normally installed like others.
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved. |