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; Tue, 18 Mar 2025 12:27:37 +0100 X-Sieve: CMU Sieve 2.4 Received: from mail-qv1-f58.google.com (mail-qv1-f58.google.com [209.85.219.58]) by shymkent.ilbers.de (8.15.2/8.15.2/Debian-8+deb9u1) with ESMTPS id 52IBRaAR021891 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Tue, 18 Mar 2025 12:27:36 +0100 Received: by mail-qv1-f58.google.com with SMTP id 6a1803df08f44-6eb1e240eddsf10966596d6.0 for ; Tue, 18 Mar 2025 04:27:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20230601; t=1742297250; x=1742902050; 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=/kXNpmcOlGiact6KHokeIGo6kGCXxUiJBhXGlUz+sNQ=; b=BUZNb23Qke+xjO+nm17ULl6HogIKL9KMzNxeNqD7eHeCo0OZFYytLhGn0F2iOG0aZa oOdehpX96QYJSXTT2jBtXm6UcCjePSCmQv8dw1UPALkDsDjwsNWzldcRqbXUK9dSxO/O B4jUqSI6G+Wov9Exft/jn4ojvIUiOS74CoUd7OWgXK1Tj8/SoJlc9+6F+gTYAYBAOwpV uUy8EMQYzWc64v1Q2fVay7gn+vhZ752LLbGSXQPEqHzjPfkuzHG3PHMv1WhpNy4rwNp/ FPRFvf2exW8oml4ThwrCo6+4SeKUw31+9mZu19pGuJxHakA7yqJJ8VhlF2d7B+eqq1YQ irfw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1742297250; x=1742902050; 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=/kXNpmcOlGiact6KHokeIGo6kGCXxUiJBhXGlUz+sNQ=; b=AVQdkMMPco6heYsLbVVn/UpjU9/4gmzbRk+oaIQXETbrVX0lkHN/jsecpyOR+hmSaG wztD2iPVSlTyI9LfeH4+czXflJ+8mSFl9FJwRkfUiywVwy4PrhlwmcM8YbQ9T++ygxTv GbCixfP+O+EYa7m4OHMC5TNmEGzLjY5ncajEmsPjOZeq+1/ls9Tg9obBmdI6mhXLZubA hFsMVYwH2aAICfCcP5rYQZM9IRow+DoVGCz8hOUOvfU+omCMWf2r2mjZzZ5q7bKYrzd8 EYPAg+iZ7G8qIP65r2DuuTMp3QBhw4oXYfsLNUNiuA4wHsowNa2VSITh9Ji7lIxC2i0d 5m1Q== X-Forwarded-Encrypted: i=1; AJvYcCUQE5czMrukRuSxlLPnyHHFamllcCxJoV8n3yTn4RaP2O57BXsD8Ifv0vyWMUQjwuF9Byxs@ilbers.de X-Gm-Message-State: AOJu0YynOhuuk77xQrAxN0PtNnr+wdiD2y1gABxjNTHFLwrluXOac09m 5uP798cQsRdg+TzBJyAk+5Bu2I4wF8yEyqXY5i/eJNIa4biBIiSd X-Google-Smtp-Source: AGHT+IEEjdsuAdE3SE8meZFh63iCynJvARdhS40nNwXaonIH4UNPCOH3xvhMGL28xKRBzg6blygD6Q== X-Received: by 2002:a05:6214:1d04:b0:6e8:fb94:b9bf with SMTP id 6a1803df08f44-6eaea9ee3femr277632766d6.4.1742297250272; Tue, 18 Mar 2025 04:27:30 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com; h=ARLLPAIkAbLvhytaM49PwK/RMiIbr1F6fNIDz/5Vta33Luijyw== Received: by 2002:a0c:c601:0:b0:6e8:9021:8d0d with SMTP id 6a1803df08f44-6eadbce4802ls25455866d6.1.-pod-prod-05-us; Tue, 18 Mar 2025 04:27:29 -0700 (PDT) X-Received: by 2002:a05:620a:27c4:b0:7c5:4caa:21a4 with SMTP id af79cd13be357-7c57c8fc42fmr2881870785a.55.1742297249002; Tue, 18 Mar 2025 04:27:29 -0700 (PDT) Date: Tue, 18 Mar 2025 04:27:28 -0700 (PDT) From: "'Antoine Petty' via isar-users" To: isar-users Message-Id: <3daa7f3f-1a95-4fed-bcdc-5251908c776fn@googlegroups.com> In-Reply-To: <14f3f83b-6203-4a64-b8cd-fbca580a8144@siemens.com> References: <24a6acdd-1c3f-40dd-8af8-0131e321bb53n@googlegroups.com> <839787e9-60f2-407d-b0e3-0a83d684de83@siemens.com> <87fad003-18d2-4449-b003-c9d0798e6e49n@googlegroups.com> <4bb71134-721d-4eec-9a17-fbbd693c1d58n@googlegroups.com> <14f3f83b-6203-4a64-b8cd-fbca580a8144@siemens.com> Subject: Re: SDK Container for app development is missing some applications MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_49766_1595155969.1742297248663" 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: YgsKGLPhq/V3 ------=_Part_49766_1595155969.1742297248663 Content-Type: multipart/alternative; boundary="----=_Part_49767_1047320670.1742297248663" ------=_Part_49767_1047320670.1742297248663 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable For ISAR, it looks like I'm using a patched version of this 2022 commit at= =20 the moment=20 https://github.com/ilbers/isar/commit/20af1e2798353b118fc3538da0d4cdd886610= 1d5=20 but due to upgrade to something more recent. The `log.do_populate_sdk` file for this image recipe contains: ``` DEBUG: Executing shell function do_populate_sdk umount:=20 /workspace/project/build/tmp/deploy/sdkchroot/debian-bullseye-armhf/dev:=20 not mounted umount:=20 /workspace/project/build/tmp/deploy/sdkchroot/debian-bullseye-armhf/proc:= =20 not mounted. umount:=20 /workspace/project/build/tmp/deploy/sdkchroot/debian-bullseye-armhf/sys:=20 not mounted find:=20 '/workspace/project/build/tmp/deploy/sdkchroot/debian-bullseye-armhf/root':= =20 Permission denied find:=20 '/workspace/project/build/tmp/deploy/sdkchroot/debian-bullseye-armhf/etc/ss= l/private':=20 Permission denied find:=20 '/workspace/project/build/tmp/deploy/sdkchroot/debian-bullseye-armhf/var/ca= che/ldconfig':=20 Permission denied find:=20 '/workspace/project/build/tmp/deploy/sdkchroot/debian-bullseye-armhf/var/ca= che/apt/archives/partial':=20 Permission denied NOTE: Generating SDK container in docker-archive format DEBUG: prepare OCI container image skeleton DEBUG: pack container image DEBUG: Creating container image type: docker-archive DEBUG: Converting OCI image to docker-archive Getting image source signatures Copying blob sha256:[hash] Copying config sha256:[hash] Writing manifest to image destination Storing signatures DEBUG: Compressing image DEBUG: Shell function do_populate_sdk finished ``` so it's interesting that there are so many errors here when it's looks=20 happy during the build! On Monday, March 17, 2025 at 3:38:54=E2=80=AFPM UTC Jan Kiszka wrote: > On 17.03.25 11:38, 'Antoine Petty' via isar-users wrote: > > For extra context, I'm using the `ghcr.io/siemens/kas/kas-isar:3.1`=20 > > > image to build the SDK in case that's relevant > > Fairly old - but it should not explain the effect you are seeing. > > >=20 > > On Monday, March 17, 2025 at 10:33:59=E2=80=AFAM UTC Antoine Petty wrot= e: > >=20 > > Thanks Jan, I've given that a go but it doesn't seem to have made a > > difference. > >=20 > > I now have e.g. > > ``` > > SDK_PREINSTALL +=3D "cmake" > > SDK_PREINSTALL +=3D "cmake:${DISTRO_ARCH}" > > ``` > > for all the SDK libraries I'm specifying > >=20 > > When I use `bitbake -e`, `SDK_PREINSTALL=3D` includes e.g. `... cmake > > cmake:armhf ... libboost-all-dev libboost-all-dev:armhf ...`. > > But when spinning 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 needed 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? > > Did you look into the installation logs of the SDK images? Should be > log.do_populate_sdk inside the target image recipe's workdir - IIRC. > > BTW, how old is your isar revision? Not that we are hunting issues that > might have been fixed meanwhile (that meta-iot2050 layer is using a > fairly recent isar). > > Jan > > >=20 > > The kas file is pointing to `debug-image` which I understand as > > being the debug-image.bb file, which > > includes debug.inc where I'm adding these changes. > >=20 > > Don't suppose you have any other ideas? > >=20 > > Thanks > > Antoine > >=20 > > On Friday, March 14, 2025 at 5:49:44=E2=80=AFPM UTC Jan Kiszka wrote: > >=20 > > On 14.03.25 17:49, 'Antoine Petty' via isar-users wrote: > > > Hi all > > > > > > I'm familiar with Yocto but fairly new to using ISAR. > > > > > > 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 > > additional > > > tools such as cmake.=20 > > > It has included Boost for the host architecture but not for > > the target > > > architecture - I was expecting the target architecture > > libraries as well > > > so that I could cross-compile my application? > > > > > > 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 > > > ``` > > > > > > 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 > > this > > > variable. > > > > > > So in summary, I have two problems: > > > > > > 1. Missing tools specified in `SDK_PREINSTALL` > > > 2. Missing cross-compiled dependencies such as Boost > > > > > > Am I doing something wrong or misunderstanding how this works? > > > > > > Thank you :) > > > > >=20 > > When cross-compiling, you will generally have to specific the > > arch for > > the extra SDK dev packages. See e.g. here: > >=20 > > https://github.com/siemens/meta-iot2050/blob/ > > bb0721efdaa67aee7702aacef6f5709d7a0b33bb/conf/distro/iot2050- > > debian.conf#L35 > bb0721efdaa67aee7702aacef6f5709d7a0b33bb/conf/distro/iot2050- > > debian.conf#L35> > >=20 > > It that also does not help, check via "bitbake -e" which value > > SDK_PREINSTALL actually gets assigned in the end. > >=20 > > Jan > >=20 > > --=20 > > Siemens AG, Foundational Technologies > > 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 email to isar-users+...@googlegroups.com > users+un...@googlegroups.com>. > > To view this discussion visit https://groups.google.com/d/msgid/isar- > > users/4bb71134-721d-4eec-9a17-fbbd693c1d58n%40googlegroups.com > groups.google.com/d/msgid/isar-users/4bb71134-721d-4eec-9a17- > > fbbd693c1d58n%40googlegroups.com?utm_medium=3Demail&utm_source=3Dfooter= >. > > > --=20 > Siemens AG, Foundational Technologies > Linux Expert Center > --=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/= 3daa7f3f-1a95-4fed-bcdc-5251908c776fn%40googlegroups.com. ------=_Part_49767_1047320670.1742297248663 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable For ISAR, it looks like I'm using a patched version of this 2022 commit at = the moment https://github.com/ilbers/isar/commit/20af1e2798353b118fc3538da0= d4cdd8866101d5 but due to upgrade to something more recent.

