Explore >> Select a destination
|
You are here 
|
tmandry.gitlab.io | ||
| | | | |
fzakaria.com
|
|
| | | | | You might hear a lot of about how Bazel is "reproducible" and "hermetic", but what does that even mean ? ?? Part of what makes Bazel incredibly fast is it effectively skips work by foregoing doing portions of the graph if the inputs have not changed. Let's consider this simple action graph in Bazel. | |
| | | | |
galowicz.de
|
|
| | | | | Most big C++ projects lack a clear structure:They consist of multiple modules, but it is not as easy to create individuallybuildable, portable, testable, and reusable libraries from them, as it is withprojects written in Rust, Go, Haskell, etc.In this article, I propose a C++ project structure using CMake that makes iteasy to have incremental monorepo builds and a nice modular structure at thesame time. | |
| | | | |
mill-build.org
|
|
| | | | | [AI summary] The blog post explores the inner workings of modern build tools, emphasizing their use of a build graph to manage tasks efficiently. It compares tools like Bazel, Gradle, and Mill, highlighting how each defines and processes the build graph. The post explains caching, parallelism, and the importance of a structured build graph in optimizing build processes. It also discusses the advantages of using a programming language for defining build configurations, such as better IDE support, compiler assistance, and access to a rich library ecosystem. The conclusion underscores that while build tools may appear different on the surface, they share a common goal of enhancing development efficiency through automation and optimization. | |
| | | | |
blog.orhun.dev
|
|
| | | FOSS ? Linux ? Programming | ||
