From: Sven Neumann <s.neumann@phase-zero.de>
To: buildroot@busybox.net
Subject: [Buildroot] Searching for the right "make clean"
Date: Fri, 16 Jan 2009 10:42:07 +0100 [thread overview]
Message-ID: <1232098927.6639.10.camel@sven> (raw)
In-Reply-To: <1232058471.4757.70.camel@aeglos.sweden.atmel.com>
Hi,
On Thu, 2009-01-15 at 23:27 +0100, Ulf Samuelsson wrote:
> Once you change a toolchain option, you should probably
> remove everything and start afresh.
>
> THere is nothing you need to save except the configs
> which you can do with make saveconfig.
>
>
> I.E: rm:
> binaries
> build_ARCH
> toolchain_build_ARCH
> project_build_ARCH
It would help a lot if there was a dedicated make target for this.
We have has this problem several times now. Whenever we change a
configuration in the toolchain or in uclibc, everything needs to be
rebuilt. Unfortunately the Makefile does not automatically care about
this dependency. So one has make sure that the tree is clean before
running the build again. If there was a target that would take care of
this, that would help a lot.
Sven
prev parent reply other threads:[~2009-01-16 9:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 16:42 [Buildroot] Searching for the right "make clean" Dan Lyke
2009-01-15 22:27 ` Ulf Samuelsson
2009-01-16 9:42 ` Sven Neumann [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=1232098927.6639.10.camel@sven \
--to=s.neumann@phase-zero.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox