All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Lijun Chen <lijchen@blackberry.com>
Cc: "yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] Shared lib symlinks in target image
Date: Mon, 4 Oct 2021 06:42:35 -0700	[thread overview]
Message-ID: <CAMKF1srQzcaStU4zBqd34+f4ie_tPibFmS2ZerZ0Ryi4YBrWTA@mail.gmail.com> (raw)
In-Reply-To: <7508347f66784a1487e4f20bf1ad89f0@blackberry.com>

[-- Attachment #1: Type: text/plain, Size: 3845 bytes --]

Libraries have another symlink which looks something like libfoo.so.1 and 2
etc that is the one which should be used by apps
On Mon, Oct 4, 2021 at 6:12 AM Lijun Chen <lijchen@blackberry.com> wrote:

> I have an app built in a different environment that has lower versioned
> libs, such as boost. I was wondering if on the target there are symlinks to
> those libs, whether the app can be run on a target that has newer libs
> without resbuild against a matched env. Seems that is not viable.
> ------------------------------
> *From:* Khem Raj <raj.khem@gmail.com>
> *Sent:* Saturday, October 2, 2021 11:23:58 PM
> *To:* Lijun Chen
> *Cc:* yocto@lists.yoctoproject.org
> *Subject:* Re: [yocto] Shared lib symlinks in target image
>
> On Sat, Oct 2, 2021 at 6:55 PM Lijun Chen <lijchen@blackberry.com> wrote:
> >
> > Hi,
> >
> >
> > 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 ?
>
> >
> > Thanks,
> >
> > Lijun
> >
> > ________________________________
> > 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.
> >
> > -=-=-=-=-=-=-=-=-=-=-=-
> > Links: You receive all messages sent to this group.
> > You automatically follow any topics you start or reply to.
> > View/Reply Online (#54934):
> https://urldefense.com/v3/__https://lists.yoctoproject.org/g/yocto/message/54934__;!!COg3wY07Hnb7!44p3yfVEnAD6rM-DM0muASh2wNizlchKqgoweZDAV8wx1sd8uvxVqOEHJORDalv1bA$
> > Mute This Topic:
> https://urldefense.com/v3/__https://lists.yoctoproject.org/mt/86035483/1997914__;!!COg3wY07Hnb7!44p3yfVEnAD6rM-DM0muASh2wNizlchKqgoweZDAV8wx1sd8uvxVqOEHJOTJ_1cQxQ$
> > Group Owner: yocto+owner@lists.yoctoproject.org
> > Unsubscribe:
> https://urldefense.com/v3/__https://lists.yoctoproject.org/g/yocto/unsub__;!!COg3wY07Hnb7!44p3yfVEnAD6rM-DM0muASh2wNizlchKqgoweZDAV8wx1sd8uvxVqOEHJOQieFL_-A$
> [raj.khem@gmail.com]
> > -=-=-=-=-=-=-=-=-=-=-=-
> >
> ------------------------------
> 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.
>

[-- Attachment #2: Type: text/html, Size: 6156 bytes --]

      reply	other threads:[~2021-10-04 13:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-03  1:55 Shared lib symlinks in target image Lijun Chen
2021-10-03  3:23 ` [yocto] " Khem Raj
2021-10-04 13:12   ` Lijun Chen
2021-10-04 13:42     ` Khem Raj [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAMKF1srQzcaStU4zBqd34+f4ie_tPibFmS2ZerZ0Ryi4YBrWTA@mail.gmail.com \
    --to=raj.khem@gmail.com \
    --cc=lijchen@blackberry.com \
    --cc=yocto@lists.yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.