> Am 08.07.2020 um 23:20 schrieb Otavio Salvador : > > Em qua., 8 de jul. de 2020 às 16:58, Jens Rehsack escreveu: >> >> Instead of recognizing only environment-setup scripts in >> ${STAGING_DIR_TARGET} or ${STAGING_DIR_NATIVE}, respectively - lurk also into >> ${SDKPATH}/buildtools/sysroots/${SDK_SYS} where nativesdk-openssl installs >> setup files. >> >> Remove overwriting of OPENSSL_CONF from buildtools-tarball.bb to clarify >> whether nativesdk-openssl installs wrong content or buildtools-tarball: >> (nativesdk-openssl) tmp/sysroots/x86_64/usr/lib/ssl-1.1/openssl.cnf >> (buildtools-tarball) buildtools/sysroots/x86_64-pokysdk-linux/etc/ssl/openssl.cnf >> >> Signed-off-by: Jens Rehsack > > I did not understand the openssl related change. Is it possible to > rework the commit log so it is more detailed? For sure, but maybe I'm completely wrong. Let me try explaining it first... If - and only if - one creates an SDK which included openssl (and not libressl, mbedssl, ...), nativesdk-openssl packages an ${SDKPATHNATIVE}/environment-setup.d/openssl.sh OTOH - meta/recipes-core/meta/buildtools-tarball.bb creates a script which is sourced at the very end of SDK environment setup and writes what's included in {SDKPATHNATIVE}/environment-setup.d/openssl.sh on it's own - with maybe slightly different location - what guides me to add: ... to clarify whether nativesdk-openssl installs wrong content or buildtools-tarball: (nativesdk-openssl) tmp/sysroots/x86_64/usr/lib/ssl-1.1/openssl.cnf (buildtools-tarball) buildtools/sysroots/x86_64-pokysdk-linux/etc/ssl/openssl.cnf Maybe they way how nativesdk-cmake is doing it is the right way. Then, maybe nativesdk-openssl should be reworked. This is for clarification. Does it explain something better? Cheers -- Jens Rehsack - rehsack@gmail.com