All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Andre McCurdy <armccurdy@gmail.com>
Cc: Andrea Adami <andrea.adami@gmail.com>,
	 OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] want to clarify proper approach to shared lib (.so) installation
Date: Fri, 4 Jun 2021 07:46:08 -0400 (EDT)	[thread overview]
Message-ID: <e33778b2-43e-bcd5-eeb2-1f319b38c4b1@crashcourse.ca> (raw)
In-Reply-To: <CAJ86T=WtkkUjFHQiY1a-+4-7-JxTZcdTM+6aHJ+FYc5o1hzHzg@mail.gmail.com>

On Fri, 4 Jun 2021, Andre McCurdy wrote:

... big ship ...

> Just a warning, but if your Makefiles are not generating versioned
> shared libraries then they are probably not setting a soname
> either... and that really messes up OE's automatic runtime
> dependency tracking for shared libraries.
>
> If OE is your main build environment for these components it's
> usually better in the long run to just update your Makefiles to
> create versioned shared libraries (using simple version .0 and a
> single symlink is fine) and setting a soname than to use the above
> trick to force packaging of an unversioned .so and manually defining
> runtime dependencies everywhere.

  oh, i realize that ... the current build system is very
legacy-driven and i have a lengthy list of cleanups to do, this just
one of them. for now, things just have to work until i can bend things
into shape.

rday

      reply	other threads:[~2021-06-04 11:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-03 14:00 want to clarify proper approach to shared lib (.so) installation Robert P. J. Day
2021-06-03 14:15 ` [OE-core] " Andrea Adami
2021-06-03 14:26   ` Robert P. J. Day
2021-06-04  7:58     ` Andre McCurdy
2021-06-04 11:46       ` Robert P. J. Day [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=e33778b2-43e-bcd5-eeb2-1f319b38c4b1@crashcourse.ca \
    --to=rpjday@crashcourse.ca \
    --cc=andrea.adami@gmail.com \
    --cc=armccurdy@gmail.com \
    --cc=openembedded-core@lists.openembedded.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.