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:34:06 +0100 X-Sieve: CMU Sieve 2.4 Received: from mail-qv1-f61.google.com (mail-qv1-f61.google.com [209.85.219.61]) by shymkent.ilbers.de (8.15.2/8.15.2/Debian-8+deb9u1) with ESMTPS id 52HAY5Ow014273 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Mon, 17 Mar 2025 11:34:05 +0100 Received: by mail-qv1-f61.google.com with SMTP id 6a1803df08f44-6e91f6bb296sf82577866d6.1 for ; Mon, 17 Mar 2025 03:34:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20230601; t=1742207639; x=1742812439; 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=a4sQJS0nL4x8PxSd+dTlIckv7lCu98pJjbrIh0tNLT4=; b=iSbADqIKHHXf7u9X4XwoJLU1NupadlTvcNHZItv/sm+TxpxjEu2Vy4Ccajv1VA1/Y3 zu6NJ5kmBRAO7qYdW4RsTuVyPlKlSHAxPFmDDQ5XOUG0OvOQ8lWI0ign24Z0rWNAwoMS pVri4qdHgAk4zWWzoBhAlu7fUXt1+UA4pmV17OrLsYhK2yjotRuWsX2yV1SPHJnc0Lxg 9fVxbTsT7Ax8XoDCySOXFOpx92tKvEaIGfQXL9pci6e+TofLj73bn5mWc6Cqjo3GJnRz iSv0NanWeGAR4qv5RPdJq+H2zN9gfYkS9qNmcZAW1gxQrqSwntsPw5R+fLR1/p8jlCXP EtSQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1742207639; x=1742812439; 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=a4sQJS0nL4x8PxSd+dTlIckv7lCu98pJjbrIh0tNLT4=; b=aT2eIht5HoUjqt4tHxverJcRZtxI3K98FsLOHTvrjTnS06j6EGt613qPCfOF7ZnOXP L/BZmorRO4WeWNZXtIa90oevTq8i2Sw/8F/h79avdI49Mgs5BhFrNU3eTsUTMTWQTvdB 0L7nplkUoYZF0gZ5xx1vKDiAph1uk80JHqR8fBY2QexyCP32iyaqLjmcyP6PdXH14A3Q qI9PlcB2Ip5zTwvffRQkRx9XbvnzjQCPpRLTx+CxKTBxfBMONCHGs/8JRDf5yIVT1ko1 viGG5+mzS2l8LIu2Wq6s80XHXd/PI8K5CVv0tIL0bxpPK4Nq7p7IdXd+GN6noTll635Z 0dow== X-Forwarded-Encrypted: i=1; AJvYcCXveZ45Ahz/31jfQqm6Nbo9EnGQkSOWt0wUT3P8c8mS/J3I+pBcAsQ7Dcdie4aOMWKp0006@ilbers.de X-Gm-Message-State: AOJu0YyCfhpyRFOPvQrXF/EsfqjHlUV4fOARnRrrqzk13cnopAua94qt E3ulZ423ugqePw4byZxiuebLG5E0E3SYL7HU5+s9R3yFlnyyhVWx X-Google-Smtp-Source: AGHT+IELKRKLt+rmPZ14dOYhH68iUyPfNKorhZtswH+PNsVp2lb7lENVnP/qzCvL5dcSiOPqf3btCQ== X-Received: by 2002:ad4:5c4c:0:b0:6e8:ea29:fdd1 with SMTP id 6a1803df08f44-6eaea9f4500mr185925936d6.3.1742207639132; Mon, 17 Mar 2025 03:33:59 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com; h=ARLLPALpOfgxjIgJzykrq0V7bkrQB5qCPJMxDMhktDJcQVzQ5A== Received: by 2002:a0c:c601:0:b0:6e8:9021:8d0d with SMTP id 6a1803df08f44-6eadbce4802ls9798396d6.1.-pod-prod-05-us; Mon, 17 Mar 2025 03:33:58 -0700 (PDT) X-Received: by 2002:a05:620a:404b:b0:7c5:7a1f:4d89 with SMTP id af79cd13be357-7c57c8fb866mr2192252285a.54.1742207638257; Mon, 17 Mar 2025 03:33:58 -0700 (PDT) Date: Mon, 17 Mar 2025 03:33:58 -0700 (PDT) From: "'Antoine Petty' via isar-users" To: isar-users Message-Id: <87fad003-18d2-4449-b003-c9d0798e6e49n@googlegroups.com> In-Reply-To: <839787e9-60f2-407d-b0e3-0a83d684de83@siemens.com> References: <24a6acdd-1c3f-40dd-8af8-0131e321bb53n@googlegroups.com> <839787e9-60f2-407d-b0e3-0a83d684de83@siemens.com> Subject: Re: SDK Container for app development is missing some applications MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_253030_2105371220.1742207638103" 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=-2.2 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_PSBL, 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: 5haX+0422hWo ------=_Part_253030_2105371220.1742207638103 Content-Type: multipart/alternative; boundary="----=_Part_253031_418669149.1742207638103" ------=_Part_253031_418669149.1742207638103 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 container.= =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: > > 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 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 wel= l > > 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 this > > 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/bb0721efdaa67aee7702aacef6f5= 709d7a0b33bb/conf/distro/iot2050-debian.conf#L35 > > It that also does not help, check via "bitbake -e" which value > SDK_PREINSTALL actually gets assigned in the end. > > Jan > > --=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/= 87fad003-18d2-4449-b003-c9d0798e6e49n%40googlegroups.com. ------=_Part_253031_418669149.1742207638103 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks Jan, I've given that a go but it doesn't seem to have made a differe= nce.

I now have e.g.
```
SDK_PREIN= STALL +=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. `...=C2= =A0cmake 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 contai= ner. It also needed me to bump the PR in the include file to recognise ther= e were changes so perhaps that's a symptom of something not being picked up= ?

The kas file is pointing to `debug-image` whic= h I understand as being the debug-image.bb file, which includes debug.inc w= here I'm adding these changes.

Don't suppose you= have any other ideas?

Thanks
Antoine<= /div>

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/87fad003-18d2-4449-b003-c9d0798e6e49n%40googlegroups.com.
------=_Part_253031_418669149.1742207638103-- ------=_Part_253030_2105371220.1742207638103--