From: Brian Smucker <bds@bsmucker.eu.org>
To: yocto@yoctoproject.org
Subject: Re: supported IMAGE_FSTYPES
Date: Tue, 30 Oct 2012 12:40:03 -0700 [thread overview]
Message-ID: <50902D13.5020206@bsmucker.eu.org> (raw)
In-Reply-To: <50901799.2090408@am.sony.com>
From a yocto also-newbie:
This is a helpful command: bitbake -e |grep xxx
where xxx is something like ^IMAGE_FSTYPE=
That retrieves the current settings of that variable.
It doesn't answer your main question of what are the options. I had
that exact question a week or so ago.
Thanks
Brian
On 10/30/2012 11:08 AM, Tim Bird wrote:
> I am in the process of creating my own distro, and trying to figure out
> all the different build variables. This is a pretty daunting task
> for a yocto project/Poky newbie.
>
> Is there some place where the possible values for IMAGE_FSTYPE are
> documented? The Poky reference manual has this helpful sentence:
> "Formats of root filesystem images that you want to have created."
> However, it does not describe the possible values this variable
> should have.
>
> At the root of the poky source dir, doing a 'find -type f -print 0 | xargs -0 grep IMAGE_FSTYPES'
> seems to reveal the following used or checked-for image types:
> jffs2 sdimg tar.bz2 ubi ext3 ext2 cpio.gz live vmdk
>
> It appears the cpio.gz corresponds to an image suitable for an initramfs.
> jffs2, ext2, ext3, ubi and tar.bz2 appear self-explanatory.
> I have a pretty good idea that vmdk is somehow related to the
> virtual build image.
>
> What does 'live' do?
>
> Wait a sec...
>
> Reading meta/classes/image_types.bbclass I just found IMAGE_TYPES,
> which says it is "available to request which values are suitable
> for IMAGE_FSTYPES".
>
> This has the following definition in denzil:
> IMAGE_TYPES = "jffs2 sum.jffs2 cramfs ext2 ext2.gz ext2.bz2 ext3 ext3.gz
> ext2.lzma btrfs live squashfs squashfs-lzma ubi tar tar.gz tar.bz2 tar.xz
> cpio cpio.gz cpio.xz cpio.lzma vmdk"
>
> How does one query this variable? Other than reading the source, is
> there a way to know that such variables (which list the allowed values
> for other variables) exist?
>
> I apologize if these are newbie questions.
>
> Thanks,
> -- Tim
>
> =============================
> Tim Bird
> Architecture Group Chair, CE Workgroup of the Linux Foundation
> Senior Staff Engineer, Sony Network Entertainment
> =============================
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
next prev parent reply other threads:[~2012-10-30 19:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 18:08 supported IMAGE_FSTYPES Tim Bird
2012-10-30 19:40 ` Brian Smucker [this message]
2012-10-30 22:04 ` Trevor Woerner
-- strict thread matches above, loose matches on Subject: below --
2012-10-30 18:06 Tim Bird
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=50902D13.5020206@bsmucker.eu.org \
--to=bds@bsmucker.eu.org \
--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.