Nicolai Grodzitski
Nicolai Grodzitski
We would definitely make changes based on PR. Actually, some parts of it are already in our private dev repos on bitbucket (move to newer catch). But it would take...
Hi @petterreinholdtsen Proposed workaround looks good to me (it can be integrated in the same fashion like we do with `link_threads_if_necessary`). The only issue is how to test the fix,...
Separate branch, sure.
@petterreinholdtsen Can you test https://github.com/Stiffstream/restinio/tree/0.6-fix-libatomic-issue-98, please?
It expects dev/so_5 (https://github.com/Stiffstream/sobjectizer) which is obtained by mxxruexternals (a part of Mxx_ru - ruby-based build tool, it is a very simple package manager, and most likely it is absent...
Hi Jean-Marc, I've taken a look on [amqp-cpp](https://github.com/CopernicaMarketingSoftware/AMQP-CPP), and I'm pretty sure restinio and amqp-cpp can coexist in a single application. Even though boost-asio is not manifested as officially supported...
> For now I'll be adding patches to fix issues in my portfile. Can you, please, share your patch with us? And by the way, regarding MacPorts (no experience with...
Hi, @aacirino Did you handle it in any way? Could you, please, share a workaround if any?
> Libraries together in Boost work well and interoperate with each other. Boost.Beast and Boost.Asio. Boost.URL and Boost.Beast. Boost.JSON and everything else. And my new libraries Boost.Http.Proto and Boost.Http.IO which...
Here are the details behind the change: https://gist.github.com/ngrodzitski/f9de8fb60ae44e7c5455f9b78a2e4134