From: Srinuvasan Arjunan <srinuvasanasv@gmail.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Srinuvasan Arjunan <srinuvasan_a@mentor.com>,
isar-users@googlegroups.com, amikan@ilbers.de,
adriaan.schmidt@siemens.com
Subject: Re: [PATCH] meta/classes/sdk.bbclass: add --transform in TAR_OPTIONS
Date: Wed, 12 Apr 2023 19:08:33 +0530 [thread overview]
Message-ID: <CAB2Z2nOZkSJ9HJCLHSybJmK5AXOh+9ELWCRQSDn44ToqSSUkdg@mail.gmail.com> (raw)
In-Reply-To: <b460e006-136e-9c4f-311a-edfa724c32e2@siemens.com>
[-- Attachment #1: Type: text/plain, Size: 2251 bytes --]
On Wed, Apr 5, 2023 at 4:27 PM 'Jan Kiszka' via isar-users <
isar-users@googlegroups.com> wrote:
> On 31.03.23 12:33, Srinuvasan Arjunan wrote:
> > From: Srinuvasan A <srinuvasan_a@mentor.com>
> >
> > 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.
> >
> > Signed-off-by: Srinuvasan A <srinuvasan_a@mentor.com>
> > ---
> > meta/classes/sdk.bbclass | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/meta/classes/sdk.bbclass b/meta/classes/sdk.bbclass
> > index 06cae02..50f718c 100644
> > --- a/meta/classes/sdk.bbclass
> > +++ b/meta/classes/sdk.bbclass
> > @@ -53,6 +53,7 @@ ROOTFS_MANIFEST_DEPLOY_DIR:class-sdk =
> "${DEPLOY_DIR_SDKCHROOT}"
> > ROOTFS_DPKGSTATUS_DEPLOY_DIR:class-sdk = "${DEPLOY_DIR_SDKCHROOT}"
> >
> > IMAGE_FSTYPES:class-sdk = "${SDK_FORMATS}"
> > +TAR_OPTIONS:append:class-sdk = " --transform="s|.|$(basename
> ${PP_DEPLOY}/${IMAGE_FULLNAME})|""
> >
> > # bitbake dependencies
> > SDKDEPENDS += "sdk-files ${SDK_INSTALL}"
>
> To my understanding, this will move the content of the SDK tarball into
> a subfolder. What will that name be? ${IMAGE_FULLNAME}? And isn't
> $(basename ${PP_DEPLOY}/${IMAGE_FULLNAME}) the same as just
> ${IMAGE_FULLNAME}?
>
Tested, yes ${IMAGE_FULLNAME} works here instead of $(basename
${PP_DEPLOY}/${IMAGE_FULLNAME})
>
> I'm fine with the relocation per se, I'm just wondering if we documented
> or otherwise referred to the structure of an unpacked SDK somewhere, in
> the user manual eg., and if that then also needs updating.
>
Yes we have gap in the document, will update and send next version
>
> Jan
>
> --
> Siemens AG, Technology
> Competence Center Embedded Linux
>
> --
> 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/b460e006-136e-9c4f-311a-edfa724c32e2%40siemens.com
> .
>
[-- Attachment #2: Type: text/html, Size: 3474 bytes --]
next prev parent reply other threads:[~2023-04-12 13:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 8:49 Srinuvasan Arjunan
2023-03-31 9:06 ` Schmidt, Adriaan
2023-03-31 10:33 ` Srinuvasan Arjunan
2023-04-03 10:01 ` Srinuvasan Arjunan
2023-04-05 10:40 ` Schmidt, Adriaan
2023-04-05 10:57 ` Jan Kiszka
2023-04-12 13:38 ` Srinuvasan Arjunan [this message]
2023-04-19 14:09 ` [PATCH v2] " Srinuvasan Arjunan
2023-04-24 10:43 ` Srinuvasan Arjunan
2023-05-08 17:57 ` Anton Mikanovich
2023-09-25 10:55 ` Jan Kiszka
2023-09-28 8:26 ` Gylstorff Quirin
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=CAB2Z2nOZkSJ9HJCLHSybJmK5AXOh+9ELWCRQSDn44ToqSSUkdg@mail.gmail.com \
--to=srinuvasanasv@gmail.com \
--cc=adriaan.schmidt@siemens.com \
--cc=amikan@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=srinuvasan_a@mentor.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