Age | Commit message (Collapse) | Author | Files | |
---|---|---|---|---|
2012-07-10 | ccache: Ensure CCACHE_DIR is cleaned by do_clean task | Richard Purdie | 1 | |
This ensures a rebuild does really build from scratch when ccache is in use. [YOCTO #2696] Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> | ||||
2012-06-28 | bitbake.conf: disable ccache explicitly if it is not enabled | Robert Yang | 1 | |
The autogen-native built error on FC17: ccache: failed to create /dev/null/.ccache This is because the default gcc command of FC17 is a symlink to ccache, so the ccache will always be used regardless to the setting of CCACHE, ccache uses $HOME/.ccache as the CACHE_DIR by default, but autogen set HOME=/dev/null, so the error happens. Disable ccache explicitly if it is not enabled would fix the problem, otherwise it would always use ccache regardless to the setting of CCACHE on Fedora 17. The ccache 3.1.7 has a bug, it would always create $CCCHE_DIR/.ccache even CCACHE_DISABLE=1. Unset CCACHE_DISABLE in ccache.bbclass, since ccache only checks whether there is a CCACHE_DISABLE in the environment or not, it doesn't care about its value, so we need unset it explicitly when enable ccache. [YOCTO #2554] Signed-off-by: Robert Yang <liezhi.yang@windriver.com> | ||||
2012-05-30 | ccache: Separate out into its own class | Richard Purdie | 1 | |
Currently, ccache is used if it is present. When building from scratch it gives no performance improvement and creates a ton of empty directories even when its not in use. This change moves ccache support to a bbclass file which the user can choose to enable. This should make builds more determinstic and make it easier/clearer to the end user when its being used and when it is not. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> |