Skip to contentSkip to conversation

eSDK: extra nativesdk binaries are not relocated

DISCUSSION [email protected] 1 participant 1 message Mar 25, 2025

lore
Share & tools
lore
#0 lore raw

Dear all,

I am trying to add some native tools to the (bundled) extensible SDK. Unfortunately, the executables don't seem to be relocated during installation and setup of the eSDK, and thus cannot be run. To eliminate possible conflicts with our yocto setup, I tested again with the vanilla poky distribution and was able to reproduce the issue:

* clone and initialize poky ( *kirkstone* )
* add the desired package (e.g. socat) and the necessary dummies to local.conf:
TOOLCHAIN_HOST_TASK_ESDK:append = " nativesdk-socat nativesdk-sdk-provides-dummy"
* create the eSDK for core-image-sato:
bitbake -c populate_sdk_ext core-image-sato

After installing the resulting eSDK, socat's libraries and executables are copied to the eSDK's sysroot directly ("<sdkpath>/sysroots/x86_64-pokysdk-linux/..."). However, their dynamic loader is still set to the placeholder "/usr/local/oe-sdk-hardcoded-buildpath/sysroots/x86_64-pokysdk-linux/lib/ld-linux-x86-64.so.2". Possible symlinks (as installed for e.g. nativesdk-file) also target a sysroot at "/usr/local/oe-sdk-hardcoded-buildpath/sysroots/x86_64-pokysdk-linux/...". If python or a package requiring it is installed, it even breaks devtool, as it is found via PATH before the "<sdkpath>/buildtools/sysroots"'s python (which is relocated correctly).

When testing the scenario with *scarthgap* , the installed extra binaries remain "unrelocated". But apparently devtool was moved away from "<sdkpath>/sysroots", and the environment-setup script no longer adds this sysroot to PATH.

So, how should tools that I want to run on the sdk machine be added to the eSDK? Should they somehow be added to the buildtools, for which the relocation is still performed?

Thanks and best regards
Cordt