From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 7216630053834063872 X-Received: by 2002:a9d:450d:0:b0:6a3:8428:fd4e with SMTP id w13-20020a9d450d000000b006a38428fd4emr4008173ote.6.1682333012687; Mon, 24 Apr 2023 03:43:32 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a05:6808:1b1e:b0:38c:3dca:c6db with SMTP id bx30-20020a0568081b1e00b0038c3dcac6dbls2440308oib.10.-pod-prod-gmail; Mon, 24 Apr 2023 03:43:32 -0700 (PDT) X-Google-Smtp-Source: AKy350ZueateucYMXtp5IexgdfS2jry3u174KG4YX6cl8fOzSMuVhFMbTmTCLkFZKDmcP0cDPI9W X-Received: by 2002:aca:1906:0:b0:38e:a824:27d3 with SMTP id l6-20020aca1906000000b0038ea82427d3mr2735305oii.27.1682333012111; Mon, 24 Apr 2023 03:43:32 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1682333012; cv=none; d=google.com; s=arc-20160816; b=w4dAhfA7ASbMK0ZelIqp7LWul0e6yycli3BY+fYa9OK/OmX19MnU4aRnI9U9mlbaZt m26H8GNPQGtLQm5c4dFQuhG0YIIVwJUv0mUFf3J3jJuFH7qrt+tujNLnkH5kEvH0qbD5 VbFOY5BgTQGBpHP5hxKI1YaV3EUm7kduOk3whqE324Baay0zhnqD/18Nmj4ug1D6JANm 2aWdA+lSohCsF3FCWT99P4FB/gVB9YpKy6XCpCA/aGLD52H5r2NJ6pJebPYoaELUdiO5 vo28AC4PjJ4iVmUzS3U9pnSD6pBEG42RwhuCQd6TPbwpCI8yCwxs/GMMEfdgmRUe5voN nnHw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:dkim-signature; bh=lcdaZQAhkUjNb1JJtYSSmzwxBvw+/iBNRyHw7KHcMdY=; b=EA3YLZSNo3ktwIn3IeF67ZMV8tdCLW8lcQiNeEpufEwQKVOw+rD+bSXHzP53MGUVGU 2dw/oNTj1kM9dv8IaOx4tl1wYOplYLYr7ZB27rb9UH3CrcNKtPiTommnlqtP5hylNyPG kQkxkqaG+nO9MgxJsnIjsvCf1mY9FwbzZu0Bec3Di6ueHQI3gUkpPhdpLVkVZDXEi/aQ J5EW78+lecHmLZUtgZBAqpzfhq6g1SPzFinD21cbPOGrkKvydCpbCbpAINe1/Bh3cigN HFQ2QgytjRoobbbe0OEqq/f6ZQrix5B28f6wOKf+AHeLcJSszp/JDy9BdvmZiiblmLlv 0bcA== ARC-Authentication-Results: i=1; gmr-mx.google.com; dkim=pass header.i=@gmail.com header.s=20221208 header.b=VrzipTnP; spf=pass (google.com: domain of srinuvasanasv@gmail.com designates 2607:f8b0:4864:20::92c as permitted sender) smtp.mailfrom=srinuvasanasv@gmail.com; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from mail-ua1-x92c.google.com (mail-ua1-x92c.google.com. [2607:f8b0:4864:20::92c]) by gmr-mx.google.com with ESMTPS id ca14-20020a056808330e00b0038e4d42b941si539338oib.1.2023.04.24.03.43.32 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 24 Apr 2023 03:43:32 -0700 (PDT) Received-SPF: pass (google.com: domain of srinuvasanasv@gmail.com designates 2607:f8b0:4864:20::92c as permitted sender) client-ip=2607:f8b0:4864:20::92c; Authentication-Results: gmr-mx.google.com; dkim=pass header.i=@gmail.com header.s=20221208 header.b=VrzipTnP; spf=pass (google.com: domain of srinuvasanasv@gmail.com designates 2607:f8b0:4864:20::92c as permitted sender) smtp.mailfrom=srinuvasanasv@gmail.com; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: by mail-ua1-x92c.google.com with SMTP id a1e0cc1a2514c-7721f36a69bso1434924241.3 for ; Mon, 24 Apr 2023 03:43:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1682333011; x=1684925011; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=lcdaZQAhkUjNb1JJtYSSmzwxBvw+/iBNRyHw7KHcMdY=; b=VrzipTnPpQ79LD6mBtqrOL8vzj/mcNXey0pPXyhSe9Kol9mfUcBpFPfGgHwwxLwYS4 LnDFXM3rBPE+RTxjSexAgyzIwwGieLvP/1DHK0y/9iDn9eCWuh1Cfh2QzfCg1Uc38JOd efFlLwRzGYiFo2NmCbWXGp17TlH1yg+tVUIyWMNm3gbHpJRQTdfBS3+FglzQdxor+3SU UVs6kyUH2B7gklZPpIkbhyQbOWBFUYjAckdAbEWT4cQLR/YEdnhDit6Y/cphQSnHKpFk kOXFaT2uTPFecUdmoxlzK8BjMhZoXjPBGkQY5fFUsZBb1YdEK0TLKvpAJ1cmmvDmBEQr Nc1Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682333011; x=1684925011; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=lcdaZQAhkUjNb1JJtYSSmzwxBvw+/iBNRyHw7KHcMdY=; b=bcnA8h5Y00emlQlJTrvlk+M5c3j3agI/kVqXYz3v6gRGUnC5y5s8OFjYSvRzQB6s4f EYx8VwaNOs6VEVdXbpzh4Pu/+CfZSVNPg84ZWjescuppW/Ioe9BiApvTwgcsUou3GxDA GIjBp+MuOfMXVgOAxp2J43FhZQpupQOr8P9/+kRR51yI88Dyp1PMNpRhDsprmDlJF5HE hMVnOWGiN9nyt/Y0x/3N3RmHriE1a7f6/7BqqXAd4y0OJ+RlYmYy4+7N1+WEuq6n5p4u fxAnstdMeVQXzV2v7xmSX/4YeQcj5nc0KXtPbNdjx6WGexaGWguggQTCLIh0KN97Zj2X Niww== X-Gm-Message-State: AAQBX9ctLTjpKKyCAsJ2VrR956UfW8gyt7NIa1X6YXmgrIIRCxyonLdD H6Uf8x9F8m60HnzK9/pRgqwH8xqmQlHY2it9mGBg8ca/ X-Received: by 2002:a05:6102:a2e:b0:42e:3861:9fa3 with SMTP id 14-20020a0561020a2e00b0042e38619fa3mr5249914vsb.18.1682333011497; Mon, 24 Apr 2023 03:43:31 -0700 (PDT) MIME-Version: 1.0 References: <20230419140940.1268690-1-srinuvasan_a@mentor.com> In-Reply-To: <20230419140940.1268690-1-srinuvasan_a@mentor.com> From: Srinuvasan Arjunan Date: Mon, 24 Apr 2023 16:13:20 +0530 Message-ID: Subject: Re: [PATCH v2] meta/classes/sdk.bbclass: add --transform in TAR_OPTIONS To: Srinuvasan Arjunan Cc: isar-users@googlegroups.com, jan.kiszka@siemens.com, amikan@ilbers.de, adriaan.schmidt@siemens.com Content-Type: multipart/alternative; boundary="0000000000008b54e405fa12ade8" X-TUID: g+fRnGnf/JpR --0000000000008b54e405fa12ade8 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Any comments or improvements? On Wed, Apr 19, 2023 at 7:40=E2=80=AFPM Srinuvasan Arjunan wrote: > From: Srinuvasan A > > When we untar the SDK rootfs archive file, all the contents are extracted > into the current directory, not a folder, this looks ugly hence fixed > it with the file name transformations option. > > But the below transform pattern not works, specifically with the symlink > TAR_OPTIONS:append:class-sdk =3D " --transform=3D"s|.|${IMAGE_FULLNAME}|"= " > > instead of changedir -C with {PP_ROOTFS} and choose all files (.), > use {PP} and choose rootfs dir, now by default extracted into a rootfs > sub folder, in this case --transform works fine with the filename. > > Updated the document as well. > > Signed-off-by: Srinuvasan A > --- > doc/user_manual.md | 20 ++++++++++---------- > meta/classes/imagetypes.bbclass | 2 +- > meta/classes/sdk.bbclass | 1 + > 3 files changed, 12 insertions(+), 11 deletions(-) > > diff --git a/doc/user_manual.md b/doc/user_manual.md > index 92075a8..60b7ca9 100644 > --- a/doc/user_manual.md > +++ b/doc/user_manual.md > @@ -1063,8 +1063,8 @@ User manually triggers creation of SDK root > filesystem for his target platform b > `bitbake -c do_populate_sdk mc:${MACHINE}-${DISTRO}:isar-image-base`. > Packages that should be additionally installed into the SDK can be > appended to `SDK_PREINSTALL` (external repositories) and `SDK_INSTALL` > (self-built). > > -The resulting SDK rootfs is archived into > `tmp/deploy/images/${MACHINE}/sdk-${DISTRO}-${DISTRO_ARCH}.tar.xz`. > -It is additionally available for direct use under > `tmp/deploy/images/${MACHINE}/sdk-${DISTRO}-${DISTRO_ARCH}/`. > +The resulting SDK rootfs is archived into > `tmp/deploy/images/${MACHINE}/${IMAGE_FULLNAME}.tar.xz`. > +Once you untar the compressed file, the content will be extracted into > the ${IMAGE_FULLNAME} sub folder. > The SDK rootfs directory `/isar-apt` contains a copy of isar-apt repo > with locally prebuilt target debian packages (for ). > One may chroot into the SDK and install required target packages with th= e > help of `apt-get install :` command. > > @@ -1073,7 +1073,7 @@ One may chroot into the SDK and install required > target packages with the help o > - Trigger creation of SDK root filesystem > > ``` > -bitbake -c do_populate_sdk mc:qemuarm-buster:isar-image-base > +bitbake -c do_populate_sdk mc:qemuarm-bullseye:isar-image-base > ``` > > - Mount the following directories in chroot by passing resulting rootfs > as an argument to the script `mount_chroot.sh`: > @@ -1091,14 +1091,14 @@ mount devtmpfs $1/dev -t devtmpfs -o > mode=3D0755,nosuid > mount devpts $1/dev/pts -t devpts -o gid=3D5,mode=3D620 > mount tmpfs $1/dev/shm -t tmpfs -o rw,seclabel,nosuid,nodev > > -$ sudo scripts/mount_chroot.sh > ../build/tmp/deploy/images/qemuarm/sdk-debian-buster-armhf > +$ sudo scripts/mount_chroot.sh > ../build/tmp/deploy/images/qemuarm/isar-image-base-sdk-debian-bullseye-qe= muarm > > ``` > > - chroot to isar SDK rootfs: > > ``` > -$ sudo chroot build/tmp/deploy/images/qemuarm/sdk-debian-buster-armhf > +$ sudo chroot > build/tmp/deploy/images/qemuarm/isar-image-base-sdk-debian-bullseye-qemua= rm > ``` > - Check that cross toolchains are installed > > @@ -1190,7 +1190,7 @@ Daemon socket) accessible in the container. > What can endanger the stability and security of the host. > > The resulting SDK formats are archived into > -`tmp/deploy/images/${MACHINE}/sdk-${DISTRO}-${DISTRO_ARCH}-${sdk_format}= .tar.xz` > > > +`tmp/deploy/images/${MACHINE}/isar-image-base-sdk-${DISTRO}-${DISTRO_ARC= H}-${sdk_format}.tar.xz` > (being `sdk_format` each one of the formats specified in `SDK_FORMATS`). > The SDK container directory `/isar-apt` contains a copy of isar-apt repo > with > locally prebuilt target debian packages (for ). > @@ -1207,27 +1207,27 @@ to edit files in the host with an IDE and build i= n > the container. > For one-shot builds (use `local.conf` otherwise): > > ``` > -export BB_ENV_EXTRAWHITE=3D"$BB_ENV_EXTRAWHITE SDK_FORMATS" > +export BB_ENV_PASSTHROUGH_ADDITIONS=3D"$BB_ENV_EXTRAWHITE SDK_FORMATS" > export SDK_FORMATS=3D"docker-archive" > ``` > > - Trigger creation of SDK root filesystem > > ``` > -bitbake -c do_populate_sdk mc:qemuarm-buster:isar-image-base > +bitbake -c do_populate_sdk mc:qemuarm-bullseye:isar-image-base > ``` > > - Load the SDK container image into the Docker Daemon > > ``` > -docker load -i > build/tmp/deploy/images/qemuarm/sdk-isar-image-base-debian-buster-armhf-1= .0-r0-docker-archive.tar.xz > +docker load -i > build/tmp/deploy/images/qemuarm/isar-image-base-sdk-debian-bullseye-armhf= -1.0-r0-docker-archive.tar.xz > ``` > > - Run a container using the SDK container image (following commands > starting > with `#~:` are to be run in the container) > > ``` > -docker run --rm -ti --volume "$(pwd):/build" > sdk-isar-image-base-debian-buster-armhf:1.0-r0 > +docker run --rm -ti --volume "$(pwd):/build" > isar-image-base-sdk-debian-bullseye-armhf:1.0-r0 > ``` > > - Check that cross toolchains are installed > diff --git a/meta/classes/imagetypes.bbclass > b/meta/classes/imagetypes.bbclass > index 2ee3240..e476778 100644 > --- a/meta/classes/imagetypes.bbclass > +++ b/meta/classes/imagetypes.bbclass > @@ -9,7 +9,7 @@ TAR_OPTIONS ?=3D "" > > IMAGE_CMD:tar() { > ${SUDO_CHROOT} tar ${TAR_OPTIONS} -cvSf \ > - ${IMAGE_FILE_CHROOT} --one-file-system -C ${PP_ROOTFS} = . > + ${IMAGE_FILE_CHROOT} --one-file-system -C ${PP} rootfs > } > > # image type: ext4 > diff --git a/meta/classes/sdk.bbclass b/meta/classes/sdk.bbclass > index 06cae02..c6dc689 100644 > --- a/meta/classes/sdk.bbclass > +++ b/meta/classes/sdk.bbclass > @@ -53,6 +53,7 @@ ROOTFS_MANIFEST_DEPLOY_DIR:class-sdk =3D > "${DEPLOY_DIR_SDKCHROOT}" > ROOTFS_DPKGSTATUS_DEPLOY_DIR:class-sdk =3D "${DEPLOY_DIR_SDKCHROOT}" > > IMAGE_FSTYPES:class-sdk =3D "${SDK_FORMATS}" > +TAR_OPTIONS:append:class-sdk =3D " > --transform=3D"s|rootfs|${IMAGE_FULLNAME}|"" > > # bitbake dependencies > SDKDEPENDS +=3D "sdk-files ${SDK_INSTALL}" > -- > 2.34.1 > > -- > You received this message because you are subscribed to a topic in the > Google Groups "isar-users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/isar-users/4-CFUZ66nmo/unsubscribe. > To unsubscribe from this group and all its topics, 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/20230419140940.1268690-1-sri= nuvasan_a%40mentor.com > . > --0000000000008b54e405fa12ade8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Any comments or improvements?

