[Buildroot] [PATCH 0/2] core/sdk: fix relative symlinks in generated tarball (branch yem/sdk)

Trent Piepho tpiepho at impinj.com
Wed Dec 26 18:22:26 UTC 2018

On Sat, 2018-12-22 at 11:21 -0700, Joel Carlson wrote:
> On Sat, Dec 22, 2018 at 1:31 AM Yann E. MORIN <yann.morin.1998 at free.fr> wrote:
> > 
> > 
> > An other approach, would be that we whietelist certain PATHs from our
> > SDK. Afterall, there are things we do not care about in the SDK. For
> > example, most executables in staging/{,usr/}{,s}bin are not needed. We
> > only really need libs and headers, so we could just ignore anything
> > that is not in staging/{lib,usr/lib,usr/include}/

With per-package staging, could this be done before the per-package
staging areas are combined?  The idea would be to reduce differences
between the stage in buildroot and the stage when using an SDK.  Every
difference is a possible source of problems, even if it is something
that we are not supposed to care about.

Could this be taken further, and everything not in the stage whitelist
be deleted?  It would be nice if the SDK were smaller.

More information about the buildroot mailing list