The `log.do_populate_sdk` file for this image recipe contains:
<= div>```
DEBUG: Executing shell function do_populate_sdk
umou= nt: /workspace/project/build/tmp/deploy/sdkchroot/debian-bullseye-armhf/dev= : not mounted
umount: /workspace/project/build/tmp/deploy/sdkchroot/de= bian-bullseye-armhf/proc: not mounted.
umount: /workspace/project/buil= d/tmp/deploy/sdkchroot/debian-bullseye-armhf/sys: not mounted
find: '/= workspace/project/build/tmp/deploy/sdkchroot/debian-bullseye-armhf/root': P= ermission denied
find: '/workspace/project/build/tmp/deploy/sdkchroot/= debian-bullseye-armhf/etc/ssl/private': Permission denied
find: '/work= space/project/build/tmp/deploy/sdkchroot/debian-bullseye-armhf/var/cache/ld= config': Permission denied
find: '/workspace/project/build/tmp/deploy/= sdkchroot/debian-bullseye-armhf/var/cache/apt/archives/partial': Permission= denied
NOTE: Generating SDK container in =C2=A0docker-archive format<= br />DEBUG: prepare OCI container image skeleton
DEBUG: pack container= image
DEBUG: Creating container image type: docker-archive
DEBUG= : Converting OCI image to docker-archive
Getting image source signatur= es
Copying blob sha256:[hash]
Copying config sha256:[hash]
W= riting manifest to image destination
Storing signatures
DEBUG: Co= mpressing image
DEBUG: Shell function do_populate_sdk finished
```
so it's interesting that there are so many errors he= re when it's looks happy during the build!
=
On Monday, March 17, 2025 at 3:38:54= =E2=80=AFPM UTC Jan Kiszka wrote:
On 17.03.25 11:38, 'Antoine Petty' via isar-us= ers wrote:
> For extra context, I'm using the `ghcr.io/siemens/kas/kas-isar:3.1`
> image to build the SDK in case that's relevant

