From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] linux custom tarball: automatically detect a change in tarball configuration
Date: Tue, 27 Sep 2011 08:18:36 +0200 [thread overview]
Message-ID: <201109270818.37828.arnout@mind.be> (raw)
In-Reply-To: <CAAXf6LWbsf0WP-A_n3DkV2mdRn54CiL=3AWFckDeuF=L2-Y31A@mail.gmail.com>
On Friday 23 September 2011 08:16:09, Thomas De Schampheleire wrote:
> > I agree that their is a minor inconvenience in having the directory
> > always named linux-custom/, but I don't have a good solution in mind.
>
> The other solution that I implemented in buildroot-2010.11 is to make
> the download step depend on the tarball, instead of on a stamp file.
> Since linux now uses gentargets, this would require a change in the
> whole of gentargets as well.
> Essentially, the .stamp_downloaded file would be no longer needed, and
> the tarball would serve as stamp file.
>
> Would you prefer such a solution?
I certainly would.
I never really understood why the dependencies are between the phony targets
instead of the stamp files. Otherwise, I could just touch a stamp file to
force all subsequent build steps to run. However, I guess the buildroot
masters must have their reasons :-)
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 part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110927/54579cfd/attachment-0001.html>
next prev parent reply other threads:[~2011-09-27 6:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-21 8:55 [Buildroot] [PATCH] linux custom tarball: automatically detect a change in tarball configuration Thomas De Schampheleire
2011-09-22 19:58 ` Thomas Petazzoni
2011-09-23 6:16 ` Thomas De Schampheleire
2011-09-27 6:18 ` Arnout Vandecappelle [this message]
2011-09-27 8:56 ` Daniel Nyström
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=201109270818.37828.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