From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Some packages don't get deployed to the staging directory?
Date: Fri, 20 Apr 2012 13:01:33 +0200 [thread overview]
Message-ID: <jmrfmb$s29$1@dough.gmane.org> (raw)
In-Reply-To: <CAGiJk9eeDabHUuKAnHZtWw_ChX7jVEDvsN+LEpsZomvH_Ky94w@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 20-04-12 12:15, Samuel Stirtzel schreef:
> Hi, my observation shows that e.g. libphonon.so from the package
> libqtphonon4-dev will not get installed to the staging sysroot.
>
> Is this intended or a bug?
>
>
> The same happened with other non -dev packages like
> meta-kde/recipes-base/kde-runtime_git.bb. The package
> kde-runtime-declarative-scriptengine will get installed but it's content
> is missing in the staging sysroot (not an issue but still confusing).
>
> I'm currently fixing race conditions in meta-kde and set strict explicit
> behavior on search paths for libraries (not searching native/hosts
> directories for libs). kdelibs4 obviously fails over this with
> "libphonon.so no rule to make target", but that goes too much into the
> details.
AIUI OE uses a whitelist to stage directories (correct me if I'm wrong), so
not everything ends up in sysroots. I have a similar problem with files in
/lib/firmware that I'd like to have end up in sysroots.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org
iQIcBAEBAgAGBQJPkUIMAAoJEHZqAkdh1vT6fNkP/3bsgWzl9Bp94pjwmoQsjkho
+HPKhVk7wcwBBTCO4mj7McmSNEGWOPPhbIdgBZuTNtiy9UVbcdIY0kZHoWhPT5u+
LlXpvAShlXXyhmQMj3HBrGfxgGUAICSZUZbkv1GOR8CLdQMRcbvu2NxMqGVpV+/9
Z7SuKu1grFk9Zc0akbwqSs1O193YTw0AX8fH/re/k4WGwD/gZJxPlnmmXhhNDj+W
N7HD2eqBUngf08motz2cOwgzOOAHuBjDeuW38pZa9N/3cy+bMr7H6Z8JDcDOqs0Z
nWRIlfXn9aR5M74ii8QpCf8sBhocK4fvF/u2wpUSMdsBNrFkeJXCwvbH+uNN8b98
llf50m1ySkMwvmpnwbqtkJXYUfFu4v7kAQO4bideW1To1+Il/1tw3Bi2b/HFmQZN
+7goTsx/R9yW4kDAfxAT3mRLI7VkIYruO7A/zlrOzxbEYUcePsVzi1FGdLrVbqRM
J/GXKjQ6QepmseHCLQenTrNM6/APyV4fyi+yAoDfwrUncXkcEa4jg1I9URZh7tqT
yPsXMOMzoj5xjM5VY8kt1ip3SeOSE0Pg4Ls6c+jkXhnVRUk40vZDZ+THqcF10Wlx
j5c4xcugy5wJnu2jSxNXzRmNdpCIo/N6YuHauhqnbgqd/wv1oaIdDu69tci6eF2m
iFwZ2hoR+QgOdETE3Lmy
=Mmwh
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-04-20 11:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 10:15 Some packages don't get deployed to the staging directory? Samuel Stirtzel
2012-04-20 11:01 ` Koen Kooi [this message]
2012-04-23 8:48 ` Samuel Stirtzel
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='jmrfmb$s29$1@dough.gmane.org' \
--to=koen@dominion.thruhere.net \
--cc=openembedded-devel@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.