Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ccache: make default host-ccache cache dir fit for multi-user setups
Date: Fri, 7 Jul 2017 09:28:08 +0200	[thread overview]
Message-ID: <20170707092808.23bae4fd@windsurf.lan> (raw)
In-Reply-To: <87y3s1w672.fsf@dell.be.48ers.dk>

Hello,

On Fri, 07 Jul 2017 00:28:49 +0200, Peter Korsgaard wrote:

>  > If I set BR2_CCACHE_DIR to /home/thomas/projects/foobar/ccache/, which
>  > works on my machine, you most likely won't
>  > have /home/jacmet/projects/foobar/ccache/ on your machine.  
> 
> No, but as far as I read the ccache code, it will create the cache dir +
> parent directories if they don't exist.
> 
> E.G.:
> 
> CCACHE_DIR=/tmp/some/funky/sub/directory ccache -s
> cache directory                     /tmp/some/funky/sub/directory
> primary config                      /tmp/some/funky/sub/directory/ccache.conf
> secondary config      (readonly)    /etc/ccache.conf
> cache hit (direct)                     0
> cache hit (preprocessed)               0
> cache miss                             0
> cache hit rate                      0.00 %
> cleanups performed                     0
> files in cache                         0
> cache size                           0.0 kB
> max cache size                       5.0 GB
> ls -l /tmp/some/funky/sub/directory
> total 4
> -rw-r--r-- 1 peko peko 16 Jul  7 00:26 ccache.conf

OK, but I definitely don't want ccache to create a random directory
somewhere in my $HOME folder, just because it was hardcoded into the
ccache binary.

> Hardcoding /home/thomas/.buildroot-ccache is very unlikely to work for
> other users, whereas ~/.buildroot-cache is quite likely.

Sure. But if I set BR2_CCACHE_DIR to /opt/ccache/, it won't work when
the SDK is moved to another machine (permissions may not be set), and
if I set BR2_CCACHE_DIR to $HOME/projects/foobar/cache/, and you run my
SDK on your system, you will get this funky folder created.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-07-07  7:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-06 10:48 [Buildroot] [PATCH] ccache: make default host-ccache cache dir fit for multi-user setups Peter Korsgaard
2017-07-06 19:21 ` Thomas Petazzoni
2017-07-06 22:28   ` Peter Korsgaard
2017-07-07  7:28     ` Thomas Petazzoni [this message]
2017-07-07  9:48       ` Peter Korsgaard
2017-07-07 15:18         ` Arnout Vandecappelle
2017-07-07 15:26           ` Peter Korsgaard
2017-07-06 23:18 ` Arnout Vandecappelle
2017-07-07  6:50   ` Peter Korsgaard
2017-07-08 18:55 ` Peter Korsgaard
2017-07-19 13:49 ` 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=20170707092808.23bae4fd@windsurf.lan \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox