public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: i shyneee <ishyneee1@gmail.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: SDK seems to be detached from rootfs, or How to package ROS 2?
Date: Thu, 16 Jul 2026 03:44:19 -0700 (PDT)	[thread overview]
Message-ID: <cbc3047c-8d12-444b-993d-d0c3f728d319n@googlegroups.com> (raw)
In-Reply-To: <1226141c-c35d-49b1-84fd-2682883393cdn@googlegroups.com>


[-- Attachment #1.1: Type: text/plain, Size: 1949 bytes --]

What also seems possible is to set HOST_ARCH=DISTRO_ARCH, and use the 
resulting SDK as sysroot for external cross compiler.

четверг, 16 июля 2026 г. в 11:10:51 UTC+3, i shyneee: 

> Hello!
>
> In build systems I've seen SDK comprises separate host tools and sysroot. 
> Isar chose the multiarch approach. So I'm asking you to clarify:
> 1) that I must put "*-dev" packages in SDK_PREINSTALL in order for them to 
> be available to the cross-compiler;
> 2) that there is no detached "sysroot" format available.
>
> I'm currently trying to install ROS 2 arm64 package to my SDK:
> SDK_PREINSTALL += "\
>     ros-lyrical-ros-base:${DISTRO_ARCH}"
> The problem is that it depends on "python3-pytest:arm64". "python3-pytest" 
> package has "Architecture: all" but not "Multi-Arch: foreign". So it is 
> not available with ":arm64" postfix. I'm currently considering 
> investigating two approaches:
> 1) fake packages with equivs;
> 2) self-packaging like in "siemens/isar-riscv".
>
> Additional note:
> The multiarch SDK approach also is also preventing me from
> SDK_PREINSTALL += "\
>     ros-lyrical-ros-base \
>     ros-lyrical-ros-base:${DISTRO_ARCH}"
> due to lack of proper multiarch support in ROS 2. 
>
> So I can't use it as Docker rootfs container (I want it to carry ROS 2 for 
> both architectures - one for host user, one for cross-compilation). I can 
> just add the SDK to a directory in the container and call 
> "./relocate_sdk.sh". But why do I have to carry the whole amd64 rootfs 
> instead of aarch64 sysroot only?
>

-- 
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/cbc3047c-8d12-444b-993d-d0c3f728d319n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 2577 bytes --]

      reply	other threads:[~2026-07-16 10:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-15 17:14 i shyneee
2026-07-16 10:44 ` i shyneee [this message]

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=cbc3047c-8d12-444b-993d-d0c3f728d319n@googlegroups.com \
    --to=ishyneee1@gmail.com \
    --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