public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: Antoine Petty <antoine.petty@siemens.com>,
	isar-users <isar-users@googlegroups.com>
Subject: Re: SDK Container for app development is missing some applications
Date: Fri, 14 Mar 2025 18:49:35 +0100	[thread overview]
Message-ID: <839787e9-60f2-407d-b0e3-0a83d684de83@siemens.com> (raw)
In-Reply-To: <24a6acdd-1c3f-40dd-8af8-0131e321bb53n@googlegroups.com>

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. 
> 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 = "1"
> ISAR_CROSS_COMPILE = "1"
> SDK_FORMATS = "docker-archive"
> SDK_PREINSTALL += "cmake"
> SDK_PREINSTALL += "libboost-all-dev"
> SDK_PREINSTALL += ...several other libraries and tools
> ```
> 
> When checking my environment with bitbake I can see
> `DISTRO_ARCH="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 :)
> 

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/bb0721efdaa67aee7702aacef6f5709d7a0b33bb/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

-- 
Siemens AG, Foundational Technologies
Linux Expert Center

-- 
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+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/839787e9-60f2-407d-b0e3-0a83d684de83%40siemens.com.

  reply	other threads:[~2025-03-14 17:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-14 16:49 'Antoine Petty' via isar-users
2025-03-14 17:49 ` 'Jan Kiszka' via isar-users [this message]
2025-03-17 10:33   ` 'Antoine Petty' via isar-users
2025-03-17 10:38     ` 'Antoine Petty' via isar-users
2025-03-17 15:38       ` 'Jan Kiszka' via isar-users
2025-03-18 11:27         ` 'Antoine Petty' via isar-users
2025-03-18 21:47           ` 'Jan Kiszka' via isar-users

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=839787e9-60f2-407d-b0e3-0a83d684de83@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=antoine.petty@siemens.com \
    --cc=jan.kiszka@siemens.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