documentation/dev-manual/common-tasks.rst

5381 Creating Partitioned Images Using Wic
5390 flash, or an HDD, you can use the OpenEmbedded Image Creator, Wic, to
5417 This section provides some background information on Wic, describes what
5419 to use the Wic utility, provides information on using the Wic plugins
5420 interface, and provides several examples that show how to use Wic.
5425 This section provides some background on the Wic utility. While none of
5426 this information is required to use Wic, you might find it interesting.
5428 -  The name "Wic" is derived from OpenEmbedded Image Creator (oeic). The
5432 -  Wic is loosely based on the Meego Image Creator (``mic``) framework.
5433    The Wic implementation has been heavily modified to make direct use
5438 -  Wic is a completely independent standalone utility that initially
5442    class. The difference between Wic and those examples is that with Wic
5450 In order to use the Wic utility with the OpenEmbedded Build system, your
5469    using Wic, the current version of Wic requires the artifacts in the
5495 Currently, Wic supports seven commands: ``cp``, ``create``, ``help``,
5506 Wic supports help for three topics: ``overview``, ``plugins``, and
5511 For example, the following returns overview help for Wic::
5515 There is one additional level of help for Wic. You can get help on
5517 command to return the available Wic images as follows::
5536 Wic images, you can use ``help`` with the command to get help on a
5548 You can use Wic in two different modes, depending on how much control
5552 -  *Raw Mode:* You explicitly specify build artifacts through Wic
5567 Running Wic in raw mode allows you to specify all the partitions through
5572 Contrast this behavior with cooked mode where Wic looks in the Build
5620    You do not need root privileges to run Wic. In fact, you should not
5626 Running Wic in cooked mode leverages off artifacts in the Build
5630 by using the "-e" option. Wic looks in the Build Directory (e.g.
5654 existing file provided by the Wic installation. As shipped, kickstart
5695 Using the Wic Plugin Interface
5698 You can extend and specialize Wic functionality by using Wic plugins.
5699 This section explains the Wic plugin interface.
5703    Wic plugins consist of "source" and "imager" plugins. Imager plugins
5707 the Wic image generation process. You can use source plugins to map
5715    tools, bootloaders, and so forth) when building a Wic image, you need
5724 populate a specific Wic image partition.
5737 available to Wic.
5739 When the Wic implementation needs to invoke a partition-specific
5753 example method called by the Wic implementation when it needs to prepare
5782 subclass (plugin) itself does not implement a particular function, Wic
5830 See the Wic implementation for examples and details.
5832 Wic Examples
5835 This section provides several examples that show how to use the Wic
5979 ``-o`` option to cause Wic to create the output somewhere other than the
6007 Using Wic to Manipulate an Image
6010 Wic image manipulation allows you to shorten turnaround time during
6011 image development. For example, you can use Wic to delete the kernel
6012 partition of a Wic image and then insert a newly built kernel. This
6018    In order to use Wic to manipulate a Wic image as in this example,
6021 The following example examines the contents of the Wic image, deletes
6025    partitions in the Wic image::
6040       You can get command usage on any Wic command using the following
6076       in the file. Then, run the Wic command again::
6089    updated kernel to the Wic image. Depending on how you built your
6135 Following, is an example that shows how to flash a Wic image. Realize
6136 that while this example uses a Wic image, you can use Bmaptool to flash