Ninja Build VS Bazel

Under the hood, Rescript uses a build system called Ninja. Ninja is similar to Make, but cross-platform and more minimal/performant. - Source: dev.to / 3 months ago

Ninja was super easy to pick up even after using make for some time (10+ years). GN is just a ninja generator that is optional. https://gn.googlesource.com/gn/+/main/docs/quick_start.md https://ninja-build.org/. - Source: Hacker News / 4 months ago

Really? I thought most new projects were switching to ninja[^1] and have never used it. [^1]: https://ninja-build.org/. - Source: Hacker News / 6 months ago

Ninja showed real promise for a while, but then CMake grew up and people stopped seeing a reason to leave it behind. Source: 10 months ago

Now that you have your build system all generated you can go ahead and build everything. By default Meson will use Ninja as the build tool. Ninja is similar to Make but much much faster. You can also generate additional build systems but that's outside of the scope of this post. - Source: dev.to / 12 months ago

Wow, if you curl it, there's a lot of boilerplate code there. Maybe built using Bazel? https://bazel.build. - Source: Hacker News / about 2 hours ago

This is a problem that Bazel (https://bazel.build) solves in a very convenient way. You can just keep using the paths relative to the repository root, and as long as you properly declare your test needs that file it will access it without problems. Or you can use the runfile libraries to access them too. - Source: Hacker News / about 2 months ago

When doing research for this lab exercise I looked at both vcpkg and conan. Both are package managers that would automate the installation and configuration of my program with its dependencies. However, when it came to releasing and sharing my program my options were limited. For example, the central public registry for conan packages is conan-center, but these packages are curated and the process is very... - Source: dev.to / 5 months ago

NOTE: I won’t mention SBT and Leiningen here because, with all due respect, they are niche build tools. I also won’t discuss Kobalt for the same reason (besides, it’s no longer actively maintained). Additionally, I won’t touch upon Bazel and Buck in this context, mainly because I’m not very familiar with them. If you have insights or comments about these tools, please feel free to share them in the comments 👇. - Source: dev.to / 5 months ago

> None of this solves C's only REAL problem (in my opinion) which is the lack of dependency management. Bazel solves this really nicely, I know some people have strong opinions on it but I cannot recommend it enough https://bazel.build/. - Source: Hacker News / 8 months ago