public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "srinuvasan.a via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com
Cc: jan.kiszka@siemens.com, Srinuvasan A <srinuvasan.a@siemens.com>
Subject: [PATCH v1] doc/user_manual.md: update ISAR_CROSS_COMPILE variable in SDK part
Date: Fri, 30 Aug 2024 05:51:57 +0530	[thread overview]
Message-ID: <20240830002157.839116-1-srinuvasan.a@siemens.com> (raw)
In-Reply-To: <74db4b29-879c-45f7-84d9-bc9ca77e1ac1@siemens.com>

From: Srinuvasan A <srinuvasan.a@siemens.com>

With the present documentation the SDK is not generated properly for
foreign architectures, basically SDK_TOOLCAHIN not picking the proper
toolchain due to mode is not properly set for foreign architecture.

Set ISAR_CROSS_COMPILE by 1 in local.conf to get the correct mode for
foreign architecture.

Update the path of scripts instead of relative path for accessing files
from isar directory.

Signed-off-by: Srinuvasan A <srinuvasan.a@siemens.com>
---
 doc/user_manual.md | 14 ++++++++++----
 1 file changed, 10 insertions(+), 4 deletions(-)

diff --git a/doc/user_manual.md b/doc/user_manual.md
index 575aa114..706c74bf 100644
--- a/doc/user_manual.md
+++ b/doc/user_manual.md
@@ -980,7 +980,7 @@ While isar is building the system, build statistics is collected in
 The collected statistics can be represented visually by using
 `pybootchartgui.py` script (borrowed from OpenEmbedded):
 ```
-../scripts/pybootchartgui/pybootchartgui.py tmp/buildstats/20210911054429/ -f pdf -o ~/buildstats.pdf
+<path-to-isar>/scripts/pybootchartgui/pybootchartgui.py tmp/buildstats/20210911054429/ -f pdf -o ~/buildstats.pdf
 ```
 
 NOTE: `python3-cairo` package is required for `pybootchartgui.py` to work:
@@ -1195,6 +1195,12 @@ One may chroot into the SDK and install required target packages with the help o
 
 ```
 SDK_INCLUDE_ISAR_APT = "1"
+```
+
+ - Set ISAR_CROSS_COMPILE by 1 for foreign architectures
+
+```
+ISAR_CROSS_COMPILE = "1"
 ```
 
  - Trigger creation of SDK root filesystem
@@ -1212,7 +1218,7 @@ sudo tar xf tmp/deploy/images/qemuarm/isar-image-base-sdk-debian-bullseye-qemuar
  - Mount the following directories in chroot by passing resulting rootfs as an argument to the script `mount_chroot.sh`:
 
 ```
-cat ../scripts/mount_chroot.sh
+cat <path-to-isar>/scripts/mount_chroot.sh
 #!/bin/sh
 
 set -e
@@ -1224,7 +1230,7 @@ mount devtmpfs $1/dev     -t devtmpfs -o mode=0755,nosuid
 mount devpts   $1/dev/pts -t devpts   -o gid=5,mode=620
 mount tmpfs    $1/dev/shm -t tmpfs    -o rw,seclabel,nosuid,nodev
 
-sudo ../scripts/mount_chroot.sh tmp/deploy/images/qemuarm/isar-image-base-sdk-debian-bullseye-qemuarm
+sudo <path-to-isar>/scripts/mount_chroot.sh tmp/deploy/images/qemuarm/isar-image-base-sdk-debian-bullseye-qemuarm
 
 ```
 
@@ -1277,7 +1283,7 @@ public nameserver like:
  - Unmount rootfs paths:
 
 ```
-sudo ../scripts/umount_chroot.sh tmp/deploy/images/qemuarm/isar-image-base-sdk-debian-bullseye-qemuarm
+sudo <path-to-isar>/scripts/umount_chroot.sh tmp/deploy/images/qemuarm/isar-image-base-sdk-debian-bullseye-qemuarm
 ```
 
 ## Create a containerized Isar SDK root filesystem
-- 
2.34.1

-- 
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 on the web visit https://groups.google.com/d/msgid/isar-users/20240830002157.839116-1-srinuvasan.a%40siemens.com.

  reply	other threads:[~2024-08-30  0:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-29 11:21 [PATCH] " srinuvasan.a via isar-users
2024-08-29 11:28 ` 'Jan Kiszka' via isar-users
2024-08-30  0:21   ` srinuvasan.a via isar-users [this message]
2024-09-06  5:57     ` [PATCH v1] " Uladzimir Bely

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=20240830002157.839116-1-srinuvasan.a@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.com \
    --cc=srinuvasan.a@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