On Wed, Apr 19, 2023 at 7:40= =E2=80=AFPM Srinuvasan Arjunan <srinuvasan_a@mentor.com> wrote:
From: Srinuvasan A <srinuvasan_a@mentor.c= om>

When we untar the SDK rootfs archive file, all the contents are extracted into the current directory, not a folder, this looks ugly hence fixed
it with the file name transformations option.

But the below transform pattern not works, specifically with the symlink TAR_OPTIONS:append:class-sdk =3D " --transform=3D"s|.|${IMAGE_FUL= LNAME}|""

instead of changedir -C with {PP_ROOTFS} and choose all files (.),
use {PP} and choose rootfs dir, now by default extracted into a rootfs
sub folder, in this case --transform works fine with the filename.

Updated the document as well.

Signed-off-by: Srinuvasan A <srinuvasan_a@mentor.com>
---
=C2=A0doc/user_manual.md=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 | = 20 ++++++++++----------
=C2=A0meta/classes/imagetypes.bbclass |=C2=A0 2 +-
=C2=A0meta/classes/sdk.bbclass=C2=A0 =C2=A0 =C2=A0 =C2=A0 |=C2=A0 1 +
=C2=A03 files changed, 12 insertions(+), 11 deletions(-)

diff --git a/doc/user_manual.md b/doc/user_manual.md
index 92075a8..60b7ca9 100644
--- a/doc/user_manual.md
+++ b/doc/user_manual.md
@@ -1063,8 +1063,8 @@ User manually triggers creation of SDK root filesyste= m for his target platform b
=C2=A0`bitbake -c do_populate_sdk mc:${MACHINE}-${DISTRO}:isar-image-base`.=
=C2=A0Packages that should be additionally installed into the SDK can be ap= pended to `SDK_PREINSTALL` (external repositories) and `SDK_INSTALL` (self-= built).

