From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] ccache directory
Date: Wed, 20 Jul 2011 18:19:55 +0200 [thread overview]
Message-ID: <20110720181955.36911f14@skate> (raw)
In-Reply-To: <CAAXf6LUROj4Pg2TLKETfo5SNYuC=teuFbcHEyhELuvmmTNTwvw@mail.gmail.com>
Le Wed, 20 Jul 2011 17:42:52 +0200,
Thomas De Schampheleire <patrickdepinguin+buildroot@gmail.com> a ?crit :
> A while ago, there were some changes in the ccache handling, with
> which the cache location also changed to $(HOME)/.buildroot-ccache.
> Before that, the cache directory was configurable in .config. What is
> the reason of changing the cache location?
Simplifying the ccache support, mainly.
> In my (corporate) environment, the home directories are actually on
> the network (NFS) which is not ideal for performance. I would like to
> configure another cache directory.
>
> Would you accept a patch that re-introduces BR2_CCACHE_DIR ?
I guess your use case is valid, so I would personally accept such a
patch. I don't like cluttering the "Build options" menu with too many
options, but I guess this option is a valid thing to have when ccache
support is enabled.
Regards,
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:[~2011-07-20 16:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 15:42 [Buildroot] ccache directory Thomas De Schampheleire
2011-07-20 16:19 ` Thomas Petazzoni [this message]
2011-07-20 20:49 ` Peter Korsgaard
2011-07-21 5:58 ` Thomas Petazzoni
2011-07-21 10:48 ` Michael S. Zick
2011-07-21 16:11 ` Peter Korsgaard
2011-07-24 11:23 ` Thomas De Schampheleire
2011-07-24 12:49 ` Peter Korsgaard
2011-07-24 16:06 ` Peter Korsgaard
2011-07-24 19:21 ` Thomas De Schampheleire
2011-07-24 20:07 ` Peter Korsgaard
2011-07-24 20:12 ` Yann E. MORIN
2011-07-26 7:38 ` Thomas De Schampheleire
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=20110720181955.36911f14@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.