public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Anton Mikanovich <amikan@ilbers.de>, <isar-users@googlegroups.com>
Subject: Re: [PATCH] sdk: always depend on crossbuild-essential for riscv64
Date: Fri, 17 Jun 2022 15:43:27 +0200	[thread overview]
Message-ID: <68c56647-aeee-cf67-8a9e-c74443957cde@siemens.com> (raw)
In-Reply-To: <20220617092818.14063-1-amikan@ilbers.de>

On 17.06.22 11:28, Anton Mikanovich wrote:
> If we add crossbuild-essential-riscv64 package to ROOTFS_PACKAGES
> unconditionally we should also depend on it even if ISAR_CROSS_COMPILE
> is set to "0". SDK creation will fail otherwise.
> 
> Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
> ---
>  meta/classes/sdk.bbclass | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta/classes/sdk.bbclass b/meta/classes/sdk.bbclass
> index 38671bb..1fc7b14 100644
> --- a/meta/classes/sdk.bbclass
> +++ b/meta/classes/sdk.bbclass
> @@ -58,7 +58,7 @@ IMAGE_FSTYPES_class-sdk = "${SDK_FORMATS}"
>  
>  # bitbake dependencies
>  SDKDEPENDS += "sdk-files ${SDK_INSTALL}"
> -SDKDEPENDS_append_riscv64 = "${@' crossbuild-essential-riscv64' if d.getVar('ISAR_CROSS_COMPILE', True) == '1' and d.getVar('PN') != 'crossbuild-essential-riscv64' else ''}"
> +SDKDEPENDS_append_riscv64 = "crossbuild-essential-riscv64"
>  DEPENDS_class-sdk = "${SDKDEPENDS}"

I don't think this is correct. What if we compile a native SDK for
RISC-V? Then we surely don't install crossbuild packages.

Jan

-- 
Siemens AG, Technology
Competence Center Embedded Linux

  reply	other threads:[~2022-06-17 13:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17  9:28 Anton Mikanovich
2022-06-17 13:43 ` Jan Kiszka [this message]
2022-06-17 16:21   ` Anton Mikanovich
2022-06-21 12:53   ` Anton Mikanovich

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=68c56647-aeee-cf67-8a9e-c74443957cde@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=amikan@ilbers.de \
    --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