-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add check for maximum boost version #231
Conversation
I added this to make bitshares-core build more easily. Maybe the check should go in bitshares-core, I'm not sure. |
67bafee
to
7c4b25e
Compare
I'm not sure if it's a good idea to do so, since we always look for supporting latest boost library although often we're a bit late. bitshares/bitshares-core#2216 |
This PR would make sense if you do another release before supporting the latest version of boost. |
We does support boost 1.70 and probably some higher versions. See bitshares/bitshares-core#2208. But the documentations are outdated. Fixing the documentations and adding support for higher boost versions are more productive IMHO. |
? Doesn't bitshares/bitshares-core#2208 say 1.70 is still on the backburner for bitshares/bitshares-core#2216 ? I'm still running into bitshares/bitshares-core#1935 when I try to use boost 1.70 [edit: with bitshares-core, of course. I haven't tried building bitshares-fc in any standalone way] maybe it would be helpful if I changed the PR to emit a warning instead of breaking the build or something |
You're on Windows? It seems #150 only fixed non-Windows build. |
Yeah, a warning would be better. Thanks. |
I'm actually on RHEL7 with a manually built boost. I'm looking at the cause of the error. I'm thinking the correct solution to this error would be to move the declaration of I'm going to try coding up a quicker and simpler fix that changes the hardcoded number to a sum of sizeof() calls, just for this one instance, and submit that as a PR unless I hear more from you. I see this PR is not the correct solution here. |
|
To close this out, wiping my build folder resolved this issue for me. If the sizeof approach is ever of interest, here was the change I had prepared. It's just the size of a pointer for the vtable if there are virtual functions, plus the size of every member:
|
Yes, the Update: |
No description provided.