-
Notifications
You must be signed in to change notification settings - Fork 232
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bringing rules_boost to BCR #573
Comments
@nelhage A kind reminder about this issue. |
@hofbi It seems the bringing Boost to BCR (in a BCR idiomatic way) already started: I would keep this repo as a reference until we find a complete Boost 1.83.0 on the BCR. Feel free to join the effort and provide PRs to BCR |
Just a short update - meanwhile the following Boost 1.83.0 modules landed in the BCR:
I think in one month there will be even more... If someone needs a newer version (e.g 1.86.0) trivial copy & pasting and changing version numbers should do it in the most cases. |
We should bring rules_boost to the Bazel Central Registry.
In the long term there should be
rules_boost
(this repo) andboost
as drafted here in the BCR.I see
rules_boost
as 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.The text was updated successfully, but these errors were encountered: