All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas De Schampheleire <patrickdepinguin+buildroot@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] ccache: allow dynamic selection of cache directory
Date: Tue, 15 May 2012 21:23:27 +0200	[thread overview]
Message-ID: <CAAXf6LW4iDFCRoqs-1kyjEg=jw9DvBzgriG+WucCTO_k6r3DGw@mail.gmail.com> (raw)
In-Reply-To: <20120515205732.71d2310d@skate>

On Tue, May 15, 2012 at 8:57 PM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> Le Tue, 15 May 2012 20:49:35 +0200,
> Thomas De Schampheleire <patrickdepinguin+buildroot@gmail.com> a ?crit :
>
>> > Euh? Why wouldn't we use CCACHE_DIR directly? What's the need of
>> > renaming this environment variable here?
>>
>> Because CCACHE_DIR is already used by gentargets/autotargets...
>
> Where?
>
> $ git grep CCACHE_DIR | cat
> package/ccache/ccache.mk:define HOST_CCACHE_FIX_CCACHE_DIR
> package/ccache/ccache.mk: ? ? ? sed -i 's,getenv("CCACHE_DIR"),"$(CCACHE_CACHE_DIR)",' $(@D)/ccache.c
> package/ccache/ccache.mk: ? ? ? HOST_CCACHE_FIX_CCACHE_DIR

It's not defined directly like that.
ccache is a package in its own right, using autotools.
(package/ccache/ccache.mk).

The variable CCACHE_DIR originates from the following line in
package/pkg-gentargets.mk:
$(2)_DIR        =  $$(BUILD_DIR)/$$($(2)_BASE_NAME)

Best regards,
Thomas

  reply	other threads:[~2012-05-15 19:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-06 18:47 [Buildroot] [PATCH v2] ccache: allow dynamic selection of cache directory Thomas De Schampheleire
2012-05-04 19:17 ` Thomas De Schampheleire
2012-05-04 20:46 ` Arnout Vandecappelle
2012-05-05  7:17   ` Thomas De Schampheleire
2012-05-15 18:13     ` Thomas De Schampheleire
2012-05-15 18:28   ` Thomas Petazzoni
2012-05-15 18:49     ` Thomas De Schampheleire
2012-05-15 18:57       ` Thomas Petazzoni
2012-05-15 19:23         ` Thomas De Schampheleire [this message]
2012-05-15 19:50           ` Thomas Petazzoni
2012-05-15 20:42             ` 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='CAAXf6LW4iDFCRoqs-1kyjEg=jw9DvBzgriG+WucCTO_k6r3DGw@mail.gmail.com' \
    --to=patrickdepinguin+buildroot@gmail.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.