From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] fs skeleton quick rebuild
Date: Tue, 4 Sep 2012 20:03:31 +0200 [thread overview]
Message-ID: <20120904200331.1222b43d@skate> (raw)
In-Reply-To: <CAE9DZUQi+OEhWzW0Hu1bBrBhs6QZ+_V=J1MwFej_H2EAhhdM4A@mail.gmail.com>
Le Tue, 4 Sep 2012 12:59:42 -0500,
Dallas Clement <dallas.a.clement@gmail.com> a ?crit :
> I'm working on a custom skeleton for my rootfs and wanting to make
> changes and test without having to rebuild everything. Is there an
> easy way to do this?
Easiest way is to *not* use the custom skeleton mechanism, but instead
use the post-build script mechanism. See
http://elinux.org/images/2/2a/Using-buildroot-real-project.pdf for more
details.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-09-04 18:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 17:59 [Buildroot] fs skeleton quick rebuild Dallas Clement
2012-09-04 18:03 ` Thomas Petazzoni [this message]
2012-09-04 18:30 ` Stephan Hoffmann
2012-09-04 19:28 ` Dallas Clement
2012-09-05 14:59 ` Aras Vaichas
2012-09-05 20:37 ` Dallas Clement
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=20120904200331.1222b43d@skate \
--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.