From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: "João Henrique Ferreira de Freitas" <joaohf@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [wic][PATCH] wic: Implement --build-rootfs command line option
Date: Thu, 9 Apr 2015 22:12:35 +0300 [thread overview]
Message-ID: <20150409191235.GA19415@linux.intel.com> (raw)
In-Reply-To: <5525A940.5040600@gmail.com>
On Wed, Apr 08, 2015 at 07:18:40PM -0300, João Henrique Ferreira de Freitas wrote:
>
> Hi Ed,
>
> I liked.
>
> Two points:
>
> - How about if user sets INHERIT = "rm_work"? I mean the image
> recipe will be rm, right? I always put my images in RM_WORK_EXCLUDE
> so wic can use it.
>
rm_work removes artifacts required by wic. Wic will complain that rootfs
can't be found. There is a bug about i https://bugzilla.yoctoproject.org/show_bug.cgi?id=7042
I closed it as not a bug as wic uses build artifacts by design.
> - What will be the behavior if: wic create test-image-4Gb -e
> test-image --rootfs rootfs1=test-image --rootfs
> rootfs2=bringup-image -f. A believed that only 'test-image' will be
> build. Right?
>
I don't fully understand command line options in your example, but generally you're right.
wic will take image name from -e option and run "bitbake test-image" in this case.
Regards,
Ed
next prev parent reply other threads:[~2015-04-09 19:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 9:57 [wic][PATCH] wic: Implement --build-rootfs command line option Ed Bartosh
2015-04-08 22:18 ` João Henrique Ferreira de Freitas
2015-04-09 19:12 ` Ed Bartosh [this message]
2015-04-09 22:24 ` João Henrique Ferreira de Freitas
2015-04-10 9:16 ` Ed Bartosh
-- strict thread matches above, loose matches on Subject: below --
2015-04-20 16:13 Adrian Freihofer
2015-04-21 12:39 ` Ed Bartosh
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=20150409191235.GA19415@linux.intel.com \
--to=ed.bartosh@linux.intel.com \
--cc=joaohf@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox