Adding Boost 1.xx.x support, what's the approach? about boost-cmake

[Orphis]

I would say to update your dependency for a modern Boost. Old versions are not very interesting for a project like this. It's over 5 years old and probably doesn't support mobile platforms well or any current compilers.

Of course, feel free to fork it and change whatever is needed of course for your usecase, but it's certainly easier to update the other library than coerce Boost to work with current compilers.

For newer versions, it's usually just drop the new archive, use it and see if the tests pass, update the build scripts as necessary for new files and new required build flags.

[helmesjo]

Yeah, I hear you! This is however exclusively for an external dependency, and I want to modify close to nothing or in "worst case" make a pull request that gets merged (private temp-fixes is not an option). I started a discussion about supporting a newer version and it wasn't out of the question, but support for boost 1.46 (!) had to be preserved. This however presumes that there aren't a lot other things to #ifndef...
That's why I hoped to just get 1.56 building first and foremost!

As you say, that version is also terribly old but this dependency on legacy boost is only for this one framework. If I ever fall into using boost myself in any project, it will of course target a modern version.

Anyways, I'll give it a try with the help of boostdep and we'll see how it goes!

[Orphis]

In the case of that library, a simple ifdef around the Boost version should be enough to fix it for newer versions, and I would recommend that approach.

But another approach is possible, which would be to define BOOST_THREAD_USES_DATETIME, which will re-add the missing functions back. Functionality is rarely removed from Boost and usually hidden behind some flags.

[helmesjo]

Alright thanks, I'll take a look at it.