From: "Jérôme Pouiller" <jezz@sysmic.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Force rebuild of local site packages and theirs local dependencies
Date: Thu, 02 Jul 2015 17:32:55 +0200 [thread overview]
Message-ID: <1909260.QcAQmjlMXM@sagittea> (raw)
In-Reply-To: <5594FE06.5030900@syscom-instruments.com>
On Thursday 02 July 2015 11:01:58 Viallard Anthony wrote:
> On 06/23/2015 09:56 AM, J?r?me Pouiller wrote:
> > Does this process would work?
> >
> > rm build/*/.stamp_built
> > make
> >
> >
>
> Hi J?rome,
>
> Yes. It can be a solution. I already did this way to rebuild package in
> the old time when there wasn't the *-rebuild target command:
>
> rm -rf output/build/clearsilver-0.10.5/.stamp_built && rm -rf
> output/build/clearsilver-0.10.5/.stamp_configured
>
> But I prefer an integrated mechanism in the makefile which make the
> think more reliable and transparent :)
When I need very specific action for a project (generally 'run', 'check',
'flash', etc...), I write a fragment of Makefile and a declare it in
BR2_PACKAGE_OVERRIDE_FILE.
Therefore, you may add a local.mk file with:
local-rebuild:
rm build/*/.stamp_built
...and maybe (not tested):
$(PACKAGES): local-rebuild
(Someday, I will post a patch to be able to display those local targets in
'make help' output)
--
J?r?me Pouiller, Sysmic
Embedded Linux specialist
http://www.sysmic.fr
prev parent reply other threads:[~2015-07-02 15:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 13:21 [Buildroot] [PATCH 1/1] Force rebuild of local site packages and theirs local dependencies Anthony Viallard
2015-06-16 16:30 ` rdkehn at yahoo.com
2015-06-22 10:01 ` Viallard Anthony
2015-06-16 19:50 ` Thomas Petazzoni
2015-06-22 10:15 ` Viallard Anthony
2015-06-22 12:07 ` Viallard Anthony
2015-06-22 16:13 ` rdkehn at yahoo.com
2015-07-02 8:56 ` Viallard Anthony
2015-06-23 7:56 ` Jérôme Pouiller
2015-07-02 9:01 ` Viallard Anthony
2015-07-02 15:32 ` Jérôme Pouiller [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=1909260.QcAQmjlMXM@sagittea \
--to=jezz@sysmic.org \
--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