We should bring rules_boost to the Bazel Central Registry.
In the long term there should be rules_boost (this repo) and boost as drafted here in the BCR.
I see rules_boost as the short term solution and boost (as shown in the draft) as the long term solution. It is cleaner in some ways - for instance when depending only on a single header library of boost you are not forced to fetched the whole boost library. Or in cases when you depend only on single boost module (e.g. Boost Asio). Also the boost (as shown in the draft) enable us to support different boost version (e.g. 1.84.0 and 1.85.0) at the same time (some user might want stick to an old boost version for some reason). Futhermore, it does not need awkward workaround for "zlib.h" includes.
We should bring rules_boost to the Bazel Central Registry.
In the long term there should be
rules_boost(this repo) andboostas drafted here in the BCR.I see
rules_boostas the short term solution andboost(as shown in the draft) as the long term solution. It is cleaner in some ways - for instance when depending only on a single header library of boost you are not forced to fetched the whole boost library. Or in cases when you depend only on single boost module (e.g. Boost Asio). Also theboost(as shown in the draft) enable us to support different boost version (e.g. 1.84.0 and 1.85.0) at the same time (some user might want stick to an old boost version for some reason). Futhermore, it does not need awkward workaround for "zlib.h" includes.