All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Colin Foster <colin.foster@in-advantage.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH V1] core: add kconfig option to archive an un-stripped filesystem
Date: Sat, 29 Jul 2023 22:59:38 +0200	[thread overview]
Message-ID: <20230729225938.69d399eb@windsurf> (raw)
In-Reply-To: <ZMV56j37ps7vOaLB@euler>

On Sat, 29 Jul 2023 13:43:22 -0700
Colin Foster <colin.foster@in-advantage.com> wrote:

> Something to consider is the file / directory sizes. From a quick
> Beaglebone build, the output/build directory is 9GB, while the
> rootfs_syms.tgz is 33MB (and it is 90MB uncompressed). I suppose I could
> compress and drag around the build directory (which compressed down to
> ~2GB) for completeness. But realistically there's a lot of baggage there
> that won't be needed.

Agreed, and that's why installing everything to staging is most likely
the way to go (staging is much smaller than output/build, and the
contents of staging are distributed within the SDK, which makes sense
for debugging purposes).

The thing is that installing everything in staging is a major change in
Buildroot... At the very least all generic-package packages need to be
modified.

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2023-07-29 20:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-28 23:18 [Buildroot] [PATCH V1] core: add kconfig option to archive an un-stripped filesystem Colin Foster
2023-07-29  7:49 ` Thomas Petazzoni via buildroot
2023-07-29 20:43   ` Colin Foster
2023-07-29 20:59     ` Thomas Petazzoni via buildroot [this message]

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=20230729225938.69d399eb@windsurf \
    --to=buildroot@buildroot.org \
    --cc=colin.foster@in-advantage.com \
    --cc=thomas.petazzoni@bootlin.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 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.