From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Report from the Buildroot Developer Day
Date: Fri, 18 Nov 2011 17:51:22 +0000 [thread overview]
Message-ID: <201111181751.22578.arnout@mind.be> (raw)
In-Reply-To: <CAEYzJUHexHVW+q95qUD3dVp5cTJp7Hu2yGShdkNr5w-rRfnoBw@mail.gmail.com>
On Friday 18 November 2011 11:04:58 Bj?rn Forsman wrote:
> Thomas P. had some concerns about the patch not handling staging-dir
> and I never got around fixing that.
>
> Should I resubmit even if the patch doesn't address the staging-dir issue?
I consider clean-staging less important than clean-target. Having things lingering around in staging is usually not a problem, except for the presence of some header or .pc of a library that is no longer present. Normally buildroot should disable old that in the configure step, but of course you can never be sure.
To implement a clean-staging, we'll probably need to use the copy-to-staging step of the external toolchains for all toolchains.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 31BB CF53 8660 6F88 345D 54CC A836 5879 20D7 CF43
next prev parent reply other threads:[~2011-11-18 17:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-02 15:03 [Buildroot] Report from the Buildroot Developer Day Thomas Petazzoni
2011-11-02 20:15 ` Peter Korsgaard
2011-11-04 11:56 ` Luca Ceresoli
2011-11-04 12:30 ` Michael S. Zick
2011-11-07 16:17 ` Peter Korsgaard
2011-11-07 9:58 ` Thomas De Schampheleire
2011-11-07 12:09 ` Sam Ravnborg
2011-11-07 12:25 ` Thomas Petazzoni
2011-11-07 12:39 ` Yann E. MORIN
2011-11-08 13:20 ` Thomas De Schampheleire
2011-11-07 12:39 ` Thomas Petazzoni
2011-11-07 19:01 ` Yann E. MORIN
2011-11-08 8:19 ` Thomas De Schampheleire
2011-11-15 22:17 ` Arnout Vandecappelle
2011-11-15 23:28 ` Michael S. Zick
2011-11-17 13:57 ` Thomas De Schampheleire
2011-11-17 21:21 ` Bjørn Forsman
2011-11-18 6:39 ` Thomas De Schampheleire
2011-11-18 11:04 ` Bjørn Forsman
2011-11-18 11:36 ` Thomas De Schampheleire
2011-11-18 17:51 ` Arnout Vandecappelle [this message]
2011-11-18 22:53 ` Peter Korsgaard
2011-11-18 23:16 ` Arnout Vandecappelle
2011-11-19 8:24 ` Peter Korsgaard
2011-11-20 8:36 ` Thomas Petazzoni
2011-11-20 9:58 ` Peter Korsgaard
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=201111181751.22578.arnout@mind.be \
--to=arnout@mind.be \
--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