On Sat, Oct 2, 2021 at 6:55 PM Lijun Chen <email@example.com> wrote:
When I build a yocto image, I added some packages into IMAGE_INSTALL, such as boost, thrift, etc. I notice in the target OS image, the shared libs don't the symlinks. But in the SDK image, the symlinks are there. For example,
lrwxrwxrwx 1 root root 22 Oct 2 16:41 libboost_filesystem-mt.so -> libboost_filesystem.so
lrwxrwxrwx 1 root root 29 Oct 2 16:41 libboost_filesystem.so -> libboost_filesystem.so.1.75.0
Is there a way to add the symlinks to the target image as well?
With the symlinks, I assume we can run an old application even the dependent lib is a newer version?
unversioned symlinks should not be used they are there to be used for
linking during build time. Unless you need to do builds on targets you
really do not need them
so explain you usecase. Are you trying to build stuff on device ?
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.