Using tmp/deploy/tools for deploying native tools is nowadays used hardly anywhere. It also has some severe drawkbacks since it relies on having matching shared libs in the host system.
Now, with poky having moved to openssl 3.0 and most distros have not, yet, this became unusable for most people, anyway.
They will run into this error:
tmp/deploy/tools/rauc: error while loading shared libraries: libssl.so.3: cannot open shared object file: No such file or directory
The recommended way of using native tools in Yocto is to use oe-run-native. Document this in the README instead of the old deploy-way..
Using tmp/deploy/tools for deploying native tools is nowadays used hardly anywhere. It also has some severe drawkbacks since it relies on having matching shared libs in the host system.
Now, with poky having moved to openssl 3.0 and most distros have not, yet, this became unusable for most people, anyway.
They will run into this error:
The recommended way of using native tools in Yocto is to use oe-run-native. Document this in the README instead of the old deploy-way..
Signed-off-by: Enrico Jorns ejo@pengutronix.de