24 Aug
2015
24 Aug
'15
12:37 p.m.
Is there another workaround for this or have I overlooked something?
I don't think there is a workaround. There was a fix for this in the old trunk branch, but I don't know if it has been merged to the release branch.
Not being familiar with boost development, could you give me a pointer to the fix in the old trunk branch? Then I could have a look in the git repo to see if the fix exists there or otherwise create a pull request. Regards, Martin