Explore >> Select a destination
|
You are here 
|
mill-build.org | ||
| | | | |
tmandry.gitlab.io
|
|
| | | | | At my company, we are moving our medium-sized C++ and Python codebase from CMake to Bazel. Moving to a new build system is a lot of work, so naturally, it has to be justified. Here are the benefits most important to us. First-class build system for C++ Our primary language today is C++, which doesn't have a standard build system. Bazel's C++ support is very good, and supports everything from code coverage reports to profile-guided optimization. | |
| | | | |
ashvardanian.com
|
|
| | | | | Experienced devs may want to skip the intro or jump immediately to the conclusions. The backbone of many foundational software systems - from compilers and interpreters to math libraries, operating systems, and database management systems - is often implemented in C and C++. These systems frequently offer Software Development Kits (SDKs) for high-level languages like Python, JavaScript, GoLang, C#, Java, and Rust, enabling broader accessibility. But there is a catch. | |
| | | | |
www.lihaoyi.com
|
|
| | | | | [AI summary] The article discusses the concept of build tools as directed acyclic graphs (DAGs) of tasks, emphasizing the potential of using pure-functional programming paradigms to model and execute builds. It highlights how tools like Mill and Bazel leverage these principles to enable caching, parallelism, and queryability. The author advocates for a build tool that seamlessly integrates with pure-functional programs, allowing developers to write builds in a familiar style while benefiting from the efficiency and flexibility of DAG-based execution. | |
| | | | |
www.davefarley.net
|
|
| | | |||
