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
Only find Boost.Iostreams if required for plugins #5233
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.
Don't we need Boost.Iostreams for our iostream component as well?
Good question. Apparently not given that it hasn't been linked so far. It does need the headers, but it'd be better to link explicitly to the Boost::iostreams since it's mostly luck if the headers were enough. I'll change that. |
f4b1da9
to
f01c5f6
Compare
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!
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!
f01c5f6
to
729f3ed
Compare
I changed my mind on this. Given that iostreams pulls in an unnecessary regex dependency, and they document which headers can be used with header-only boost (https://www.boost.org/doc/libs/1_75_0/libs/iostreams/doc/index.html), I think it's ok to not link to the iostreams library. I take back my statement that it worked mostly through luck... |
No description provided.