Hacker News Reader

Comment by pjmlp | Hacker News Reader

Yes, cargo is perfect if you are willing to always compile from source, everything is Rust and one is willing to deal with everything else themselves in build.rs scripts.

Google and Microsoft aren't using cargo on their projects, rather had to come up with their own build tool.

View on HN

At Microsoft, we do use cargo internally but we make use of an internal crate registry.

Google's bazel/blaze predates rust. It has the advantage of supporting multiple languages

and is pretty much unuseable in the traditional unix setting where you are supposed to vendor nothing and use all the libraries of the OS however broken they may be

That's a feature, no?

That's less a limitation of the build system and more an intentional policy to ensure reproducible binaries etc.

Technically bazel can load any external files, but they must be tracked as workspace dependencies, which is more verbose:

E.g.

    new_local_repository(
        name = "system_libs",
        # pkg-config --variable=libdir x11
        path = "/usr/lib/x86_64-linux-gnu",
        build_file_content = """

cc_library( name = "x11", srcs = ["libX11.so"], visibility = ["//visibility:public"], ) """, )

Reply on news.ycombinator.com