public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Silvano Cirujano Cuesta <silvano.cirujano-cuesta@siemens.com>
To: Jan Kiszka <jan.kiszka@siemens.com>,
	Henning Schild <henning.schild@siemens.com>
Cc: isar-users@googlegroups.com
Subject: Re: [RFC PATCH 1/2] sdk: support creation of container image
Date: Tue, 12 Jan 2021 18:08:12 +0100	[thread overview]
Message-ID: <aad9fd1a-f99d-e665-31bb-6643ad575e5d@siemens.com> (raw)
In-Reply-To: <27f5d2ac-dc78-2d08-1611-0373ecae16a0@siemens.com>


On 12/01/2021 15:50, Jan Kiszka wrote:
> On 12.01.21 12:50, [ext] Silvano Cirujano Cuesta wrote:
>> On 12/01/2021 12:36, Henning Schild wrote:
>>> Am Tue, 12 Jan 2021 11:33:37 +0100
>>> schrieb "[ext] Silvano Cirujano Cuesta"
>>> <silvano.cirujano-cuesta@siemens.com>:
>>>
>>>> Extend task "populate_sdk" to support the creation of a container
>>>> image containing the SDK.
>>>>
>>>> Signed-off-by: Silvano Cirujano Cuesta
>>>> <silvano.cirujano-cuesta@siemens.com> ---
>>>>  meta/classes/image-sdk-extension.bbclass | 99
>>>> ++++++++++++++++++++++-- 1 file changed, 92 insertions(+), 7
>>>> deletions(-)
>>>>
>>>> diff --git a/meta/classes/image-sdk-extension.bbclass
>>>> b/meta/classes/image-sdk-extension.bbclass index a8c708a..9317256
>>>> 100644 --- a/meta/classes/image-sdk-extension.bbclass
>>>> +++ b/meta/classes/image-sdk-extension.bbclass
>>>> @@ -6,10 +6,77 @@
>>>>  # This class extends the image.bbclass to supply the creation of a
>>>> sdk 
>>>>  SDK_INCLUDE_ISAR_APT ?= "0"
>>>> +SDK_GENERATE_FORMATS = "${@d.getVar("SDK_FORMATS", "tar")}"
>>> I do not understand why there are two variables, maybe one is enough.
>>> And i think a ?= assignment would be a better choice here.
>> Probably lack of ISAR expersite... I don't know why using
>>
>> SDK_FORMATS = "${@d.getVar("SDK_FORMATS", "tar")}"
>>
>> fails. I've also tried
>>
>> SDK_FORMATS ?= "tar"
>>
>> and failed.
> How did it fail - because this is how it should look like.
Using `SDK_FORMATS ?= "tar"` and not providing any value for SDK_FORMATS (so using the default), `bitbake -e` doesn't show SDK_FORMATS at all and therefore I thought it was failing.

I've retried with `SDK_FORMATS ?= "tar"` and it works. I'll fix it.

  Silvano

>
> Jan
>
-- 
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux


  reply	other threads:[~2021-01-12 17:08 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-12 10:33 [RFC PATCH 0/2] support generation of sdk container images Silvano Cirujano Cuesta
2021-01-12 10:33 ` [RFC PATCH 1/2] sdk: support creation of container image Silvano Cirujano Cuesta
2021-01-12 11:36   ` Henning Schild
2021-01-12 11:50     ` Silvano Cirujano Cuesta
2021-01-12 14:50       ` Jan Kiszka
2021-01-12 17:08         ` Silvano Cirujano Cuesta [this message]
2021-01-12 17:36   ` Henning Schild
2021-01-12 17:54     ` Silvano Cirujano Cuesta
2021-01-12 18:04       ` Jan Kiszka
2021-01-12 20:46         ` Silvano Cirujano Cuesta
2021-01-12 10:33 ` [RFC PATCH 2/2] docs: document usage of sdk container images Silvano Cirujano Cuesta
2021-01-12 11:40   ` Henning Schild
2021-01-12 12:03     ` Silvano Cirujano Cuesta
2021-01-12 12:18       ` Henning Schild
2021-01-12 14:52         ` Silvano Cirujano Cuesta
2021-01-12 14:56           ` Jan Kiszka
2021-01-12 15:12             ` Silvano Cirujano Cuesta
2021-01-12 15:14               ` Jan Kiszka
2021-01-12 15:11           ` Henning Schild
2021-01-12 16:26             ` Silvano Cirujano Cuesta
2021-01-14 13:56 ` [RFC PATCH 0/2] support generation " Silvano Cirujano Cuesta
2021-01-14 18:32   ` Henning Schild
2021-01-15  8:11     ` Silvano Cirujano Cuesta
2021-01-15  7:09   ` Jan Kiszka
2021-01-15  8:16     ` Silvano Cirujano Cuesta

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=aad9fd1a-f99d-e665-31bb-6643ad575e5d@siemens.com \
    --to=silvano.cirujano-cuesta@siemens.com \
    --cc=henning.schild@siemens.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