icecream
gg
icecream | gg | |
---|---|---|
16 | 5 | |
1,553 | 985 | |
0.6% | 0.0% | |
0.0 | 0.0 | |
5 days ago | about 1 year ago | |
C++ | C++ | |
GNU General Public License v3.0 only | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
icecream
- Icecream: Distributed compiler with a central scheduler to share build load
-
Distcc: A fast, free distributed C/C++ compiler
Related
https://github.com/icecc/icecream - another option that does what distcc does, but aimed at a somewhat different use case.
https://ccache.dev/ - a similar idea but provides caching of build outputs instead of distributing builds. You can use it together with distcc to achieve even better performance.
-
Do you use ccache to speed up compilation times
Of course! The github readme provides a lot of info - https://github.com/icecc/icecream
- GitHub - icecc/icecream: Distributed compiler with a central scheduler to share build load
-
Ccache – a fast C/C++ compiler cache
If you like distcc, did you ever give icecc a try?
https://github.com/icecc/icecream
I never had the time to set it up properly, but by the looks of it, it should be even better.
- People who use distributed builds, how do you handle many compilers?
- Fuchsia Workstation
-
Give local devices a way to connect to clients? - openvpn
I would like to have a icecc setup I can vpn into. It seems that with normal configs the clients can talk to the scheduler, but the scheduler cant connect to the clients as it tries to connect to the device running the openvpn server not the one behind it. How could I make my openvpn clients appear almost as physical devices on the network, with unique IP's that local devices can connect to; or if that is unnecessary how could I solve this?
-
ccache 4.6 released
Glad to see a new release on this! I've read worrying news about the state of icecc, and the followup uncertain news on sccache, so I hope at least some part of the tooling is in a good shape.
-
Best way to manage dependencies with c++?
I always wanted to try to use cmake-conan so I could let Conan grab all packages but have a neat cmake script being in charge of what gets built when. Also, this would allow me to easily switch between CMake fetchcontent and Conan packages that may or may not be stashed automatically on a local Artifactory server. Secondly, since now all build requirements are stashed on a server and binary reproducible, you could concider adding icecream and ccache into the mix. (Try running a node one of your buildservers for massive speadups with icecream) This however does require a reproducible build environment (by configure script) which conan again is really good in.
gg
-
Migrating Your Open Source Builds Off Of Travis CI
Another interesting option if you are feeling adventurous is using AWS lambda as your build executor. I have no idea how feasible this is, however, the gg project from Stanford looks interesting. It attempts to use AWS lambdas for running builds at the maximum possible parallelism.
- Gg – The Stanford Builder
-
Building LLVM in 90 seconds using Amazon Lambda
This is very similar to https://github.com/StanfordSNR/gg by Keith Weinstein's group at Stanford. Cool stuff! Have always wondered why Keith's work hasnt made its way into large companies (besides I think Facebook? not sure)
- Comments About Build Systems and CI Services
-
Distcc – distribute builds across multiple machines simultaneously
Running it locally will always be faster as long as your machine is not a bottleneck (#cores, ram, ...). I think the use-case for distcc et al is to enable less-powerful machines to run builds faster by levering other machines. That’s exactly what we use it for at work. Our developers have not-so-powerful laptops and with distcc/icecc they can utilize the power of our build agents in the server room.
Also interesting to read: https://github.com/StanfordSNR/gg
What are some alternatives?
sccache - Sccache is a ccache-like tool. It is used as a compiler wrapper and avoids compilation when possible. Sccache has the capability to utilize caching in remote storage environments, including various cloud storage options, or alternatively, in local storage.
ccache - ccache – a fast compiler cache
zapcc - zapcc is a caching C++ compiler based on clang, designed to perform faster compilations
keppel - Regionally federated multi-tenant container image registry
Buildkite - The Buildkite Agent is an open-source toolkit written in Go for securely running build jobs on any device or network
compiler-benchmark - Benchmarks compilation speeds of different combinations of languages and compilers.
Phoenix - Peace of mind from prototype to production
cmake-init-conan-example - cmake-init generated executable project with Conan integration
bazelisk - A user-friendly launcher for Bazel.
reactos - A free Windows-compatible Operating System
cmake-init-vcpkg-example - cmake-init generated executable project with vcpkg integration