From: wberrier at uclibc.org <wberrier@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/toolchain/ccache
Date: Mon, 6 Oct 2008 12:14:41 -0700 (PDT) [thread overview]
Message-ID: <20081006191441.EF9D33C7C5@busybox.net> (raw)
Author: wberrier
Date: 2008-10-06 12:14:41 -0700 (Mon, 06 Oct 2008)
New Revision: 23604
Log:
ccache:
-Allow user to specify custom ccache location.
This allows you to build a toolchain and put it on
an nfs share so other people can use the toolchain
without errors about the ccache dir missing.
Modified:
trunk/buildroot/toolchain/ccache/Config.in
trunk/buildroot/toolchain/ccache/ccache.mk
Changeset:
Modified: trunk/buildroot/toolchain/ccache/Config.in
===================================================================
--- trunk/buildroot/toolchain/ccache/Config.in 2008-10-06 19:09:14 UTC (rev 23603)
+++ trunk/buildroot/toolchain/ccache/Config.in 2008-10-06 19:14:41 UTC (rev 23604)
@@ -7,3 +7,13 @@
help
Enable ccache support?
+config BR2_CCACHE_DIR
+ string "ccache dir location?"
+ depends on BR2_CCACHE
+ default "$(TOOL_BUILD_DIR)/ccache-$(CCACHE_VER)/cache"
+ help
+ Where ccache should store cached files.
+
+comment "ccache dir location? - disabled (requires ccache support)"
+ depends on !BR2_CCACHE
+
Modified: trunk/buildroot/toolchain/ccache/ccache.mk
===================================================================
--- trunk/buildroot/toolchain/ccache/ccache.mk 2008-10-06 19:09:14 UTC (rev 23603)
+++ trunk/buildroot/toolchain/ccache/ccache.mk 2008-10-06 19:14:41 UTC (rev 23604)
@@ -24,8 +24,9 @@
# Should probably patch things to use a relative path.
$(SED) "s,getenv(\"CCACHE_PATH\"),\"$(STAGING_DIR)/usr/bin-ccache\",g" \
$(CCACHE_DIR1)/execute.c
- # WARNING - this will break if the toolchain build dir is deleted.
- $(SED) "s,getenv(\"CCACHE_DIR\"),\"$(CCACHE_DIR1)/cache\",g" \
+ # WARNING - this will break if the toolchain build dir is deleted
+ # when using the default cache dir location.
+ $(SED) "s,getenv(\"CCACHE_DIR\"),\"$(BR2_CCACHE_DIR)\",g" \
$(CCACHE_DIR1)/ccache.c
mkdir -p $(CCACHE_DIR1)/cache
touch $@
next reply other threads:[~2008-10-06 19:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-06 19:14 wberrier at uclibc.org [this message]
2008-10-06 19:52 ` [Buildroot] svn commit: trunk/buildroot/toolchain/ccache Peter Korsgaard
2008-10-06 20:29 ` Wade Berrier
-- strict thread matches above, loose matches on Subject: below --
2008-10-06 20:28 wberrier at uclibc.org
2008-08-04 19:08 jacmet at uclibc.org
2008-08-04 19:08 jacmet at uclibc.org
2008-08-04 19:08 jacmet at uclibc.org
2008-08-04 19:07 jacmet at uclibc.org
2007-06-23 13:49 aldot at uclibc.org
2007-06-22 19:01 aldot at uclibc.org
2007-06-22 21:58 ` Julien Letessier
2007-06-23 8:39 ` Julien Letessier
2007-06-23 9:14 ` Bernhard Fischer
2007-02-03 21:07 andersen at uclibc.org
2007-02-03 0:52 andersen at uclibc.org
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=20081006191441.EF9D33C7C5@busybox.net \
--to=wberrier@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