From: Nikolay Dimitrov <picmaster@mail.bg>
To: Khem Raj <raj.khem@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: 2 images with single Bitbake recipe
Date: Mon, 09 Mar 2015 21:56:46 +0200 [thread overview]
Message-ID: <54FDFAFE.7020707@mail.bg> (raw)
In-Reply-To: <BD661189-005C-48AE-804D-31A33CB14583@gmail.com>
Hi Khem,
On 03/09/2015 09:31 PM, Khem Raj wrote:
>
>> On Mar 9, 2015, at 12:22 PM, Nikolay Dimitrov <picmaster@mail.bg> wrote:
>>
>> Hi guys,
>>
>> I need an advice for the following Yocto use case.
>>
>> My system has to boot via minimal initramfs and then must use the full
>> rootfs. I can use 2 separate recipes to generate the 2 images (minimal
>> initramfs, complete rootfs), but I prefer to create all my build-
>> products via single bitbake command.
>>
>> So, is it possible to build these 2 images with 1 recipe, and if "yes"
>> then how?
>>
>
>
> Look at how initramfs http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#ref-tasks-bundle_initramfs
> and also meta/conf/local.conf.sample.extended
Thanks for answering. INITRAMFS_IMAGE_BUNDLE doesn't achieve what I
need, instead it merges the kernel image and initramfs in a single
file. What I need is, instead of invoking:
bitbake myproduct-image
bitbake myproduct-initrams-image
to invoke:
bitbake myproduct-combined-image
...which should create 2 separate images.
Regards,
Nikolay
next prev parent reply other threads:[~2015-03-09 19:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 19:22 2 images with single Bitbake recipe Nikolay Dimitrov
2015-03-09 19:31 ` Khem Raj
2015-03-09 19:56 ` Nikolay Dimitrov [this message]
2015-03-09 19:58 ` Burton, Ross
2015-03-09 20:05 ` Nikolay Dimitrov
[not found] ` <1425931669.5166.45.camel@concept-embarque.fr>
2015-03-10 13:30 ` Nikolay Dimitrov
2015-03-09 20:00 ` Gary Thomas
2015-03-09 20:06 ` Nikolay Dimitrov
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=54FDFAFE.7020707@mail.bg \
--to=picmaster@mail.bg \
--cc=raj.khem@gmail.com \
--cc=yocto@yoctoproject.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.