From: "Khem Raj" <raj.khem@gmail.com>
To: Brian Hutchinson <b.hutchman@gmail.com>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [oe] Any way to make cryptsetup smaller? I have a small 32M NOR flash and 11M SquashFS rootfs.
Date: Mon, 2 Aug 2021 18:36:15 -0700 [thread overview]
Message-ID: <CAMKF1so85_HpSoqt=ZBvgf_jYoJJnnBtVXUjPZfsJdupHa6_zA@mail.gmail.com> (raw)
In-Reply-To: <CAFZh4h-oyyAdWC-vceBEJuUgZMEL7h7f5CRRO3f6yx6iY-zs7Q@mail.gmail.com>
On Mon, Aug 2, 2021 at 4:14 PM Brian Hutchinson <b.hutchman@gmail.com> wrote:
>
>
>
> On Mon, Aug 2, 2021 at 7:06 PM Khem Raj <raj.khem@gmail.com> wrote:
>>
>>
>> I meant build an image like you do and then add cryptsetup and do a build again this all after enabling build history then check build history repo and it will have the information on top commit about what changed and which all packages got added and how much are they adding to size
>
>
> Use both:
>
> INHERIT += "buildhistory"
>
> BUILDHISTORY_COMMIT = "1"
yes see for e.g.
https://github.com/YoeDistro/yoe-distro/blob/master/sources/meta-yoe/conf/distro/yoe.inc#L49
https://github.com/YoeDistro/yoe-distro/blob/master/sources/meta-yoe/conf/distro/yoe.inc#L93
>
> ???
>
> I've never used it before.
>
> Do I have to smoke /tmp and rebuild everything?
No, but perhaps better to do so. You can still reuse sstate
>
> Regards,
>
> Brian
next prev parent reply other threads:[~2021-08-03 3:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 18:07 Any way to make cryptsetup smaller? I have a small 32M NOR flash and 11M SquashFS rootfs Brian Hutchinson
2021-08-02 20:05 ` [oe] " Khem Raj
2021-08-02 22:16 ` Brian Hutchinson
2021-08-02 23:06 ` Khem Raj
2021-08-02 23:14 ` Brian Hutchinson
2021-08-03 1:36 ` Khem Raj [this message]
2021-08-03 14:00 ` Andrea Adami
2021-08-03 16:09 ` Brian Hutchinson
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='CAMKF1so85_HpSoqt=ZBvgf_jYoJJnnBtVXUjPZfsJdupHa6_zA@mail.gmail.com' \
--to=raj.khem@gmail.com \
--cc=b.hutchman@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.