wanted: websocketpp

[pvarcholik]

Module location

https://github.com/zaphoyd/websocketpp

Link to bzlmod issue in the module's repository

No response

Any other context to provide?

WebSocket++ is a C++11 header-only library that supports various transport layers included Boost.Asio and stand-alone Asio. This needs to compile under C++11, but it appears that the bazel build is pulling the stand-alone Asio library and it contains C++17 features. If possible, I'd like a bazel module that allows the use of Boost::Asio instead of the stand-alone library.

Fund our work

• Sponsor our community's open source work by donating a feature bounty

[hofbi]

Websocket in general is already available at https://registry.bazel.build/modules/websocketpp. However, it depends on https://registry.bazel.build/modules/asio/1.28.2 which uses some C++17 features. According to the readme, we could replace standalone asio with boost.asio.

Question to the maintainers (@meteorcloudy since you approved the PRs). Should we create a completely new module such as websocket-boost or just a new version such as 0.8.2.boost?

[meteorcloudy]

Sorry I don't have much insight into this specific library, I was approving as a general BCR maintainer. /cc @BYVoid @lalten who actually contributed the PRs.

[lalten]

The reason I touched asio was to bring mvukov/rules_ros2#238 forward. rules_ros2 needs asio in Workspace and I adapted the Bzlmod version to be compatible so the repo can use the same implementation for both modes.

I've seen @keith use some neat tricks for Bzlmod curl to switch the TLS backend:

bazel-central-registry/modules/curl/8.8.0/patches/add_build_file.patch

Lines 302 to 305 in dee0784

	+ deps = select({
	+ ":use_mbedtls_setting": ["@mbedtls"],
	+ "//conditions:default": [],
	+ }),

Possibly you could do something similar for WebSocket++ to switch between Boost Asio and Standalone Asio.

Cc also @wep21 who has contributed the most recent incarnation of Boost Bzlmods

[hofbi]

I came up with this first draft