-The resulting SDK rootfs is archived into `tmp/deploy/images/${MACHINE}/sd= k-${DISTRO}-${DISTRO_ARCH}.tar.xz`.
-It is additionally available for direct use under `tmp/deploy/images/${MAC= HINE}/sdk-${DISTRO}-${DISTRO_ARCH}/`.
+The resulting SDK rootfs is archived into `tmp/deploy/images/${MACHINE}/${= IMAGE_FULLNAME}.tar.xz`.
+Once you untar the compressed file, the content will be extracted into the= ${IMAGE_FULLNAME} sub folder.
=C2=A0The SDK rootfs directory `/isar-apt` contains a copy of isar-apt repo= with locally prebuilt target debian packages (for <HOST_DISTRO>). =C2=A0One may chroot into the SDK and install required target packages with= the help of `apt-get install <package_name>:<DISTRO_ARCH>` com= mand.

@@ -1073,7 +1073,7 @@ One may chroot into the SDK and install required targ= et packages with the help o
=C2=A0 - Trigger creation of SDK root filesystem

=C2=A0```
-bitbake -c do_populate_sdk mc:qemuarm-buster:isar-image-base
+bitbake -c do_populate_sdk mc:qemuarm-bullseye:isar-image-base
=C2=A0```

=C2=A0 - Mount the following directories in chroot by passing resulting roo= tfs as an argument to the script `mount_chroot.sh`:
@@ -1091,14 +1091,14 @@ mount devtmpfs $1/dev=C2=A0 =C2=A0 =C2=A0-t devtmpf= s -o mode=3D0755,nosuid
=C2=A0mount devpts=C2=A0 =C2=A0$1/dev/pts -t devpts=C2=A0 =C2=A0-o gid=3D5,= mode=3D620
=C2=A0mount tmpfs=C2=A0 =C2=A0 $1/dev/shm -t tmpfs=C2=A0 =C2=A0 -o rw,secla= bel,nosuid,nodev

-$ sudo scripts/mount_chroot.sh ../build/tmp/deploy/images/qemuarm/sdk-debi= an-buster-armhf
+$ sudo scripts/mount_chroot.sh ../build/tmp/deploy/images/qemuarm/isar-ima= ge-base-sdk-debian-bullseye-qemuarm

=C2=A0```

=C2=A0 - chroot to isar SDK rootfs:

=C2=A0```
-$ sudo chroot build/tmp/deploy/images/qemuarm/sdk-debian-buster-armhf
+$ sudo chroot build/tmp/deploy/images/qemuarm/isar-image-base-sdk-debian-b= ullseye-qemuarm
=C2=A0```
=C2=A0 - Check that cross toolchains are installed

@@ -1190,7 +1190,7 @@ Daemon socket) accessible in the container.
=C2=A0What can endanger the stability and security of the host.

=C2=A0The resulting SDK formats are archived into
-`tmp/deploy/images/${MACHINE}/sdk-${DISTRO}-${DISTRO_ARCH}-${sdk_format}.t= ar.xz`
+`tmp/deploy/images/${MACHINE}/isar-image-base-sdk-${DISTRO}-${DISTRO_ARCH}= -${sdk_format}.tar.xz`
=C2=A0(being `sdk_format` each one of the formats specified in `SDK_FORMATS= `).
=C2=A0The SDK container directory `/isar-apt` contains a copy of isar-apt r= epo with
=C2=A0locally prebuilt target debian packages (for <HOST_DISTRO>). @@ -1207,27 +1207,27 @@ to edit files in the host with an IDE and build in = the container.
=C2=A0For one-shot builds (use `local.conf` otherwise):

=C2=A0```
-export BB_ENV_EXTRAWHITE=3D"$BB_ENV_EXTRAWHITE SDK_FORMATS"
+export BB_ENV_PASSTHROUGH_ADDITIONS=3D"$BB_ENV_EXTRAWHITE SDK_FORMATS= "
=C2=A0export SDK_FORMATS=3D"docker-archive"
=C2=A0```

=C2=A0 - Trigger creation of SDK root filesystem

=C2=A0```
-bitbake -c do_populate_sdk mc:qemuarm-buster:isar-image-base
+bitbake -c do_populate_sdk mc:qemuarm-bullseye:isar-image-base
=C2=A0```

=C2=A0 - Load the SDK container image into the Docker Daemon

=C2=A0```
-docker load -i build/tmp/deploy/images/qemuarm/sdk-isar-image-base-debian-= buster-armhf-1.0-r0-docker-archive.tar.xz
+docker load -i build/tmp/deploy/images/qemuarm/isar-image-base-sdk-debian-= bullseye-armhf-1.0-r0-docker-archive.tar.xz
=C2=A0```

=C2=A0 - Run a container using the SDK container image (following commands = starting
=C2=A0 =C2=A0 with `#~:` are to be run in the container)

