Explore >> Select a destination
|
You are here 
|
mill-build.org | ||
| | | | |
jmmv.dev
|
|
| | | | | This is a rare post because I don't usually talk about Google stuff here, and this post is about Bazel: a tool recently published by Google. Why? Because I love its internal counterpart, Blaze, and believe that Bazel has the potential to be one of the best build tools if it is not already. However, Bazel currently has some shortcomings to cater to a certain kind of important projects in the open source ecosystem: the projects that form the foundation of open source operating systems. This post is, exclusively, about this kind of project. | |
| | | | |
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. | |
| | | | |
readrust.net
|
|
| | | Read Rust collects and categorises interesting posts related to the Rust programming language. This page lists posts in the Performance category. | ||
