Looking forward to the rest of this series! Hope it's structured to cover the most "bang for your buck" boost libraries first, sorta like what you showed abit with boost logging here. I'm sure many of these libraries like boost asio deserve their own series just from how large they are. Great stuff!
Best Library 1st time i see it, is loong time. But I use now only Asio non boost. I have same libraries write by my self look like boost but boost is best best than mein.
Do this for a big project with 20 libs and everybody will hate you that tries to get your project compiling on theirs machine. Have one project require the one version of the boost with another build configuration or even a whole different boost version. Manual dependencies management is a big burden. Conan removes all this complexity. It downloads or builds everything you need on demand and exactly in the configuration you are seeking.
@@LötwigFusel We use Boost 1.78, the entire team uses the same version (debug and release) and upgrading Boost version is major project in itself, so not done very frequently. I am curious, what scenario requires using a different version of boost per project? Is boost not backwards compatible? Are there any specific examples you have where code written to compile with 1.78 version will not work with 1.76 ? Thank you.
Looking forward to the rest of this series! Hope it's structured to cover the most "bang for your buck" boost libraries first, sorta like what you showed abit with boost logging here. I'm sure many of these libraries like boost asio deserve their own series just from how large they are. Great stuff!
Very nice, keep up the good work man.
I need to develop some project with some one in C++. For Oil Industrial. Who is ready.
What exactly are you looking for?
Best Library 1st time i see it, is loong time. But
I use now only Asio non boost.
I have same libraries write by my self look like boost but boost is best best than mein.
Conan just adds more complexity. Why not just install boost first and then use CMake ? There are tons of examples of doing that exactly.
Do this for a big project with 20 libs and everybody will hate you that tries to get your project compiling on theirs machine. Have one project require the one version of the boost with another build configuration or even a whole different boost version. Manual dependencies management is a big burden. Conan removes all this complexity. It downloads or builds everything you need on demand and exactly in the configuration you are seeking.
@@LötwigFusel We use Boost 1.78, the entire team uses the same version (debug and release) and upgrading Boost version is major project in itself, so not done very frequently. I am curious, what scenario requires using a different version of boost per project? Is boost not backwards compatible? Are there any specific examples you have where code written to compile with 1.78 version will not work with 1.76 ? Thank you.