From: "Moessbauer, Felix" <felix.moessbauer@siemens.com>
To: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
Cc: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"jan.kiszka@siemens.com" <jan.kiszka@siemens.com>
Subject: RE: Avoid to produce the bmap stuff that double the size
Date: Sat, 8 Oct 2022 09:42:24 +0000 [thread overview]
Message-ID: <AM9PR10MB486978261D8066099A4C297B895E9@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CAJGKYO7YfWSx6APDV3_5i4MuGrvy9PH538sUdbbT+uBOCzjS-Q@mail.gmail.com>
> -----Original Message-----
> From: Roberto A. Foglietta <roberto.foglietta@gmail.com>
> Sent: Saturday, October 8, 2022 5:09 PM
> To: Moessbauer, Felix (T CED SES-DE) <felix.moessbauer@siemens.com>
> Cc: isar-users@googlegroups.com; Kiszka, Jan (T CED)
> <jan.kiszka@siemens.com>
> Subject: Re: Avoid to produce the bmap stuff that double the size
>
> Il giorno sab 8 ott 2022 alle ore 10:28 Roberto A. Foglietta
> <roberto.foglietta@gmail.com> ha scritto:
> >
> > Il giorno mar 4 ott 2022 alle ore 08:02 Moessbauer, Felix
> > <felix.moessbauer@siemens.com> ha scritto:
> > >
> >
> > > " [PATCH v7 0/6] use xz and gzip on host (outside chroot)"
> > >
> > > Please give it a try and if it works, feel free to ack.
> > > Testers are always welcome 😉
> > >
> >
> > Hi Felix,
> >
> > this is what I found and fits with what was expecting to find:
> >
> > $ sudo find build -name \*.wic\*
> > build/tmp/deploy/images/debx86/eval-image-debian-bullseye-debx86.wic
>
> Is it possible to avoid creating a sstate-cache of the {image or rootfs}?
> Mine is over 9GB and its cache is useless. Screenshot 12KB attached.
Hi Roberto,
Please do not mix up topics in this thread.
Disabling sstate cache is possible by passing --no-setscene to bitbake as stated in the docs [1]
Apart from that, I doubt that you do not profit from the cache.
Just have a look at the "match: <X>%" output when bitbake starts.
Felix
[1] https://github.com/ilbers/isar/blob/next/doc/user_manual.md#using-sstate-cache
>
> Thanks, R.
next prev parent reply other threads:[~2022-10-08 9:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 5:46 Roberto A. Foglietta
2022-10-04 6:00 ` Jan Kiszka
2022-10-05 5:46 ` Roberto A. Foglietta
2022-10-04 6:02 ` Moessbauer, Felix
2022-10-04 6:17 ` Roberto A. Foglietta
2022-10-08 8:28 ` Roberto A. Foglietta
2022-10-08 9:08 ` Roberto A. Foglietta
2022-10-08 9:42 ` Moessbauer, Felix [this message]
2022-10-08 9:55 ` Roberto A. Foglietta
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=AM9PR10MB486978261D8066099A4C297B895E9@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM \
--to=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=roberto.foglietta@gmail.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