mirror of
https://github.com/thead-yocto-mirror/meta-qt5
synced 2026-09-07 14:44:37 +02:00
57709a4ee2
If Qt5 (qtbase) is machine specific, then all packages depending on qtbase will also be machine specific, because the (initial) qtbase configuration becomes part of Qt5/qmake, thus affecting builds of packages built against this specific version of qtbase. Since it is not feasible to add PACKAGE_ARCH=... to each and every recipe that is built using qmake and depends on Qt5, we introduce a new variable, QT_PACKAGES_ARCH, that can be set by the machine configuration as needed. We have to be careful though to only change the architecture of the resulting packages if we're not compiling a 'native' package. Signed-off-by: André Draszik <andre.draszik@linaro.org> 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 https://github.com/meta-qt5/meta-qt5/ 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. Main layer maintainers: Martin 'JaMa' Jansa <martin.jansa@gmail.com> Otavio Salvador <otavio@ossystems.com.br>