mirror of
https://github.com/thead-yocto-mirror/meta-qt5
synced 2026-09-04 05:04:36 +02:00
6ce50bf97b
cinematicexperience will run failed on Qt5.3.0 and Qt5.3.1, error message
as below
------------------------------------------------------------
Qt5_CinematicExperience.qml:26:5: Type MainView unavailable
MainView {
^
/content/MainView.qml:241:9: Type SettingsView unavailable
SettingsView {
^
/content/SettingsView.qml:88:13: Type Switch unavailable
Switch {
^
/content/Switch.qml:9:21: Cannot assign a value to a signal (expecting a script to be run)
property string onText: "On"
^
------------------------------------------------------------
This patch fix this issue and make cinematicexperience can run on qt5.3.
ref: http://wickwire2099.blogspot.tw/2014/05/qt-530-qt5-cinematic-experience.html
Signed-off-by: Yen-Chin Lee <coldnew.tw@gmail.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
This layer depends on: URI: git://github.com/openembedded/oe-core.git branch: master revision: HEAD URI: git://github.com/openembedded/meta-oe.git layers: meta-ruby branch: master revision: HEAD When building stuff like qtdeclarative, qtquick, qtwebkit, make sure that you have required PACKAGECONFIG options enabled in qtbase build, see qtbase.inc for detail. Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-qt5]' in the subject' When sending single patches, please using something like: 'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix=meta-qt5][PATCH' You are encouraged to fork the mirror on github[1] to share your patches. This is preferred for patch sets consisting of more than one patch. Other services like gitorious, repo.or.cz or self hosted setups are of course accepted as well, 'git fetch <remote>' works the same on all of them. We recommend github because it is free, easy to use, has been proven to be reliable and has a really good web GUI. 1. https://github.com/meta-qt5/meta-qt5/ Main layer maintainers: Martin 'JaMa' Jansa <martin.jansa@gmail.com> Otavio Salvador <otavio@ossystems.com.br>