public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Srinuvasan Arjunan <srinuvasanasv@gmail.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] crossvars.bbclass: use d.appendVar instead of d.setVar for SDK_TOOLCHAIN variable
Date: Wed, 24 May 2023 21:53:50 -0700 (PDT)	[thread overview]
Message-ID: <86f59c50-3cd4-4465-b04c-db7c0aa0cee9n@googlegroups.com> (raw)
In-Reply-To: <46a03938-0343-4221-a57c-efba80b27c83@siemens.com>


[-- Attachment #1.1: Type: text/plain, Size: 1687 bytes --]



On Monday, May 22, 2023 at 11:24:53 AM UTC+5:30 Jan Kiszka wrote:

On 22.05.23 07:16, 'Jan Kiszka' via isar-users wrote: 
> On 22.05.23 06:41, Srinuvasan Arjunan wrote: 
>> From: Srinuvasan A <srinuv...@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

 

    yes we can append our toolchain via SDK_PREINSTALL, but i need to 
replace with the "crossbuild-essential-${COMPAT_DISTRO_ARCH}" , this one 
comes via SDK_TOOLCHAIN variable, if i append " gcc-multilib g++-multilib" 
without removing the crossbuild-essential am facing broken package problem.
Logs:

 Broken gcc-multilib:amd64 Conflicts on gcc-10-i686-linux-gnu:amd64 < none 
-> 10.2.1-6cross1 @un puN Ib >
 |   Considering gcc-10-i686-linux-gnu:amd64 1 as a solution to 
gcc-multilib:amd64 10001
 | Investigating (0) gcc-10-i686-linux-gnu:amd64 < none -> 10.2.1-6cross1 
@un puN Ib >

Eventually I need to remove crossbuild-essential, but this one will do via 
SDK_TOOLCHAIN remove override , but this does not work in the downstream 
layer, because always ISAR's python anonymous function wins and set its 
value.

Thanks,
Srinu 

[-- Attachment #1.2: Type: text/html, Size: 3002 bytes --]

  reply	other threads:[~2023-05-25  4:53 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
2023-05-25  4:53     ` Srinuvasan Arjunan [this message]
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=86f59c50-3cd4-4465-b04c-db7c0aa0cee9n@googlegroups.com \
    --to=srinuvasanasv@gmail.com \
    --cc=isar-users@googlegroups.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