From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from shymkent.ilbers.de ([unix socket]) by shymkent (Cyrus 2.5.10-Debian-2.5.10-3+deb9u2) with LMTPA; Mon, 17 Mar 2025 11:38:20 +0100 X-Sieve: CMU Sieve 2.4 Received: from mail-qk1-f192.google.com (mail-qk1-f192.google.com [209.85.222.192]) by shymkent.ilbers.de (8.15.2/8.15.2/Debian-8+deb9u1) with ESMTPS id 52HAcIJU014346 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Mon, 17 Mar 2025 11:38:19 +0100 Received: by mail-qk1-f192.google.com with SMTP id af79cd13be357-7c543ab40d3sf791032885a.2 for ; Mon, 17 Mar 2025 03:38:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20230601; t=1742207893; x=1742812693; darn=ilbers.de; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:reply-to:x-original-sender :mime-version:subject:references:in-reply-to:message-id:to:from:date :from:to:cc:subject:date:message-id:reply-to; bh=Q54pjJvLqTn4pHXCDGHm7WX11VM7AB7iXwE8mJsT+vg=; b=cCkg7vq9G4cWK2tLxI6RxSN+dMEwFLkbimMWw+TJg24Ai++ac+daRDqVNeeXqGBd1K ih4SkauhHGVnbtkri7kRlprH6CXsq7pXpdsY+O4hewEZO49lmMVmfPql94cWIzLP1Mg+ xEfa5jBWScuLDaR3jKpAnNu5xSRyddxIwLSaicEUmx0I72EnlNajEoyEWYHUbfz25OrA I0lk3qqpudsHktjidp9Ln+xuQ1mSLK20Gt2WmdeZ8lUNTZC4AqUGs/6w98x866ijbyAB qiI8bF1gkWexqlWrcJbT6PM0EqqV8APrDmeA60GSxqF7ZD3DEhAChZ7LQ96t9Go3oNAj mvLA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1742207893; x=1742812693; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :x-spam-checked-in-group:list-id:mailing-list:precedence:reply-to :x-original-sender:mime-version:subject:references:in-reply-to :message-id:to:from:date:x-beenthere:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=Q54pjJvLqTn4pHXCDGHm7WX11VM7AB7iXwE8mJsT+vg=; b=jBBxOD/CxhKxZnsYiELR+G/OEpqG7Lrr+x1xcInkgcV6HYmt5GuXzYMc7fMGVIuwpd jZc7TAZthmnbt6o0z6v1ewP+JhmqTUi3YeqZ+dOcV3+96wthqDYe6yvoNRrXHupUNmZs vFTBzgruGnmf4DiQ4v4s2yQjLUFVZJ7EigwASYtBN01eagRuK7vscOM2iWUTQOLq2A8O KrDesizl7ViIdouwt8rUDBkpr+abjX+yY7hD2sEFxfNtVny85TgsAvyWK71+NpkTVhup tWozo+k74pS+VSxXy5Rr+XitJUR0Nxx9Qpm7KfW1lq5YQKSAQVPo8dlg7Uj6pRhmA2ln FgeQ== X-Forwarded-Encrypted: i=1; AJvYcCVQR5YSJN9DKK2IVAN+id5EEsV2+E3f0RiPaA+9BqsYQwPjLfz9gwuWmgiOdQig1CVg0iTv@ilbers.de X-Gm-Message-State: AOJu0YzyGsG2ea0hspMkogO9ABFdTx6e+Ci9YkHgrQlSmVTICH7cceV3 Sq6OwsVQW/yke5SXd+83WDctToEcceuab4/A6589SGS28zZ84E7B X-Google-Smtp-Source: AGHT+IGAe12Z1qS41YXXuwgSj0GvNF2A9P0BB83P5LkHUN7+FMTWu3F/uH7r/1rmK39sLuXCqR+UZQ== X-Received: by 2002:a05:620a:468d:b0:7c5:562d:cd01 with SMTP id af79cd13be357-7c57c77826cmr1422786785a.16.1742207892777; Mon, 17 Mar 2025 03:38:12 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com; h=ARLLPAK9RDqFONTXxFnYSVX5cMFgrSO0OOEeC5TQN9gtMxgXjw== Received: by 2002:ac8:5756:0:b0:476:91a5:c821 with SMTP id d75a77b69052e-476b7dd0347ls80056431cf.2.-pod-prod-03-us; Mon, 17 Mar 2025 03:38:12 -0700 (PDT) X-Received: by 2002:a05:620a:191a:b0:7c5:4eee:53f8 with SMTP id af79cd13be357-7c57c8abb12mr1633770085a.41.1742207891798; Mon, 17 Mar 2025 03:38:11 -0700 (PDT) Date: Mon, 17 Mar 2025 03:38:11 -0700 (PDT) From: "'Antoine Petty' via isar-users" To: isar-users Message-Id: <4bb71134-721d-4eec-9a17-fbbd693c1d58n@googlegroups.com> In-Reply-To: <87fad003-18d2-4449-b003-c9d0798e6e49n@googlegroups.com> References: <24a6acdd-1c3f-40dd-8af8-0131e321bb53n@googlegroups.com> <839787e9-60f2-407d-b0e3-0a83d684de83@siemens.com> <87fad003-18d2-4449-b003-c9d0798e6e49n@googlegroups.com> Subject: Re: SDK Container for app development is missing some applications MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_254664_277878287.1742207891660" X-Original-Sender: antoine.petty@siemens.com X-Original-From: Antoine Petty Reply-To: Antoine Petty Precedence: list Mailing-list: list isar-users@googlegroups.com; contact isar-users+owners@googlegroups.com List-ID: X-Spam-Checked-In-Group: isar-users@googlegroups.com X-Google-Group-Id: 914930254986 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Status: No, score=-4.9 required=5.0 tests=DKIMWL_WL_MED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,HTML_MESSAGE,MAILING_LIST_MULTI, RCVD_IN_DNSWL_BLOCKED,RCVD_IN_MSPIKE_H2,RCVD_IN_RP_CERTIFIED, RCVD_IN_RP_RNBL,RCVD_IN_RP_SAFE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on shymkent.ilbers.de X-TUID: bAso1XOSchGf ------=_Part_254664_277878287.1742207891660 Content-Type: multipart/alternative; boundary="----=_Part_254665_27586285.1742207891660" ------=_Part_254665_27586285.1742207891660 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable For extra context, I'm using the `ghcr.io/siemens/kas/kas-isar:3.1` image= =20 to build the SDK in case that's relevant On Monday, March 17, 2025 at 10:33:59=E2=80=AFAM UTC Antoine Petty wrote: > Thanks Jan, I've given that a go but it doesn't seem to have made a=20 > difference. > > I now have e.g. > ``` > SDK_PREINSTALL +=3D "cmake" > SDK_PREINSTALL +=3D "cmake:${DISTRO_ARCH}" > ``` > for all the SDK libraries I'm specifying > > When I use `bitbake -e`, `SDK_PREINSTALL=3D` includes e.g. `... cmake=20 > cmake:armhf ... libboost-all-dev libboost-all-dev:armhf ...`. > But when spinning that up into a container, cmake isn't installed at all= =20 > and it still looks like only the host version of boost is in the containe= r.=20 > It also needed me to bump the PR in the include file to recognise there= =20 > were changes so perhaps that's a symptom of something not being picked up= ? > > The kas file is pointing to `debug-image` which I understand as being the= =20 > debug-image.bb file, which includes debug.inc where I'm adding these=20 > changes. > > Don't suppose you have any other ideas? > > Thanks > Antoine > > On Friday, March 14, 2025 at 5:49:44=E2=80=AFPM UTC Jan Kiszka wrote: > >> On 14.03.25 17:49, 'Antoine Petty' via isar-users wrote:=20 >> > Hi all=20 >> >=20 >> > I'm familiar with Yocto but fairly new to using ISAR.=20 >> >=20 >> > I am able to create a containerised SDK file system which includes the= =20 >> > libraries I'm using e.g. Boost but seems to be missing the additional= =20 >> > tools such as cmake. =20 >> > It has included Boost for the host architecture but not for the target= =20 >> > architecture - I was expecting the target architecture libraries as=20 >> well=20 >> > so that I could cross-compile my application?=20 >> >=20 >> > I'm using KAS and my target recipe has the following:=20 >> > ```=20 >> > SDK_INCLUDE_ISAR_APT =3D "1"=20 >> > ISAR_CROSS_COMPILE =3D "1"=20 >> > SDK_FORMATS =3D "docker-archive"=20 >> > SDK_PREINSTALL +=3D "cmake"=20 >> > SDK_PREINSTALL +=3D "libboost-all-dev"=20 >> > SDK_PREINSTALL +=3D ...several other libraries and tools=20 >> > ```=20 >> >=20 >> > When checking my environment with bitbake I can see=20 >> > `DISTRO_ARCH=3D"armhf"`. I can see my container has the g++ etc cross-= =20 >> > compilers for this architecture which I assume is triggered by this=20 >> > variable.=20 >> >=20 >> > So in summary, I have two problems:=20 >> >=20 >> > 1. Missing tools specified in `SDK_PREINSTALL`=20 >> > 2. Missing cross-compiled dependencies such as Boost=20 >> >=20 >> > Am I doing something wrong or misunderstanding how this works?=20 >> >=20 >> > Thank you :)=20 >> >=20 >> >> When cross-compiling, you will generally have to specific the arch for= =20 >> the extra SDK dev packages. See e.g. here:=20 >> >> >> https://github.com/siemens/meta-iot2050/blob/bb0721efdaa67aee7702aacef6f= 5709d7a0b33bb/conf/distro/iot2050-debian.conf#L35=20 >> >> It that also does not help, check via "bitbake -e" which value=20 >> SDK_PREINSTALL actually gets assigned in the end.=20 >> >> Jan=20 >> >> --=20 >> Siemens AG, Foundational Technologies=20 >> Linux Expert Center=20 >> > --=20 You received this message because you are subscribed to the Google Groups "= isar-users" group. To unsubscribe from this group and stop receiving emails from it, send an e= mail to isar-users+unsubscribe@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/isar-users/= 4bb71134-721d-4eec-9a17-fbbd693c1d58n%40googlegroups.com. ------=_Part_254665_27586285.1742207891660 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable For extra context, I'm using the `ghcr.io/siemens/kas/kas-isar:3.1` image t= o build the SDK in case that's relevant

