Home
last modified time | relevance | path

Searched full:ccache (Results 1 – 15 of 15) sorted by relevance

/Zephyr-latest/cmake/modules/
Dccache.cmake3 # Use ccache if it is installed, unless the user explicitly disables
10 find_program(CCACHE_FOUND ccache)
12 set_property(GLOBAL PROPERTY RULE_LAUNCH_COMPILE ccache)
13 set_property(GLOBAL PROPERTY RULE_LAUNCH_LINK ccache)
Dzephyr_default.cmake84 list(APPEND zephyr_cmake_modules ccache)
/Zephyr-latest/cmake/sca/gcc/
Dsca.cmake26 # This option encounters a specific issue[1] when used with ccache.
27 # Therefore, currently, the build process is halted if 'ccache' is enabled.
28 # [1] https://github.com/ccache/ccache/issues/1466
30 …message(FATAL_ERROR "GCC SCA requires 'ccache' to be disabled for output file generation. Disable …
/Zephyr-latest/.github/workflows/
Dcodecov.yaml33 CCACHE_DIR: /node-cache/ccache-zephyr
36 # `--specs` is ignored because ccache is unable to resovle the toolchain specs file path.
81 - name: Set up ccache
84 ccache -M 10G
85 ccache -p
86 ccache -z -s -vv
112 - name: Print ccache stats
115 ccache -s -vv
Dtwister.yaml40 CCACHE_DIR: /node-cache/ccache-zephyr
43 # `--specs` is ignored because ccache is unable to resolve the toolchain specs file path.
115 - name: Set up ccache
118 ccache -M 10G
119 ccache -p
120 ccache -z -s -vv
176 - name: Print ccache stats
179 ccache -s -vv
/Zephyr-latest/boards/native/common/
Dnatsim_config.cmake5 get_property(CCACHE GLOBAL PROPERTY RULE_LAUNCH_COMPILE)
14 "NSI_CC:=${CCACHE} ${CMAKE_C_COMPILER}"
/Zephyr-latest/dts/riscv/starfive/
Djh7110-visionfive-v2.dtsi49 next-level-cache = <&ccache>;
74 next-level-cache = <&ccache>;
99 next-level-cache = <&ccache>;
124 next-level-cache = <&ccache>;
169 ccache: cache-controller@2010000 { label
175 compatible = "starfive,jh7110-ccache", "sifive,ccache0", "cache";
Dstarfive_jh7100_beagle_v.dtsi97 compatible = "sifive,fu540-c000-ccache", "starfive,ccache0", "cache";
/Zephyr-latest/cmake/
Dtarget_toolchain_flags.cmake11 # ccache will generate unique signatures
14 # methods, where an upgraded compiler could have same signature due to ccache
/Zephyr-latest/doc/develop/getting_started/
Dinstallation_linux.rst80 ccache dfu-util device-tree-compiler wget \
121 sudo pacman -S git cmake ninja gperf ccache dfu-util dtc wget \
Dindex.rst94 ccache dfu-util device-tree-compiler wget \
141 brew install cmake ninja gperf python3 python-tk ccache qemu dtc libmagic wget openocd
/Zephyr-latest/boards/intel/adsp/doc/
Dintel_adsp_generic.rst335 rm -rf ~/.ccache ~/.cache/zephyr
/Zephyr-latest/doc/releases/
Drelease-notes-1.7.rst407 * ``ZEP-1663`` - sanitycheck overrides user's environment for CCACHE
Drelease-notes-2.5.rst1256 * :github:`30531` - When using ccache, compiler identity stored in ToolchainCapabilityDatabase is a…
/Zephyr-latest/scripts/pylib/twister/twisterlib/
Denvironment.py849 which will ultimately disable ccache.