=C2=A0```
-docker run --rm -ti --volume "$(pwd):/build" sdk-isar-image-base= -debian-buster-armhf:1.0-r0
+docker run --rm -ti --volume "$(pwd):/build" isar-image-base-sdk= -debian-bullseye-armhf:1.0-r0
=C2=A0```

=C2=A0 - Check that cross toolchains are installed
diff --git a/meta/classes/imagetypes.bbclass b/meta/classes/imagetypes.bbcl= ass
index 2ee3240..e476778 100644
--- a/meta/classes/imagetypes.bbclass
+++ b/meta/classes/imagetypes.bbclass
@@ -9,7 +9,7 @@ TAR_OPTIONS ?=3D ""

=C2=A0IMAGE_CMD:tar() {
=C2=A0 =C2=A0 =C2=A0${SUDO_CHROOT} tar ${TAR_OPTIONS} -cvSf \
-=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0${IMAGE_FILE= _CHROOT} --one-file-system -C ${PP_ROOTFS} .
+=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0${IMAGE_FILE= _CHROOT} --one-file-system -C ${PP} rootfs
=C2=A0}

=C2=A0# image type: ext4
diff --git a/meta/classes/sdk.bbclass b/meta/classes/sdk.bbclass
index 06cae02..c6dc689 100644
--- a/meta/classes/sdk.bbclass
+++ b/meta/classes/sdk.bbclass
@@ -53,6 +53,7 @@ ROOTFS_MANIFEST_DEPLOY_DIR:class-sdk =3D "${DEPLOY_D= IR_SDKCHROOT}"
=C2=A0ROOTFS_DPKGSTATUS_DEPLOY_DIR:class-sdk =3D "${DEPLOY_DIR_SDKCHRO= OT}"

=C2=A0IMAGE_FSTYPES:class-sdk =3D "${SDK_FORMATS}"
+TAR_OPTIONS:append:class-sdk =3D " --transform=3D"s|rootfs|${IMA= GE_FULLNAME}|""

=C2=A0# bitbake dependencies
=C2=A0SDKDEPENDS +=3D "sdk-files ${SDK_INSTALL}"
--
2.34.1

--
You received this message because you are subscribed to a topic in the Goog= le Groups "isar-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/isar-users/4-CFUZ66nmo/unsubscribe<= /a>.
To unsubscribe from this group and all its topics, send an email to isa= r-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/isar-= users/20230419140940.1268690-1-srinuvasan_a%40mentor.com.
--0000000000008b54e405fa12ade8--