From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] ccache directory
Date: Sun, 24 Jul 2011 14:49:42 +0200 [thread overview]
Message-ID: <874o2byhax.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <CAAXf6LUHjWVv794Voi40DPOy+QAaZNpdVKp8Z-k=yFcRtxay-Q@mail.gmail.com> (Thomas De Schampheleire's message of "Sun, 24 Jul 2011 13:23:13 +0200")
>>>>> "Thomas" == Thomas De Schampheleire <patrickdepinguin+buildroot@gmail.com> writes:
Hi,
>> That's another possibility, but I find it quite confusing to have some
>> parameters set by environment variables, and some other by
>> configuration options.
Thomas> The disadvantage with this particular configuration variable, is that
Thomas> it requires a forced recompilation of host-ccache in order for changes
Thomas> to this variable to take effect.
Thomas> Another solution is to remove the hardcoded cache directory, use the
Thomas> CCACHE_DIR environment variable, but let buildroot set that variable
Thomas> based on BR2_CCACHE_DIR (a configuration option). This addresses
Thomas> Thomas' point regarding mixing environment variables and configuration
Thomas> options, and my request of being able to change the cache directory
Thomas> and making sure these changes are automatically in effect.
Thomas> What do you think?
Yes, something like:
# use BR setting if not set in environment
ifndef CCACHE_DIR
CCACHE_DIR:=$(call qstrip,BR2_CCACHE_DIR)
endif
export CCACHE_DIR
in the toplevel Makefile.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2011-07-24 12:49 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
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 [this message]
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=874o2byhax.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.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