f4188229f1
If you perform a "bitbake -c devshell <some qt5 recipe>" and then try "which
qmake" in the devshell, you'll find your host's qmake is found (which is most
likely to be based on qt4) rather than the one that is built as part of
meta-qt5. The reason for this is that the qt5 items are installed to
${STAGING_DIR_NATIVE}/usr/bin/qt5 and not ${STAGING_DIR_NATIVE}/usr/bin. The
reason for the extra "qt5" directory at the end is so that qt4-based items
that are built in OE can live side-by-side with things from meta-qt5 without
interfering with each other.
This patch prepends ${STAGING_DIR_NATIVE}/usr/bin/qt5 to the devshell's PATH
so that the qt5-based native tools which are built as part of meta-qt5 will be
found before the host's.
Signed-off-by: Trevor Woerner <trevor.woerner@linaro.org>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
||
|---|---|---|
| classes | ||
| conf | ||
| recipes-devtools/cmake | ||
| recipes-qt/qt5 | ||
| COPYING.MIT | ||
| README | ||
README
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 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>