Bazel for Open-source C / C++ Libraries Distribution

In the past a few days, I’ve been experimenting with Bazel as a library distribution mechanism for ccv.I am pretty familiar with hermetic build systems at this point. It is versatile enough to handle cases that have Bazel integrations and have no Bazel integrations.Consumption of the packaged Bazel dependencies then becomes as simple as adding git_repository to the WORKSPACE and call proper <your_library_name>_deps() repository rule.After packaging ccv with Bazel, now Swift for nnc can consume the packaged dependency.While the Bazel-provided library distribution mechanism works well for my case, it is simplistic. It is working so far, but one has to wonder whether this can scale if more libraries adopted Bazel as the distribution mechanism.The past a few months experience with Bazel has been delightful.