From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Regenerating Skeleton without a clean in 2017
Date: Fri, 10 Nov 2017 14:41:56 +0100 [thread overview]
Message-ID: <20171110144156.6c2a8295@windsurf> (raw)
In-Reply-To: <eff7c8c514764b54a3a11924db80c3bb@PGHPRDEXCH02.corp.bbns.com>
Hello,
On Fri, 10 Nov 2017 13:17:15 +0000, John O'Sullivan wrote:
> In the older buildroot releases one could force a reintegration of a
> skeleton overlay with various hacks like removing the .root file in
> build, are there any equivalents in Buildroot-2017.02-4. I understand
> this is not best practice but I have some quick prototyping to do and
> the build time is an issue.
$ make skeleton-rebuild
should do the trick in Buildroot 2017.02. Starting with 2017.08, this
won't work as the skeleton has been split into several packages.
However, you should stop using a custom skeleton, and use a root
filesystem overlay instead (perhaps with a post build script). Why do
you still use a custom skeleton ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-11-10 13:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-10 13:17 [Buildroot] Regenerating Skeleton without a clean in 2017 John O'Sullivan
2017-11-10 13:41 ` Thomas Petazzoni [this message]
2017-11-10 13:43 ` John O'Sullivan
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=20171110144156.6c2a8295@windsurf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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.