You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, what is the blocker in creating a new version that considers the issues with boost::asio since version 1.70?
I'm aware that the develop branch addressed this issue, but the situation is far from being perfect, especially if you use libraries/repos that include websocketpp like i.e. cpprestsdk.
Attached is a patch for master that works with boost >= 1.70, tested under Windows by compiling the cpprestsdk (VS2017 and boost 1.170, VS2019 and bost 1.71 and 1.72).
Have you instead tried the two commits on the "develop" branch, which were committed/merged there in April 2019?: c769c92 f810ca2
They are supposed to fix build with boost:::asio >= 1.70.
Hi, what is the blocker in creating a new version that considers the issues with boost::asio since version 1.70?
I'm aware that the develop branch addressed this issue, but the situation is far from being perfect, especially if you use libraries/repos that include websocketpp like i.e. cpprestsdk.
Attached is a patch for master that works with boost >= 1.70, tested under Windows by compiling the cpprestsdk (VS2017 and boost 1.170, VS2019 and bost 1.71 and 1.72).
I know the patch is far from optimal, but it already would help all the cpprestsdk users that can't downgrade to boost 1.69.
0001-Make-websocketpp-usable-with-boost-1.70-and-higher.-.zip
The text was updated successfully, but these errors were encountered: