From: mattwood2000@gmail.com
To: Yocto-mailing-list <yocto@lists.yoctoproject.org>
Subject: Re: Create separate jffs2 with only specific data from recipe
Date: Sun, 10 Mar 2024 21:28:49 -0400 [thread overview]
Message-ID: <CADjezmZCNmf+g3u+QtePO5k7Nh2-cSFGxTK4asZCu-JzpAKTbg@mail.gmail.com> (raw)
In-Reply-To: <CADjezmaxO9pGMy91rMDgneq13VBS0FFcz9H_C-CVC2rnTX4rNQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1097 bytes --]
I was able to work this out. For others who may find this useful, my
method was to add mtd-utils-native to the DEPENDS list and then call
mkfs.jffs2 from do_install. I also inherited deploy and added a do_deploy
task to copy the jffs2 file to DEPLOYDIR.
Thanks, Matt.
On Thu, Mar 7, 2024 at 11:20 AM <mattwood2000@gmail.com> wrote:
> Hi,
>
> I've been looking around and trying to figure out if it is possible to
> create a separate jffs2 (or other FS) image that does not contain the main
> build image, but only specific files or data from a recipe in the same
> build.
>
> For example, I have an image recipe that creates a wic with ext4 and FAT32
> partitions containing the boot and rootfs to be flashed to eMMC. I want to
> create a separate jffs2 file that only contains specific data or
> applications generated by a recipe in the same build used to create the
> wic. This would be flashed to a QSPI device separate from the eMMC.
>
> I can do this manually but I would like to have the buildsystem handle it.
>
> Is this possible?
>
> Thanks, Matt.
>
[-- Attachment #2: Type: text/html, Size: 1530 bytes --]
prev parent reply other threads:[~2024-03-11 1:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 16:20 Create separate jffs2 with only specific data from recipe mattwood2000
2024-03-11 1:28 ` mattwood2000 [this message]
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=CADjezmZCNmf+g3u+QtePO5k7Nh2-cSFGxTK4asZCu-JzpAKTbg@mail.gmail.com \
--to=mattwood2000@gmail.com \
--cc=yocto@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).