On Wed, Nov 28, 2018 at 9:26 PM Richard Weinberger
On Wed, Nov 28, 2018 at 9:42 AM Richard Purdie
My idea was having a 32bit only SDK. In my case I really don't need
But it seems that building and SDK is currently broken/disabled:http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=e153efde9754a650e555f46cba09680baabd7d7e
I see a bug was opened for this but its not valid and this shouldn't be
an issue. Keep in mind that an SDK contains all multilibs so "bitbake
X-image -c populate_sdk" would be equivalent to "bitbake libXX-X-image
-c populate_sdk" and be the same thing. One didn't work so we remove
On the other hand, having both 32bit and 64bit libs in the SDK is not
a big deal right now.
So I did "bitbake my-image -c populate_sdk" but the resulting SDK
seems to contain no
TOOLCHAIN_TARGET_TASK contains "openssl", so I expected libssl.so present.
I did a search for libssl.so and found these files in the SDK install directory:
Both files are 64bit shared libraries :-(
What do I miss?