ccache.bbclass: Allow user to override CCACHE_DIR.
PATCH 1/1 ccache.bbclass: Allow user to override CCACHE_DIR.
In reply to a message not in the archiveFor example, some users may want to use single cache directory (instead of per-package) with known max size limit, to better control disk usage.
--- meta/classes/ccache.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
meta/classes/ccache.bbclass +1 -1
@@ -1,5 +1,5 @@ CCACHE = "${@bb.which(d.getVar('PATH', True), 'ccache') and 'ccache '}" -export CCACHE_DIR = "${TMPDIR}/ccache/${MULTIMACH_HOST_SYS}/${PN}" +export CCACHE_DIR ?= "${TMPDIR}/ccache/${MULTIMACH_HOST_SYS}/${PN}" CCACHE_DISABLE[unexport] = "1" do_configure[dirs] =+ "${CCACHE_DIR}"
Signature · 1 line
1.7.9.5
Paul Sokolovsky <[email protected]>
Quoted 2 lines · writes:
For example, some users may want to use single cache directory (instead of per-package) with known max size limit, to better control disk usage.
You change conflicts with
| do_clean[cleandirs] += "${CCACHE_DIR}"
To use ccache, it is the best to avoid this class completely and to remove
| export CCACHE_DISABLE ??= "${@[0,1][d.getVar('CCACHE', True) == '']}"
from bitbake.conf.
Enrico
Hello,
Quoted 10 lines · On Sun, 10 Feb 2013 14:48:58 +0100 Enrico Scholz…
Paul Sokolovsky <[email protected]>
Quoted 3 lines · writes:
For example, some users may want to use single cache directory (instead of per-package) with known max size limit, to better control disk usage.
You change conflicts with
| do_clean[cleandirs] += "${CCACHE_DIR}"
Good catch, thanks.
Signature · 2 lines
Best regards, Paul mailto:[email protected]