-
Updated
Jun 27, 2022 - CMake
ccache
Here are 30 public repositories matching this topic...
-
Updated
May 17, 2022 - CMake
Something like:
BUILDCACHE_DISABLE
Bla, bla, bla...
...
BUILDCACHE_TERMINATE_ON_MISS
Bla, bla, bla...
Introduced in #128.
The original reason for that is purely technical - it is required to call unshare(CLONE_NEWUSER) in the main thread of a program. Since cachepot-dist is multi-threaded and the build is executed on a new thread, we used a hack in which we fork() and call unshare in the forked child (fork() forks the calling thread into a main thread of a forked child process).
Us
-
Updated
Sep 7, 2021
-
Updated
Jul 6, 2022 - TypeScript
-
Updated
Apr 1, 2019
-
Updated
Aug 13, 2019 - Dockerfile
-
Updated
Sep 23, 2020
-
Updated
Oct 19, 2021 - Python
-
Updated
Apr 16, 2022
-
Updated
Jan 6, 2019 - C
-
Updated
Mar 8, 2019 - Python
-
Updated
Jan 20, 2022 - Mako
-
Updated
Mar 8, 2019
-
Updated
Feb 22, 2022 - Shell
Improve this page
Add a description, image, and links to the ccache topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the ccache topic, visit your repo's landing page and select "manage topics."
GCC and Clang have a
-frandom-seedcompiler option. The idea is to improve reproducibility by allowing the build system to specify random seeds for symbols that are randomly generated by the compiler.ccache should ignore
-frandom-seedin compiler options when looking for cache hits. Currently two compiler invocation command lines that are strictly identical except for the random seed will