From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/5] shlibs providers improvements
Date: Sat, 18 Jan 2014 15:02:05 +0100 [thread overview]
Message-ID: <cover.1390052636.git.Martin.Jansa@gmail.com> (raw)
Fixes for [YOCTO #4628]
Richard had few more ideas to improve it even more, but this is good start.
Most important changes:
* PRIVATE_LIBS aren't duplicitly added to RDEPENDS (when recipe provides
own libfoo it shouldn't get runtime dependency on global libfoo shlib provider)
* warning is shown for undeterministic providers (multiple packages
recorded to provide the same library) - recipe maintainers can decide
if such library should be considered private or make sure that only one
package is built (most common case are gst plugins where 0.10 and 1.* provide
the same gst modules, but as long as nobody tries to linke directly to some
gst plugin we shouldn't list them as shlib providers).
* list files which require given shlib, often I was surprised to see that
something got runtime dependency on libfoo, showing which binary is linked to
it makes it easier to debug when you have only log.do_package and package
directory is already gone (e.g. analyzing test-dependencies.sh script outputs)
The following changes since commit 8163854adf87ac42a8f08ee25685d0ce1efb4724:
oe-selftest: separated the SStateBase and SStateTests in different modules (2014-01-16 12:18:44 +0000)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib jansa/shlib-providers
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=jansa/shlib-providers
Martin Jansa (5):
package.bbclass: move reading shlibs providers to separate function
package.bbclass: show warning when package is trying to provide
already provided shlib
package.bbclass: add SHLIBSSEARCHDIRS to define where to search for
shlib providers
package.bbclass: Don't search for prividers of PRIVATE_LIBS
package.bbclass: Show which files require given dependency in debug
output
meta/classes/package.bbclass | 102 +++++++++++++++++++++++++++++++------------
1 file changed, 75 insertions(+), 27 deletions(-)
--
1.8.5.2
next reply other threads:[~2014-01-18 14:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-18 14:02 Martin Jansa [this message]
2014-01-18 14:02 ` [PATCH 1/5] package.bbclass: move reading shlibs providers to separate function Martin Jansa
2014-01-18 14:02 ` [PATCH 2/5] package.bbclass: show warning when package is trying to provide already provided shlib Martin Jansa
2014-01-19 13:13 ` Martin Jansa
[not found] ` <cover.1390138091.git.Martin.Jansa@gmail.com>
2014-01-19 13:28 ` [PATCHv2 " Martin Jansa
2014-01-19 14:42 ` Phil Blundell
2014-01-19 15:23 ` [PATCHv2 3/5] package.bbclass: add SHLIBSSEARCHDIRS to define where to search for shlib providers Martin Jansa
2014-01-19 15:25 ` Martin Jansa
2014-01-19 15:24 ` [PATCHv3 2/5] package.bbclass: show warning when package is providing already provided shlib Martin Jansa
2014-01-18 14:02 ` [PATCH 3/5] package.bbclass: add SHLIBSSEARCHDIRS to define where to search for shlib providers Martin Jansa
2014-01-19 17:13 ` Richard Purdie
2014-01-19 18:55 ` Martin Jansa
2014-01-18 14:02 ` [PATCH 4/5] package.bbclass: Don't search for prividers of PRIVATE_LIBS Martin Jansa
2014-01-18 14:02 ` [PATCH 5/5] package.bbclass: Show which files require given dependency in debug output Martin Jansa
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=cover.1390052636.git.Martin.Jansa@gmail.com \
--to=martin.jansa@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.