Fairly old - but it should not explain the effect you are seeing.

>=20
> On Monday, March 17, 2025 at 10:33:59=E2=80=AFAM UTC Antoine Petty= wrote:
>=20
> Thanks Jan, I've given that a go but it doesn't seem t= o have made a
> difference.
>=20
> I now have e.g.
> ```
> SDK_PREINSTALL +=3D "cmake"
> SDK_PREINSTALL +=3D "cmake:${DISTRO_ARCH}"
> ```
> for all the SDK libraries I'm specifying
>=20
> When I use `bitbake -e`, `SDK_PREINSTALL=3D` includes e.g. `..= .=C2=A0cmake
> cmake:armhf ... libboost-all-dev libboost-all-dev:armhf ...`.
> But when spinning that up into a container, cmake isn't in= stalled at
> all and it still looks like only the host version of boost is = in the
> container. It also needed me to bump the PR in the include fil= e to
> recognise there were changes so perhaps that's a symptom o= f
> something not being picked up?

Did you look into the installation logs of the SDK images? Should be
log.do_populate_sdk inside the target image recipe's workdir - IIRC= .

BTW, how old is your isar revision? Not that we are hunting issues that
might have been fixed meanwhile (that meta-iot2050 layer is using a
fairly recent isar).

Jan

>=20
> The kas file is pointing to `debug-image` which I understand a= s
> being the debug-image.bb <http://debug-image.bb> file, which
> includes debug.inc where I'm adding these changes.
>=20
> Don't suppose you have any other ideas?
>=20
> Thanks
> Antoine
>=20
> On Friday, March 14, 2025 at 5:49:44=E2=80=AFPM UTC Jan Kiszka= wrote:
>=20
> On 14.03.25 17:49, 'Antoine Petty' via isar-users = wrote:
> > Hi all
> >
> > I'm familiar with Yocto but fairly new to using I= SAR.
> >
> > I am able to create a containerised SDK file system w= hich
> includes the
> > libraries I'm using e.g. Boost but seems to be mi= ssing the
> additional
> > tools such as cmake.=C2=A0
> > It has included Boost for the host architecture but n= ot for
> the target
> > architecture - I was expecting the target architectur= e
> libraries as well
> > so that I could cross-compile my application?
> >
> > I'm using KAS and my target recipe has the follow= ing:
> > ```
> > 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 to= ols
> > ```
> >
> > When checking my environment with bitbake I can see
> > `DISTRO_ARCH=3D"armhf"`. I can see my conta= iner has the g++ etc
> cross-
> > compilers for this architecture which I assume is tri= ggered by
> this
> > variable.
> >
> > So in summary, I have two problems:
> >
> > 1. Missing tools specified in `SDK_PREINSTALL`
> > 2. Missing cross-compiled dependencies such as Boost
> >
> > Am I doing something wrong or misunderstanding how th= is works?
> >
> > Thank you :)
> >
>=20
> When cross-compiling, you will generally have to specific = the
> arch for
> the extra SDK dev packages. See e.g. here:
>=20
> https://github.com/siemens/meta-iot2050/blob/
> bb0721efdaa67aee7702aacef6f5709d7a0b33bb/conf/distro/iot20= 50-
> debian.conf#L35 <https://github.com/siemens/meta-iot2050/blob/<= /a>
> bb0721efdaa67aee7702aacef6f5709d7a0b33bb/conf/distro/iot20= 50-
> debian.conf#L35>
>=20
> It that also does not help, check via "bitbake -e&quo= t; which value
> SDK_PREINSTALL actually gets assigned in the end.
>=20
> Jan
>=20
> --=20
> Siemens AG, Foundational Technologies
> 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 email to isar-users+= ...@googlegroups.com <mailto:isar-
> users+un...@googlegroup= s.com>.
> To view this discussion visit https://groups.google.com/d/msgid/isar-
> users/4bb71134-721d-4eec-9a17-fbbd693c1d58n%40googlegroups.com <https://
> groups.google.com/d/msgid/is= ar-users/4bb71134-721d-4eec-9a17-
> fbbd693c1d58n%40googlegroups.= com?utm_medium=3Demail&utm_source=3Dfooter>.


--=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/3daa7f3f-1a95-4fed-bcdc-5251908c776fn%40googlegroups.com.
------=_Part_49767_1047320670.1742297248663-- ------=_Part_49766_1595155969.1742297248663--