From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Roxana Ciobanu <roxana.ciobanu@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] image.bbclass: add ROOTFS_POSTPROCESS_COMMAND to rootfs[vardeps]
Date: Wed, 09 Jul 2014 21:42:58 +0100 [thread overview]
Message-ID: <1404938578.15985.59.camel@ted> (raw)
In-Reply-To: <fc1e780d3862d570820104c388a20e2b6d832c89.1404896873.git.roxana.ciobanu@intel.com>
On Wed, 2014-07-09 at 12:08 +0300, Roxana Ciobanu wrote:
> Changes to ROOTFS_POSTPROCESS_COMMAND require the rootfs
> for the image to be rebuilt.
>
> [YOCTO #6502]
>
> Signed-off-by: Roxana Ciobanu <roxana.ciobanu@intel.com>
> ---
> meta/classes/image.bbclass | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
> index a03b880..e088bdb 100644
> --- a/meta/classes/image.bbclass
> +++ b/meta/classes/image.bbclass
> @@ -75,7 +75,7 @@ LDCONFIGDEPEND_libc-musl = ""
> do_rootfs[depends] += "makedevs-native:do_populate_sysroot virtual/fakeroot-native:do_populate_sysroot ${LDCONFIGDEPEND}"
> do_rootfs[depends] += "virtual/update-alternatives-native:do_populate_sysroot update-rc.d-native:do_populate_sysroot"
> do_rootfs[recrdeptask] += "do_packagedata"
> -do_rootfs[vardeps] += "BAD_RECOMMENDATIONS NO_RECOMMENDATIONS"
> +do_rootfs[vardeps] += "BAD_RECOMMENDATIONS NO_RECOMMENDATIONS ROOTFS_POSTPROCESS_COMMAND"
>
> do_build[depends] += "virtual/kernel:do_deploy"
Are there other variables we look at in the rootfs process we also need
to list here?
As background, the move to lib/oe has moved the variables outside the
scope of bitbake's function parsing code so we need to handle that
manually now...
Cheers,
Richard
next prev parent reply other threads:[~2014-07-09 20:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 9:08 [PATCH 0/1] Fix for YB6502 Roxana Ciobanu
2014-07-09 9:08 ` [PATCH 1/1] image.bbclass: add ROOTFS_POSTPROCESS_COMMAND to rootfs[vardeps] Roxana Ciobanu
2014-07-09 20:42 ` Richard Purdie [this message]
2014-07-13 23:48 ` Jacob Kroon
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=1404938578.15985.59.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=roxana.ciobanu@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox