mirror of
git://git.openembedded.org/meta-openembedded
synced 2026-01-04 16:10:10 +00:00
334608d5dd
asio may or may not build examples and tests that depend on OpenSSL, alas, it has no way to explicitly enable or disable OpenSSL support, which is enabled unconditionally whenever openssl/ssl.h can be found. Due to that we get non-deterministic build behaviour, based on whether or not some other package pulled OpenSSL into the sysroot before asio's configure is running. Additionally, we can get random compilation failures if openssl/ssl.h exists during configure time, but is removed from sysroot later, e.g. due to a concurrent rebuild of OpenSSL at the same time as building asio. Having an explicit DEPENDS avoids both these problems. We can not use PACKAGECONFIG, because as mentioned above there is no way to explicitly disable OpenSSL support. Signed-off-by: André Draszik <adraszik@tycoint.com> Reviewed-by: Sylvain Lemieux <slemieux@tycoint.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> |
||
|---|---|---|
| .. | ||
| classes | ||
| conf | ||
| licenses | ||
| recipes-benchmark | ||
| recipes-bsp/pointercal | ||
| recipes-connectivity | ||
| recipes-core | ||
| recipes-devtools | ||
| recipes-extended | ||
| recipes-gnome | ||
| recipes-graphics | ||
| recipes-kernel | ||
| recipes-multimedia | ||
| recipes-navigation | ||
| recipes-sato/claws-mail | ||
| recipes-support | ||
| recipes-test | ||
| site | ||
| COPYING.MIT | ||
| README | ||
This layer depends on:
URI: git://github.com/openembedded/oe-core.git
branch: master
revision: HEAD
Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe]' in the subject'
When sending single patches, please use something like:
'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix=meta-oe][PATCH'
You are encouraged to fork the mirror on github https://github.com/openembedded/meta-oe/ 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 maintainer: Koen Kooi <koen@dominion.thruhere.net>
Martin Jansa <martin.jansa@gmail.com>