From: Michael Smith <msmith@cbnco.com>
To: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Recommended way to stage nothing?
Date: Tue, 09 Nov 2010 19:06:25 -0500 [thread overview]
Message-ID: <4CD9E201.3040808@cbnco.com> (raw)
Hi,
There's a recipe that installs binary blob libraries, overwriting the
libraries from a standard package. (Let's say the first letter of the
binary recipe is N, second is V...) There is no need to stage the binary
libraries; at build-time the standard libraries are fine.
What's the best way to prevent anything from being staged in the new
post-legacy-staging world? At the moment I'm doing:
EXCLUDE_FROM_SHLIBS = "1"
sysroot_stage_all() {
}
Seems to work, but I don't know if it's the right way.
Mike
reply other threads:[~2010-11-10 0:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4CD9E201.3040808@cbnco.com \
--to=msmith@cbnco.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.