From: "Hombourger, Cedric" <Cedric_Hombourger@mentor.com>
To: Jan Kiszka <jan.kiszka@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: RE: [PATCH] wic-img: handle variables in .wks files
Date: Fri, 8 Feb 2019 07:55:36 +0000 [thread overview]
Message-ID: <211b85d81663465abfa192d0da5c841c@svr-ies-mbx-02.mgc.mentorg.com> (raw)
In-Reply-To: <c1d51a02-5a99-4383-5b47-4ad5292fb48a@siemens.com>
Thanks for the pointer. Will check how that's implemented there and if it works equally well on Isar
(I was obviously not aware that OE was now having this)
-----Original Message-----
From: Jan Kiszka [mailto:jan.kiszka@siemens.com]
Sent: Friday, February 8, 2019 8:53 AM
To: Hombourger, Cedric <Cedric_Hombourger@mentor.com>; isar-users@googlegroups.com
Subject: Re: [PATCH] wic-img: handle variables in .wks files
On 08.02.19 08:48, [ext] Jan Kiszka wrote:
> On 08.02.19 08:44, Hombourger, Cedric wrote:
>> I will double check but WICVARS are for variables you wish to export
>> to wic plugins This interface is for variables we would to make
>> available inside .wks files
>
> There is no WKSVARS in OE, while you can use variables, see e.g.
> scripts/lib/wic/canned-wks/directdisk.wks.
>
Sorry, I meant scripts/lib/wic/canned-wks/efi-bootdisk.wks.in.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2019-02-08 7:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 7:02 Cedric Hombourger
2019-02-08 7:42 ` Jan Kiszka
2019-02-08 7:44 ` Hombourger, Cedric
2019-02-08 7:48 ` Jan Kiszka
2019-02-08 7:53 ` Jan Kiszka
2019-02-08 7:55 ` Hombourger, Cedric [this message]
2019-02-08 11:32 ` Hombourger, Cedric
2019-02-08 13:50 ` Hombourger, Cedric
2019-02-08 19:13 ` [PATCH v2] wic-img: import support for .wks.in files from oe-core Cedric Hombourger
2019-02-15 17:43 ` Maxim Yu. Osipov
2019-02-08 14:28 ` [PATCH] wic-img: handle variables in .wks files Henning Schild
2019-02-08 14:31 ` Hombourger, Cedric
2019-02-08 14:31 ` Jan Kiszka
2019-02-08 16:27 ` Henning Schild
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=211b85d81663465abfa192d0da5c841c@svr-ies-mbx-02.mgc.mentorg.com \
--to=cedric_hombourger@mentor.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
/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