-
Notifications
You must be signed in to change notification settings - Fork 769
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
Fix/boost issue #713 again #732
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
@varunagrawal What do you think? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any reason you have added the <boost/serialization/optional.hpp>
headers for FastList.h and SubgraphBuilder.h?
To be precise, I started again with the latest develop version and iteratively added changes to get rid of the errors:
I added
I simply moved include of |
As my inspection showed, it is needed for |
@Alevs2R please add back the header to SubgraphBuilder.h since I believe that is required to work on Boost 1.74. Once you do that, I can approve. Thanks a lot for the great work and explanation!! |
@varunagrawal done! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thanks a lot @Alevs2R
Please merge once the CI passes. :) |
Fixes issue #634
Fixes order of #include <boost/serialization/version.hpp> headers
My compilation on Ubuntu failed with the same error as in issue #634
Changing order of includes fixed my compilation.
<boost/serialization/version.hpp>
should be included before<boost/serialization/list.hpp>
and before<boost/shared_ptr.hpp>
, not after.Also it was needed to add includes to
FastList.h
to avoid the same compilation errors.boost version: 1.74.0
gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
Probably this issue will not appear in boost version 1.75, but I tested only with 1.74