All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Neumann <s.neumann@raumfeld.com>
To: buildroot@busybox.net
Subject: [Buildroot] how to clean up everything but the toolchain
Date: Thu, 01 Oct 2009 10:04:33 +0200	[thread overview]
Message-ID: <1254384273.5284.5.camel@sven> (raw)

Hi,

we are using buildroot to build a number of projects for the same
platform. Currently we do this simply by changing the .config file. In
order for the build to work after changing the .config file, we remove
the project_build_arm, build_arm and toolchain_build_arm directories. So
basically we are doing a full rebuild, including the toolchain. We could
save a lot of CPU cycles if we could reuse the toolchain build. However
I found that if I remove the build_arm directory, but not the
toolchain_build_arm directory, things will break. So I wonder if there
is an easy solution to this. Perhaps a make target that we didn't
discover yet?


Sven

             reply	other threads:[~2009-10-01  8:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-01  8:04 Sven Neumann [this message]
2009-10-01  8:44 ` [Buildroot] how to clean up everything but the toolchain Thomas Petazzoni
2009-10-01 11:22 ` Will Newton
2009-10-01 11:28   ` Sven Neumann

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=1254384273.5284.5.camel@sven \
    --to=s.neumann@raumfeld.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.