All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dallas Clement <dallas.a.clement@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] fs skeleton quick rebuild
Date: Wed, 5 Sep 2012 15:37:56 -0500	[thread overview]
Message-ID: <CAE9DZUSHA9TX+7xQSLsL1Na4SavpureAbFqR8if_XHKK8B58Qg@mail.gmail.com> (raw)
In-Reply-To: <CAJkQPOmzL7L2Z+Bx=t48Fn_+7+ZHtv7gRknhEPhvSxL7CKkcgg@mail.gmail.com>

Hi Aras,

I know it's not recommended, but it sure helps to quickly make changes
and test, especially for an impatient person like me!  ;^)

Here is my script, which is working well.

-- snip --
m -rf target
mkdir -p target/sbin
mkdir -p target/lib
mkdir -p target/usr/lib
cp -a staging/sbin/* target/sbin/
cp -a staging/lib/* target/lib/
cp -a staging/usr/lib/* target/usr/lib/
rm -f build/.root
find . -name ".stamp_target_installed*" -print | xargs rm -f
-- snip --

Thanks,

Dallas

On Wed, Sep 5, 2012 at 9:59 AM, Aras Vaichas <aras.vaichas@gmail.com> wrote:
> On 4 September 2012 19:30, Stephan Hoffmann <sho@relinux.de> wrote:
>> Am 04.09.2012 19:59, schrieb Dallas Clement:
>>> Greetings:
>>>
>>> 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?
>> Hi,
>>
>> I figured out that
>> 1. remove output/target
>> 2. remove output/build/.root
>> 3. remove all .stamp_target_installed files
>> give a quite fast, clean rebuild of the root file system.
>
> I have something similar in a script I call "pre_build_clean.sh"
>
> -- snip --
> #/bin/sh
> echo pre build cleanup script
> echo removing stamps, output/target, output/images,
> find -name .stamp_target_installed | xargs rm
> rm -rf output/target
> rm -rf output/images/*
> rm output/build/.root
> rm output/stamps/ct-ng-toolchain-installed
> echo build your target now. e.g. \"make\" or \"make
> linux-reconfigure\" to rebuild the kernel
> -- snip --
>
> This is the script I created when I was making lots of skeleton,
> configuration and kernel changes; YMMV.
>
> Dallas, be careful doing this because it's easy to make a mistake, and
> I know that Thomas doesn't recommend doing partial builds like this.
>
> If you use a custom toolchain, then I highly recommend building an
> external toolchain. You can perform a "make clean; make" and it
> doesn't take very long.
>
> Aras
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

      reply	other threads:[~2012-09-05 20:37 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
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 [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=CAE9DZUSHA9TX+7xQSLsL1Na4SavpureAbFqR8if_XHKK8B58Qg@mail.gmail.com \
    --to=dallas.a.clement@gmail.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.