From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Depend autotools targets on host-ccache when BR2_CCACHE is enabled.
Date: Sun, 26 May 2013 19:48:13 +0200 [thread overview]
Message-ID: <20130526194813.51f8e9bb@skate> (raw)
In-Reply-To: <CAHXCMMKHE+quVdK=HncViWGO=B38ncFKnBwvgn2AVLsW40KHFQ@mail.gmail.com>
Dear Samuel Martin,
On Sun, 26 May 2013 19:44:33 +0200, Samuel Martin wrote:
> In these cases, I rather suggest to build either a whole "small"
> config, or at least the toolchain
> before tweaking anything (packages, kernel or bootloader).
>
> Note that if we want to allow this use case, it may require adding BASE_TARGETS
> to all *-menuconfig and packages' targets.
>
> I think we don't want to go this way.
Being able to do "make linux-menuconfig" right after "make menuconfig"
is a quite important use case, IMO. We should support that I believe.
linux-menuconfig already depends on "dirs" so that it can work properly
when ran after "make menuconfig" (when ccache is not enabled). But I
see that it also depends on linux-configure. Maybe we just need to make
the *-extract of all packages depend on $(BASE_TARGETS) or something
like that?
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-05-26 17:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 15:37 [Buildroot] [PATCH] Depend autotools targets on host-ccache when BR2_CCACHE is enabled Raúl Sánchez Siles
2013-05-26 15:12 ` Samuel Martin
2013-05-26 15:44 ` Thomas Petazzoni
2013-05-26 17:00 ` Thomas Petazzoni
2013-05-26 17:44 ` Samuel Martin
2013-05-26 17:48 ` Thomas Petazzoni [this message]
2013-05-26 20:37 ` Samuel Martin
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=20130526194813.51f8e9bb@skate \
--to=thomas.petazzoni@free-electrons.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.