Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: Daniel Schultz <d.schultz@phytec.de>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Create more than one image with WIC
Date: Wed, 8 Mar 2017 12:57:29 +0200	[thread overview]
Message-ID: <20170308105729.GA22401@linux.intel.com> (raw)
In-Reply-To: <2791e915-9e22-a01a-ccb5-c629d250edb2@phytec.de>

On Wed, Mar 08, 2017 at 10:44:21AM +0100, Daniel Schultz wrote:
> Hi,
> 
> I created two kickstart files (am335x-sdimage.wks, am335x-emmc.wks)
> and added them to the local.conf.
> 
> When I build the image only the first wks in WKS_FILES will be used
> by WIC and the second will be ignored. Is it possible to build two
> images in one build?
>

I don't think it's possible to build more than one image for the same
type. wic is not an exception here.

> Includes of the wks files in local.conf:
> WKS_FILES_ti33x = "am335x-sdimage.wks am335x-emmc.wks "

WKS_FILES variable is to provide possible wks files to use. First one found will
be used to produce an image.

--
Regards,
Ed


  reply	other threads:[~2017-03-08 11:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-08  9:44 Create more than one image with WIC Daniel Schultz
2017-03-08 10:57 ` Ed Bartosh [this message]
2017-03-08 13:41   ` Gary Thomas
2017-03-08 13:43     ` Ed Bartosh
2017-03-13 16:16       ` Daniel Schultz
2017-03-14 17:11         ` Ed Bartosh
2017-03-14 17:49           ` Patrick Ohly
2017-03-14 18:06             ` Ed Bartosh
2017-03-15  7:24               ` Patrick Ohly
2017-03-15 12:58                 ` Ed Bartosh
2017-03-15 13:39                   ` Patrick Ohly
2017-03-15 13:41                     ` Patrick Ohly
2017-03-15 14:01                       ` Ed Bartosh
2017-03-15 14:47                         ` Ed Bartosh
2017-03-15 15:09                           ` Patrick Ohly
2017-03-15 15:04                         ` Patrick Ohly

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=20170308105729.GA22401@linux.intel.com \
    --to=ed.bartosh@linux.intel.com \
    --cc=d.schultz@phytec.de \
    --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