Closed severin-lemaignan closed 3 years ago
The fix consists in removing <void>
from expressions like boost::bind<void>(...)
.
Indeed, master branch is compatible only with Boost 1.59 release-2.4 branch is compatible with Boost 1.55, but there is nothing in between, we made a 1.55-1.59 jump README file is lacking this information (issue #13)
PS: Hi Séverin!
Hum... this is a pity: ubuntu 16.04 comes with boost 1.58... I was about to submit a PR so that it also compiles on boost 1.58. Would you consider merging it if it does not impair boost 1.59 compilation?
PS: hi Vincent ;-)
Of course, submit a PR, we'll check it with our code base and integrate it.
That being said, we provide public toolchains if you need boost-1.59: https://github.com/aldebaran/toolchains The behavior with 1.58 hasn't been tested, so there could be bugs
Here you are :-)
Behavior with boost-1.58 has been unofficially tested. And this version got a lot of bugs. So we accept to not support it. We unofficially go from 1.57 to 1.59. Officially it's 1.55 -> 1.59. But we are of course always open to more compatibility.
Like some other issues with libqi stuff I also ran into this. I would appreciate if the PR was merged.
The current versions (in team/platform/dev) works with boost 1.59 and 1.64. I'll update master soon but it should already have been compiling with 1.59 as mentionned by @vbarbaresi .
Do you still have issues?
If boost 1.59 is downward compatible with 1.58, then no :)
It's not, but issues we had when upgrading to 1.59 should also help for 1.58. We also rewrote Eventloop internals so if you could check if you still have problems with team/platform/dev branch that would help us identify what is now missing for 1.58.
Okay, thx I will give it a try.
Compilation fails with the following error:
Tried on ubuntu 16.04 with both gcc-5.3.1 and clang-3.8.