From: Samuel Stirtzel <s.stirtzel@googlemail.com>
To: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Some packages don't get deployed to the staging directory?
Date: Fri, 20 Apr 2012 12:15:50 +0200 [thread overview]
Message-ID: <CAGiJk9eeDabHUuKAnHZtWw_ChX7jVEDvsN+LEpsZomvH_Ky94w@mail.gmail.com> (raw)
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.
--
Regards
Samuel
next reply other threads:[~2012-04-20 10:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 10:15 Samuel Stirtzel [this message]
2012-04-20 11:01 ` Some packages don't get deployed to the staging directory? Koen Kooi
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=CAGiJk9eeDabHUuKAnHZtWw_ChX7jVEDvsN+LEpsZomvH_Ky94w@mail.gmail.com \
--to=s.stirtzel@googlemail.com \
--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.