public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Srinuvasan Arjunan <srinuvasan_a@mentor.com>,
	isar-users@googlegroups.com
Cc: amikan@ilbers.de, Srinuvasan A <srinuvasan.a@siemens.com>
Subject: Re: [PATCH] crossvars.bbclass: use d.appendVar instead of d.setVar for SDK_TOOLCHAIN variable
Date: Mon, 22 May 2023 07:54:47 +0200	[thread overview]
Message-ID: <46a03938-0343-4221-a57c-efba80b27c83@siemens.com> (raw)
In-Reply-To: <f18f48e8-f834-a7e5-2756-1136608ed2de@siemens.com>

On 22.05.23 07:16, 'Jan Kiszka' via isar-users wrote:
> On 22.05.23 06:41, Srinuvasan Arjunan wrote:
>> From: Srinuvasan A <srinuvasan.a@siemens.com>
>>
>> In downstream layer we may override the sdk_toolchain, but this not works as
>> expected in latest ISAR, the reason behind this as they moved toolchain
>> selection into python Anonymous function.
> 
> Dod you want to append or do you want to replac SDK_TOOLCHAIN in
> downstream? In the latter case, we likely rather want to make our
> assignment in isar weak, no?
> 
> if not d.getVar('SDK_TOOLCHAIN'):
>     ...
> 

Also to answer: Why is SDK_PREINSTALL insufficient for your customization?

Jan

-- 
Siemens AG, Technology
Competence Center Embedded Linux


  reply	other threads:[~2023-05-22  5:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-22  4:41 Srinuvasan Arjunan
2023-05-22  5:16 ` Jan Kiszka
2023-05-22  5:54   ` Jan Kiszka [this message]
2023-05-25  4:53     ` Srinuvasan Arjunan
2023-05-25 10:20       ` Jan Kiszka
2023-05-26  9:03         ` Srinuvasan Arjunan
2023-06-04  9:32     ` [PATCH] meta/classes/crossvars: move sdk toolchain selection from python block Srinuvasan Arjunan
2023-06-05  7:00       ` Jan Kiszka
2023-06-05  7:07         ` Srinuvasan Arjunan
2023-06-05  7:18           ` Jan Kiszka
2023-06-05  7:43             ` Srinuvasan Arjunan

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=46a03938-0343-4221-a57c-efba80b27c83@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=amikan@ilbers.de \
    --cc=isar-users@googlegroups.com \
    --cc=srinuvasan.a@siemens.com \
    --cc=srinuvasan_a@mentor.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