From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com
Cc: Anton Mikanovich <amikan@ilbers.de>
Subject: [PATCH v2 4/4] doc/user_manual.md: Improve SDK usage howto
Date: Thu, 21 Dec 2023 12:31:42 +0200 [thread overview]
Message-ID: <20231221103142.47089-5-amikan@ilbers.de> (raw)
In-Reply-To: <20231221103142.47089-1-amikan@ilbers.de>
Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
---
doc/user_manual.md | 31 ++++++++++++++++++++++++++++---
1 file changed, 28 insertions(+), 3 deletions(-)
diff --git a/doc/user_manual.md b/doc/user_manual.md
index 3744c753..2eb97647 100644
--- a/doc/user_manual.md
+++ b/doc/user_manual.md
@@ -1138,16 +1138,28 @@ One may chroot into the SDK and install required target packages with the help o
### Example
+ - Enable isar-apt include in `conf/local.conf`:
+
+```
+SDK_INCLUDE_ISAR_APT = "1"
+```
+
- Trigger creation of SDK root filesystem
```
bitbake -c do_populate_sdk mc:qemuarm-bullseye:isar-image-base
+```
+
+ - Unpack generated SDK:
+
+```
+sudo tar xf tmp/deploy/images/qemuarm/isar-image-base-sdk-debian-bullseye-qemuarm.tar.xz -C tmp/deploy/images/qemuarm
```
- 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 ../scripts/mount_chroot.sh
#!/bin/sh
set -e
@@ -1159,14 +1171,14 @@ 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 ../build/tmp/deploy/images/qemuarm/isar-image-base-sdk-debian-bullseye-qemuarm
+sudo ../scripts/mount_chroot.sh tmp/deploy/images/qemuarm/isar-image-base-sdk-debian-bullseye-qemuarm
```
- chroot to isar SDK rootfs:
```
-$ sudo chroot build/tmp/deploy/images/qemuarm/isar-image-base-sdk-debian-bullseye-qemuarm
+sudo chroot tmp/deploy/images/qemuarm/isar-image-base-sdk-debian-bullseye-qemuarm
```
- Check that cross toolchains are installed
@@ -1180,6 +1192,13 @@ ii crossbuild-essential-armhf 12.3 all Inf
```
:~# apt-get update
:~# apt-get install libhello-dev:armhf
+```
+
+Note that you may need to copy `/etc/resolv.conf` from the host or use any
+public nameserver like:
+
+```
+:~# echo "nameserver 8.8.8.8" > /etc/resolv.conf
```
- Check the contents of the installed target package
@@ -1200,6 +1219,12 @@ ii crossbuild-essential-armhf 12.3 all Inf
/usr/share/doc/libhello-dev/changelog.gz
/usr/share/doc/libhello-dev/copyright
~#
+```
+
+ - Unmount rootfs paths:
+
+```
+sudo ../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
next prev parent reply other threads:[~2023-12-21 10:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 10:31 [PATCH v2 0/4] Fixing isar-apt usage inside SDK Anton Mikanovich
2023-12-21 10:31 ` [PATCH v2 1/4] rootfs: Split isar-apt and base-apt cleanup Anton Mikanovich
2023-12-21 10:31 ` [PATCH v2 2/4] sdk: Remove duplicated isar-apt cleanup Anton Mikanovich
2023-12-21 10:31 ` [PATCH v2 3/4] sdk: Control isar-apt list removing Anton Mikanovich
2023-12-21 10:31 ` Anton Mikanovich [this message]
2023-12-29 7:17 ` [PATCH v2 0/4] Fixing isar-apt usage inside SDK Anton Mikanovich
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=20231221103142.47089-5-amikan@ilbers.de \
--to=amikan@ilbers.de \
--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