On Monday, March 17, 2025 at 10:3= 3:59=E2=80=AFAM UTC Antoine Petty wrote:
Thanks Jan, I've given that a go but it doe= sn't seem to have made a difference.

I now have e.g.=
```
SDK_PREINSTALL +=3D "cmake"
SDK_PREIN= STALL +=3D "cmake:${DISTRO_ARCH}"
```
for all= the SDK libraries I'm specifying

When I use `= bitbake -e`, `SDK_PREINSTALL=3D` includes e.g. `...=C2=A0cmake cmake:armhf = ... libboost-all-dev libboost-all-dev:armhf ...`.
But when spinni= ng that up into a container, cmake isn't installed at all and it still = looks like only the host version of boost is in the container. It also need= ed me to bump the PR in the include file to recognise there were changes so= perhaps that's a symptom of something not being picked up?
<= br>
The kas file is pointing to `debug-image` which I understand = as being the debug-image.bb file, which includes de= bug.inc where I'm adding these changes.

Don= 9;t suppose you have any other ideas?

Thanks
=
Antoine

On Friday, March 14, 2025 at 5:49:44=E2= =80=AFPM UTC Jan Kiszka wrote:
On 14.03.25 17:49, 'Antoine Petty' via isar-users wrote:
> Hi all
>=20
> I'm familiar with Yocto but fairly new to using ISAR.
>=20
> I am able to create a containerised SDK file system which includes= the
> libraries I'm using e.g. Boost but seems to be missing the add= itional
> tools such as cmake.=C2=A0
> It has included Boost for the host architecture but not for the ta= rget
> architecture - I was expecting the target architecture libraries a= s well
> so that I could cross-compile my application?
>=20
> I'm using KAS and my target recipe has the following:
> ```
> SDK_INCLUDE_ISAR_APT =3D "1"
> ISAR_CROSS_COMPILE =3D "1"
> SDK_FORMATS =3D "docker-archive"
> SDK_PREINSTALL +=3D "cmake"
> SDK_PREINSTALL +=3D "libboost-all-dev"
> SDK_PREINSTALL +=3D ...several other libraries and tools
> ```
>=20
> When checking my environment with bitbake I can see
> `DISTRO_ARCH=3D"armhf"`. I can see my container has the = g++ etc cross-
> compilers for this architecture which I assume is triggered by thi= s
> variable.
>=20
> So in summary, I have two problems:
>=20
> 1. Missing tools specified in `SDK_PREINSTALL`
> 2. Missing cross-compiled dependencies such as Boost
>=20
> Am I doing something wrong or misunderstanding how this works?
>=20
> Thank you :)
>=20

When cross-compiling, you will generally have to specific the arch for
the extra SDK dev packages. See e.g. here:

https://github.com/siemens/meta-iot2050/blob/bb0721efdaa67aee7702aacef6f57= 09d7a0b33bb/conf/distro/iot2050-debian.conf#L35

It that also does not help, check via "bitbake -e" which valu= e
SDK_PREINSTALL actually gets assigned in the end.

Jan

--=20
Siemens AG, Foundational Technologies
Linux Expert Center

--
You received this message because you are subscribed to the Google Groups &= quot;isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to isar-use= rs+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-use= rs/4bb71134-721d-4eec-9a17-fbbd693c1d58n%40googlegroups.com.
------=_Part_254665_27586285.1742207891660-- ------=_Part_254664_277878287.1742207891660--