Can't utilize ccache with a custom compiler #253
Comments
vlovich
added a commit
to vlovich/wasi-libc
that referenced
this issue
Sep 1, 2021
If using a custom toolchain not on the path, explicitly invoking ccache/sccache is required (also easier to debug that the right compiler is being invoked). Fixes WebAssembly#253.
vlovich
added a commit
to vlovich/wasi-libc
that referenced
this issue
Sep 8, 2021
If using a custom toolchain not on the path, explicitly invoking ccache/sccache is required (also easier to debug that the right compiler is being invoked). Fixes WebAssembly#253.
sbc100
pushed a commit
that referenced
this issue
Sep 22, 2021
If using a custom toolchain not on the path, explicitly invoking ccache/sccache is required (also easier to debug that the right compiler is being invoked). Fixes #253.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Typically one might expect to be able to supply
make WASM_CC="ccache <path to clang>"to override the compiler & use ccache, but the use of double-quotes invoking the compiler ("$(WASM_CC)") inhibits this. The double-quotes should be removed or perhaps a newWASM_CC_WRAPPERintroduced that can be used to inject ccache?The text was updated successfully, but these errors were encountered: