Please VS Bazel

I’m not sure a JS library qualifies as a PL. Or automation software (SoftStack). Or an API description language. Or a build system. Source: about 1 year ago

Regarding your first point, a good alternative to Bazel is [Please][https://please.build/] - its build graph can solve exactly this problem in CI. - Source: Hacker News / over 1 year ago

Checkout: https://please.build/ - CMake is not directly supported, but you can easily extend please.build to invoke cmake commands to build your targets. - It does supports both Windows(ehweee) and Linux - MIT - BONUS: it is fast. Really fast(||)! Single binary. It is also versatile. I am using it to build a repo with multiple programming languages(C++(Wasm),Go,Js, Flutter), while spinning up vagrant and... Source: over 1 year ago

> the best way forward is to take the ideas of Bazel (hermetic and deterministic builds) and package them as a good small build system, perhaps even compatible with Bazel so you don't have to rewrite build rules all the time. How does https://please.build measure up? - Source: Hacker News / over 1 year ago

Good luck! I assume you are aware of please.build? Source: over 1 year ago

Wow, if you curl it, there's a lot of boilerplate code there. Maybe built using Bazel? https://bazel.build. - Source: Hacker News / 8 days 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 / 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 / 6 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 / 9 months ago