From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/toolchain/ccache
Date: Mon, 06 Oct 2008 21:52:31 +0200 [thread overview]
Message-ID: <871vyt1oxs.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20081006191441.EF9D33C7C5@busybox.net> (wberrier@uclibc.org's message of "Mon\, 6 Oct 2008 12\:14\:41 -0700 \(PDT\)")
>>>>> "wberrier" == wberrier <wberrier@uclibc.org> writes:
wberrier> Author: wberrier
wberrier> Date: 2008-10-06 12:14:41 -0700 (Mon, 06 Oct 2008)
wberrier> New Revision: 23604
wberrier> Log:
wberrier> ccache:
wberrier> -Allow user to specify custom ccache location.
...
wberrier> +config BR2_CCACHE_DIR
wberrier> + string "ccache dir location?"
wberrier> + depends on BR2_CCACHE
wberrier> + default "$(TOOL_BUILD_DIR)/ccache-$(CCACHE_VER)/cache"
wberrier> + help
wberrier> + Where ccache should store cached files.
wberrier> +
wberrier> +comment "ccache dir location? - disabled (requires ccache support)"
wberrier> + depends on !BR2_CCACHE
wberrier> +
Do we really need that comment line? Would anyone go looking for
something like this if they weren't using ccache in the first place?
wberrier> Modified: trunk/buildroot/toolchain/ccache/ccache.mk
wberrier> ===================================================================
wberrier> --- trunk/buildroot/toolchain/ccache/ccache.mk 2008-10-06 19:09:14 UTC (rev 23603)
wberrier> +++ trunk/buildroot/toolchain/ccache/ccache.mk 2008-10-06 19:14:41 UTC (rev 23604)
wberrier> @@ -24,8 +24,9 @@
wberrier> # Should probably patch things to use a relative path.
wberrier> $(SED) "s,getenv(\"CCACHE_PATH\"),\"$(STAGING_DIR)/usr/bin-ccache\",g" \
wberrier> $(CCACHE_DIR1)/execute.c
wberrier> - # WARNING - this will break if the toolchain build dir is deleted.
wberrier> - $(SED) "s,getenv(\"CCACHE_DIR\"),\"$(CCACHE_DIR1)/cache\",g" \
wberrier> + # WARNING - this will break if the toolchain build dir is deleted
wberrier> + # when using the default cache dir location.
wberrier> + $(SED) "s,getenv(\"CCACHE_DIR\"),\"$(BR2_CCACHE_DIR)\",g" \
Why do we even do this in the first place? What's wrong with the user
simply setting CCACHE_DIR like they expect to do for ccache?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2008-10-06 19:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-06 19:14 [Buildroot] svn commit: trunk/buildroot/toolchain/ccache wberrier at uclibc.org
2008-10-06 19:52 ` Peter Korsgaard [this message]
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=871vyt1oxs.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